3 ms·
> If an attacker is specifically targeting me and thinking about my passwords, there's not much I can do at that point. Have really long passwords that are ext
by theandrewbailey 10y ago
> If an attacker is specifically targeting me and thinking about my passwords, there's not much I can do at that point.
Have really long passwords that are extremely random on a bit-by-bit basis and doesn't have a snowball's chance in hell of containing a dictionary word (which are the blindingly killer flaw in your formula). Like: 6vRmÓ£æp¥£{&XèñgäÐë¸pH©Þ|÷g¸jn§/¥ÔÎpV4fÎ or ò\f4¬Ð³ &{W+ãÄçÏ)æý½06Ýzȯ+µ>få²9Æð:WÚuÂ
> Plus, I still don't get why 1Password is better than a password generator on the 4th point.
Because you have credentials that are 100% externally independent of each other. Only you have access to the plaintext passwords (the only way they are related) and you define the terms on which the ciphertext is distributed.
- rocqua 10y agoThat is massive overkill. 128 bits of security is way more than sufficient. 23 characters (uppercase, lowercase, numbers) already gives much security. Honestly, 128 bits is already overkill. An attacker that determined is probably quite proficient at rubber hose cryptography. The point of PW manager is to prevent compromise from spreading. Not to keep a motivated NSA out of your PC.
- theandrewbailey 10y agoI know, but that's a good property to have, it's easy to do, and the extra costs are insignificant.
- rocqua 10y agoIt's a useless property to have, and the extra costs make it much harder to transcribe by hand. Never mind the fact that using non-ascii is asking for compatibility problems. Honestly, diceware[1] is probably an even better choice, though it sometimes fails symbol count requirements. [1] http://world.std.com/~reinhold/diceware.html http://world.std.com/~reinhold/diceware.html