arcticPeril

13 ms·

1. 1.▲
   by arcticPeril 12y ago

   So, encryption (as opposed to hashing) COULD be prone to frequency analysis (depending on the cipher used, ROT13 for example, ha ha!). IF that's what Yahoo! were using to protect their password data. But that's a big "if.
2. 2.▲
   by arcticPeril 12y ago

   So you're just going to implicitly trust the user's browser to generate the hash for you? Good luck with that, sir. And there is a reason to limit length, the very obvious reason being that short passwords are easier to brute fo
3. 3.▲
   by arcticPeril 12y ago

   > But why? Because you cannot trust any checks performed on the client-side, since the user may have total control over the client-side system, and possess the ability to (somehow) bypass or spoof client-side validation. Client-s
4. 4.▲
   by arcticPeril 12y ago

   Actually, they are (or could be, given that I don't know for sure because I don't work there). It merely means that they are most likely looking for spaces with client-side JavaScript, and rejecting any string that contains spaces
5. 5.▲
   by arcticPeril 12y ago

   Maybe I'm missing an important detail about the lifecycle of arctic ice, but... If the arctic ice contains plastic particles... And the particles are man made... And man has only been making small plastic particles for roughly 100 year