Re:Logs were our lifeblood, now they're our liability
by jacquesm on Tuesday October 08, 2019 @05:39PM
(#21197594)
The search space is so small you can simply create a table with all of the hashes and use that to reverse the hash.
[ Parent
| on HN ]
Re:Logs were our lifeblood, now they're our liability
by thaumasiotes on Tuesday October 08, 2019 @06:06PM
(#21197803)
Mandatory IPv6 could finally be here! ;D
Re:Logs were our lifeblood, now they're our liability
by GhettoMaestro on Tuesday October 08, 2019 @08:51PM
(#21198879)
You could always salt it.
Re:Logs were our lifeblood, now they're our liability
by majewsky on Wednesday October 09, 2019 @05:51AM
(#21201611)
Salts are only useful when you already know which hash to check e.g. because the user supplied the username that picks which password hash to check. When matching an IP against a list of salted hashes, you need to hash the input with every possible salt to compare against all hashes in the list. So for performance reasons, it's probably not feasible to use more than one salt (or a small number of salts). Then it's again very possible to reverse the list of salted hashes because the search space is number of all IP addresses times number of salts used, which is way less than the number of all hashes.
Re:Logs were our lifeblood, now they're our liability
by thaumasiotes on Wednesday October 09, 2019 @01:14AM
(#21200239)
How would that address the problem? Salts don't make hashes any less reversible.