News for hackers. Stuff that matters.
Re:Adding Easy SSL Client Authentication To Any Webapp by michaelmior on Saturday November 30, 2013 @06:27PM (#6825163)
"Private keys cannot be guessed – Because users didn’t choose them!" I don't follow this logic. Sure they're likely to have more entropy than a user-selected password (and almost certainly be longer). However, there's nothing about the fact that the key isn't selected about the user that makes it un-guessable.
Re:Adding Easy SSL Client Authentication To Any Webapp by asdfaoeu on Saturday November 30, 2013 @07:53PM (#6825498)
It's because it actually has enough entropy to be completely improbable guessing.
Re:Adding Easy SSL Client Authentication To Any Webapp by michaelmior on Saturday November 30, 2013 @08:53PM (#6825671)
Some users (of course a tiny minority) generate random passwords. I think the point holds, I just think the presentation isn't completely accurate.
Re:Adding Easy SSL Client Authentication To Any Webapp by joesb on Sunday December 01, 2013 @04:46AM (#6826730)
> They can be guessed – Regardless of complexity requirements, users will find and use the simplest pattern allowed, and attackers routinely take advantage.

It's right in the article that they are talking about average user behavior of choosing guessable password, even if you tell them not to.

Re:Adding Easy SSL Client Authentication To Any Webapp by scriptjunkie on Saturday November 30, 2013 @09:19PM (#6825751)
Private keys should have over 128 bits of entropy, which is enough to make it un-brute-forceable with at least the amount of energy likely to be obtained by any human organization on earth. http://en.wikipedia.org/wiki/Brute-force_attack#Theoretical_... That's what makes it un-guessable. Also, some users do choose passwords with at least as much entropy and are also unguessable. But most don't.
Re:Adding Easy SSL Client Authentication To Any Webapp by mnordhoff on Saturday November 30, 2013 @11:57PM (#6826183)
Security FYI:

This situation concerns RSA keys, not 128-bit symmetric keys; our problem is "factoring a really big number", not "guessing a really big number". A 128-bit RSA key can be broken in seconds.

RSA keys are commonly 2048 bits at the moment. NIST's rough rule of thumb is that a 2048-bit RSA key is equivalent in secureness to a 112-bit symmetric key; for 128-bit equivalence, you need around a 3072-bit RSA key. (2048 provides fine security for the next few decades at least.)

Edit:

You referred to "128 bits of entropy", which could be interpreted as "equivalent to a 3072-bit RSA key". I'm not accusing you of recommending insecure RSA key sizes, I just wanted to make a public service announcement. I've seen people make that mistake before.

Re:Adding Easy SSL Client Authentication To Any Webapp by dmix on Saturday November 30, 2013 @11:11PM (#6826058)
I use automated high-entropy password-generators and a surprising amount of websites cap lengths to 30-50 characters (or even 8 chars sometimes like a Canadian bank I won't name). Allowing super-long passwords would be a good starting alternative to SSL.
Re:Adding Easy SSL Client Authentication To Any Webapp by tmikaeld on Sunday December 01, 2013 @06:15AM (#6826874)
The problem with this is that some sites still only support max 20 characters.
Re:Adding Easy SSL Client Authentication To Any Webapp by tiziano88 on Sunday December 01, 2013 @05:09AM (#6826765)
Social engineering techniques can be very effective when trying to guess a user's password (birth date, pet name, etc.). Also think about not-so-random password like "password", "qwerty", "12345" etc..