Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

10
  • 1
    @deceze: Not really. See my answer for a replay-resistant cleartext login protocol. Commented Apr 20, 2011 at 1:49
  • 1
    But if it is PKI and the public key is on the client side, how will they have the key to decrypt? Commented Apr 20, 2011 at 1:49
  • 2
    @0A0D That's the point, they don't need to actually decrypt it. Commented Apr 20, 2011 at 1:53
  • 2
    @deceze Point taken. SSL certificate pricing is finally getting within hailing distance of domain registration pricing now, so there's really little excuse. However, I do rather wish that browsers would support anonymous SSL without throwing up a big scary warning AND without displaying any "secure connection" chrome, so it looks just like a regular unsecured connection. If nothing else, that would make life somewhat more difficult for hijackers -- they'd have to MITM instead of just sniff. Commented Apr 20, 2011 at 2:05
  • 4
    @0A0D And I'm saying I'm not even interested in decrypting your encrypted password. :) I'll just sniff the encrypted password you're sending to the server and forge the exact same request, sending the same encrypted password to the server, which will allow me to log in the same way you do. Without a nonce this replay attack is trivial and I don't care whether or how or how often you encrypt your password. Commented Apr 20, 2011 at 12:09