3 ms·
SSL officially became TLS in 1999 when the Internet Engineering Task Force published TLS 1.0 as RFC 2246. TLS 1.0 was designed as an upgrade to SSL 3.0, address
by woleium 1y ago
SSL officially became TLS in 1999 when the Internet Engineering Task Force published TLS 1.0 as RFC 2246. TLS 1.0 was designed as an upgrade to SSL 3.0, addressing security vulnerabilities and making several improvements, but the changes were significant enough to prevent interoperability between SSL 3.0 and TLS 1.0
It seems a bit silly to call a new tool an SSL manager?
- browningstreet 1y agoYou can’t fight mindshare. Naming is branding, not a ruleset. Maybe think of it as “SSL certs” the thing uses TLS x.0 standard. Too many people will say “what?” if you call it TLS cert management. Or worse, they will ignore it because it doesn’t trip the synapses.
- vivzkestrel 1y agounfortunately outside tech circles, most people still refer to it as SSL or HTTPS. They dont know about the intricacies of the changes involved
- fab_space 1y agocertmate dev here :) I came from a decade of certificate management in multiple work contexts and YES, all the people refer to them as SSL and not TLS, while TLS 1.2 is the minimum de facto standard nowadays. The point of certmate is to have a simple url like https://certmate/domain/tls https://certmate/domain/tls to grab a valid cert from wherever I am, any time. This because I focused on DNS challenge only. A good feat btw is the deploymenet check, where the app verify if the cert issued is the same deployed on public FQDN. Of course some more interesting additional features will be added soon like: - multiple cloud accounts support - deploy to remote nodes - vault integration/support Enjoy and contribute!