2 ms·
"You might as well" implement your own secure transport protocol instead of SSL/TLS by the same thinking. With your own protocol implemented in your app there's
by tialaramex 9y ago
"You might as well" implement your own secure transport protocol instead of SSL/TLS by the same thinking. With your own protocol implemented in your app there's no need to rely on whatever TLS implementation ships with the device.
In both cases it's a trade, and my argument is that just as it would have been a mistake to roll your own transport security protocol in 2011, it's a mistake to make your own PKI in 2018. At least for any reason other than education.
There doubtless were people in 2011 who could have come up with something better than TLS 1.2, and there doubtless are people in 2018 who can do a better job of managing a PKI than we've done of the Web PKI. But most people's secure transport protocol in 2011 would have made SSL 2.0 look good, and most people's attempt at running their own CA today is going to be OpenSSL on somebody's laptop.
Part of the reason for my skepticism is interacting with private PKIs where they touch the edge of the Web PKI. Without exception they are badly managed. Whether it is the Payment Card Industry, the US Federal Government, or a company-specific setup that I end up debugging, it's pretty shocking. If Bad Guys aren't breaking these systems, it's because they aren't trying. And if they aren't trying, who cares what you do about security - anything would work.
- tptacek 9y agoMost software developers, tasked to implement their own secure transport protocol, would fail to produce something as secure as even TLS 1.2, which is a flawed transport. And, of course, designing and implementing a secure transport is vastly harder than simply whitelisting certificates. So there's that, and there's the fact that HTTPS makes it through middleboxes that custom protocols don't. No, I don't think this is a meaningful comparison.