41 ms·
One way hash of the IP.
by DiabloD3 7y ago
One way hash of the IP.
- jacquesm 7y agoThe search space is so small you can simply create a table with all of the hashes and use that to reverse the hash.
- thaumasiotes 7y agoMandatory IPv6 could finally be here! ;D
- GhettoMaestro 7y agoYou could always salt it.
- thaumasiotes 7y agoHow would that address the problem? Salts don't make hashes any less reversible.
- majewsky 7y agoSalts 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.
- EdwardDiego 7y agoYeah, we're GDPR bound and henceforth compliant, and nope, a one-way hash isn't sufficient. We just drop the last octet and accept it. I mean, we can still say 'this impression was from a user in Strasbourg', but we enrich the record with that enroute through our pipeline, about the same time as we drop the last octet of the IP.