3/n Zxcvbn checks for mangled variations of its blacklists. Aka could easily be said it has over 300mil blacklist depending on configuration
-
-
Replying to @lakiw @TychoTithonus and
4/n What I think makes Zxcvbn different from using Troy Hunt's list though is that it attempts to explain why a password was rejected aka UX
1 reply 1 retweet 0 likes -
Replying to @lakiw @TychoTithonus and
5/n Much longer way of saying the disagreement might not be on size of blacklist but the user's experience with the blacklist ;p
2 replies 0 retweets 1 like -
Replying to @lakiw @thorsheim and


:) Put another way: teaching/UX about entire *classes* of bad password scales much better than a huge list of *only* leaked passwords1 reply 0 retweets 1 like -
Replying to @TychoTithonus @lakiw and
Use Chinese. Use Japanese. Use Cyrillic, Greek, Hebrew & Arabic. Use Unicode. Use it all. Choose life. Choose UX. Choose your own password.
2 replies 0 retweets 2 likes -
Replying to @thorsheim @TychoTithonus and
If you think using Japanese or Chinese for passwords is reasonable, you clearly know nothing about how those two languages work.
3 replies 0 retweets 2 likes -
Replying to @marcan42 @thorsheim and
Yeah
@thorsheim is a password rookie I totally agree

2 replies 0 retweets 1 like -
Replying to @m33x @thorsheim and
Go make up and type some passwords in Japanese, I'll be waiting to see how well that goes ;)
2 replies 0 retweets 0 likes -
My attempt to bruteforce hiragana & katakana (Rurapenthe method) on LinkedIn corpus had 0 hits. Figured I was doing it wrong - maybe not!
1 reply 0 retweets 0 likes -
Replying to @TychoTithonus @m33x and
Let's just say I've seen poorly configured systems logging all passwords in Japan, and none of them were non-ASCII. Often outright forbidden
1 reply 0 retweets 0 likes
(yes, I made them fix that, "customer support" excuses be damned)
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.