News for hackers. Stuff that matters.
Re:Introducing s2n, a New Open-Source TLS Implementation by cperciva on Tuesday June 30, 2015 @01:00PM (#9806722)
Yes, but 99.999% of web servers don't need client certs.
Re:Introducing s2n, a New Open-Source TLS Implementation by marcosdumay on Tuesday June 30, 2015 @07:49PM (#9809122)
Of course. But they'll end up implementing it anyway, because of the 00.001%.
Re:Introducing s2n, a New Open-Source TLS Implementation by Tepix on Tuesday June 30, 2015 @02:29PM (#9807432)
Source?
Re:Introducing s2n, a New Open-Source TLS Implementation by Natsu on Tuesday June 30, 2015 @03:29PM (#9807843)
Other than the government, nobody trying to do client certs actually runs the CA that issues them that I've seen. Instead, they trust some random set of commercial CAs, ignorant of the fact that openssl s_client -connect will dump out that list to any passer-by. I've even seen them trusting the "domain control validated only" certs, without any indication of "maybe this is a bad idea, because anyone who can buy a cert can auth to us because we don't even check."

So for every case I've seen, they'd have been ahead to issue credentials themselves and just skip client certs.

Re:Introducing s2n, a New Open-Source TLS Implementation by tedunangst on Tuesday June 30, 2015 @03:30PM (#9807847)
99.999% of web servers.
Re:Introducing s2n, a New Open-Source TLS Implementation by aaronbrethorst on Tuesday June 30, 2015 @03:32PM (#9807867)
I think cperciva's opinion is a sufficiently valid source on this sort of issue, which is probably why you're being down voted.
Re:Introducing s2n, a New Open-Source TLS Implementation by cperciva on Tuesday June 30, 2015 @06:52PM (#9808918)
Thank you for the vote of confidence, but you're wrong. The question of "real world usage of TLS" is one where I would immediately defer to tptacek without question... and you've been around long enough to know that's something I don't do very often.