logoalt Hacker News

yayachiken • today at 9:11 AM • 1 reply • view on HN

SSL/TLS has always been a wonky and complicated standard built upon other wonky standards like x509 and ASN.1 (for PKI) that nobody would touch unless they are forced to.

There is a reason why people did not do a lot of TLS (outside of anything involving monetary transactions) before Firesheep, the NSA leaks were the final nail in the coffin for unencrypted HTTP. On top of that Let's Encrypt and ACME did not exist, so TLS was behind a paywall on top of that.

And then everything proliferated relatively quick even for tech standards. I guess people grabbed onto the next available tooling just like a drowning person would take any piece of driftwood.

Not so fun fact: AFAIK the openssl binary was initially explicitly meant to be only used for testing. That is why its command line is so strange. It was initially meant to expose a couple of low-level primitives, not to implement workflows. One example would be the openssl-ca man page, which explicitly mentions this. People didn't care because unfortunately you could somehow do everything you could ever want with the openssl binary and I guess that is also something how the impression stuck that openssl is the most advanced library.


Replies

Woodi • today at 11:55 AM

> Not so fun fact: AFAIK the openssl binary was initially explicitly meant to be only used for testing.

I'm in shock ! Someone noticed ! Thanks man ! :)

In the meantime in real world IT :>>

line 57: https://github.com/acmesh-official/acme.sh/blob/master/acme....

line 306: "This script requires openssl binary" https://github.com/dehydrated-io/dehydrated/blob/master/dehy...

Pretty recommended scripts :)

And I'm sure there are more and not only for ACME, for example I'm sure I saw few examples in production setup docs from IBM and Redhat... :>

Yes, openssl library is wholesale backdoor, subtype: footgun.