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
Hint: the sequence of keypresses to type in those languages is unmemorizable and even nondeterministic, thus incompatible w/ password boxes.
2 replies 0 retweets 0 likes -
Replying to @marcan42 @thorsheim and
Huh. I assumed that if a char is type-able, result would be independent of keystroke combos. Where can I read more about this?
1 reply 0 retweets 0 likes -
Replying to @TychoTithonus @thorsheim and
Japanese is typed phonetically but that representation is ambiguous. Disambiguation is an interactive process with feedback.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @TychoTithonus and
And since modern IMEs are adaptive and take into account past usage, the disambiguation part is nondeterministic.
1 reply 0 retweets 0 likes
Read https://en.wikipedia.org/wiki/Japanese_input_methods#Kana_to_kanji_conversion … . In practice what ends up happening is your password is exposed until IME is done, then turns into ••••••••.
-
-
Replying to @marcan42 @TychoTithonus and
(Which was really annoying for me when KDE4 had that bug where it kept allowing the IME on password boxes; KDE5 fixed it)
1 reply 0 retweets 0 likes -
Replying to @marcan42 @TychoTithonus and
It would be possible to type phonetic-only Japanese (kana) for passwords, but that is typed identically to romanized Japanese.
2 replies 0 retweets 1 like - Show replies
New conversation -
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.