I implemented @troyhunt's HIBP password list as a pure Python3 Bloom filter, in 629MB (false positive rate = 0.0005)https://gist.github.com/marcan/23e1ec416bf884dcd7f0e635ce5f2724 …
-
-
And this is how I will be using it in production, on the
@euskalencounter reservations website. Comments welcome :)pic.twitter.com/al2DpM2z5P
10 replies 25 retweets 80 likes -
Replying to @marcan42
I would advice against using such a massive block list, top 1K-10K is enough, & implement other serverside features instead. Better UX.
3 replies 1 retweet 6 likes -
Replying to @thorsheim
Top 1K-10K is way too easy to brute force. I could implement attempt throttling, but that's a massive can of worms and hard to get right.
1 reply 0 retweets 1 like -
Replying to @marcan42
Too easy? Dude, If somebody has your hashes you're pwnd already! Nobody attacks online login using a 306 million wordlist.
1 reply 0 retweets 2 likes -
Replying to @thorsheim
But people *do* attack online login with a 10k wordlist.
1 reply 0 retweets 2 likes -
Replying to @marcan42
Maybe they do. If I have an account with you and you can't detect or block 10k attacks against it, I'll delete my account with your service.
2 replies 0 retweets 3 likes -
Replying to @thorsheim
Blocking attacks requires finesse. For our use case, a single user wrongly blocked is much worse than 1000 rejected passwords.
1 reply 0 retweets 2 likes -
Replying to @marcan42 @thorsheim
But hey, keep making assumptions about our userbase and use case ;-)
1 reply 0 retweets 1 like -
Replying to @marcan42
I'm not. I was thinking completely generic userbase in my replies. For a lanparty my first question would be: risk analysis?
1 reply 0 retweets 0 likes
At this point I'm just going to enable it for the upcoming ones (which will sell out anyway) and see what the logs say about actual UX ;)
-
-
Replying to @marcan42
Now that I would actually love to hear about when you're done tbh!
0 replies 0 retweets 3 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.