Re:Introducing s2n, a New Open-Source TLS Implementation
by cperciva on Tuesday June 30, 2015 @11:25AM
(#9805929)
Insane complexity is exactly why supporting client certs is a bad idea.
[ Parent
| on HN ]
Re:Introducing s2n, a New Open-Source TLS Implementation
by richm44 on Tuesday June 30, 2015 @11:58AM
(#9806211)
Certainly true if you don't need them. However since code using the library as a TLS client is already partially present, support for certificate verification is definitely going to need to be added.
At the moment, I'm not that impressed with the testing since even making it build actually requires patching it! This is just due to one of the examples, but from the git history it's been broken since January.
Re:Introducing s2n, a New Open-Source TLS Implementation
by marcosdumay on Tuesday June 30, 2015 @12:34PM
(#9806475)
No, sorry. The insane complexity is on the requirements. If you need client certs, anything you do to satisfy the need will be at least as complex.
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.
Re:Introducing s2n, a New Open-Source TLS Implementation
by JoachimSchipper on Tuesday June 30, 2015 @02:45PM
(#9807552)
Eh, just dumping X509 for something easier-to-parse would cut out a huge chunk of code. Being compatible is hard, but we stick with what we have because of switching cost, not because it's the best we can do.