From 1ad63b528f3363546e53ed3e07ed014517a7a4bb Mon Sep 17 00:00:00 2001
From: Quantum
You don't have to worry about this hypothetical scenario. Running this sort of attack is prohibitively expensive. - Unless you possess highly valuable secrets that makes this sort of effort worthwhile, in which case you should be - using stuff more complex than a password to protect it. If you have to, you can simply add more words.
+Running this sort of attack is prohibitively expensive. Unless you possess highly valuable secrets that + makes this sort of effort worthwhile (you should use something more secure than passwords in such a case), you don't + have to worry about this hypothetical scenario. If you have to, you can simply add more words.
In practice, most real life systems use secure password hashing algorithms, captchas, and other mechanisms to stop password cracking. It is unlikely that your attacker can reach anywhere close to a million @@ -159,8 +159,8 @@
Another major part of the reason is that a lot of the similar websites fail to generate passwords securely: for
example, they used Math.random()
, which is not a cryptographically secure random number generator,
- and should never be used to passwords. This website aims to avoid such pitfalls, and provide a truly secure
- experience.
+ and should never be used to generate passwords. This website aims to avoid such pitfalls, and provide a truly
+ secure experience.
window.crypto.getRandomValues()
— the only cryptographically-secure random number
generator in JavaScript, instead of
Math.random()
, whose use is explicitly discouraged for this purporse.
- If you don't believe me, that okay. Lots of other people agree with me. Check out + If you don’t believe me, that’s okay. Check out this post on the Information Security Stack - Exchange. The top four answers (by a huge margin) agree with me.
+ Exchange. The top four answers (with vast majority of the votes) agree with me, and they provide more + details and additional material to support xkcd-style passwords.