Gonna pursue my progressive hashing idea, even though this may eventually be replaced with a different system. Now that we have privacy aware DNS resolvers, we urgently need privacy-aware content filtering systems.
-
-
Replying to @jedisct1
I’m trying to follow the need for progressive hashing to accomplish private content filtering.
1 reply 0 retweets 0 likes -
Replying to @averagesecguy
Mitigate dictionary attacks, yet don’t require to complete all rounds to reject false positives — the fact that most lookups will be true negatives is a reasonable assertion.
3 replies 0 retweets 0 likes -
Replying to @jedisct1
So, I calculate hash, send it to you. You give a go/no go. Eve captures the hash but cannot reconstruct domain from hash.
1 reply 0 retweets 0 likes -
Replying to @averagesecguy
You got it. Or rather: reconstructing the domain is costly.
1 reply 0 retweets 0 likes -
Replying to @jedisct1
Wouldn't scrypt or argon work for that? If you think of a domain as a passphrase. The first lookup would take a bit of time but you could cache the hash on the client side to save time later.
2 replies 0 retweets 0 likes -
Replying to @averagesecguy @jedisct1
Something like http://www.abc.com would be trivial to break but http://i-like-donald-trumps-hair.com would not be.
1 reply 0 retweets 0 likes -
Replying to @averagesecguy
Just loading Facebook needs about 20+ requests. Want to wait 1 minute before you can display the first page (with no other devices on the network and nothing else running simultaneously)?
1 reply 0 retweets 0 likes
Enough talk, this is not IETF. Let’s write code.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.