>You agree, that You will install Your Certificate only on servers that are accessible at the subjectAltName(s) listed in Your Certificate How the fuck are you gonna prove that
@dcc I have a list of ACME providers here, found in acme.sh (that I don't recall the origin of). Let's Encrypt, Buypass, Zero SSL, SSLCOM, Google.
Of course, I automatically ignored the big jew, and of the others, only LE and ZSSL are willing to issue certs for free, the latter of which has substantial restrictions. I'm still probably going to use it for one of my domains, just as a tiny bit more insurance.
@dcc Because it doesn't really prove anything. But then you realise that LE doesn't really prove anything either lol, they've broken the whole system while sucking the jew cock, instead of actually breaking the system the right way.
sites that employ ssl can be intercepted in transit and changed UNIQUELY FOR THE VIEWER.
you may not believe this, but it's a thing.
think about dns resolvers, the infrastructure, network topology, and people who speak their minds, and who may 'be getting' different versions of a site......
Which just results in you trading trust in the certificate authority for trust in the DNS system, and have it not function anywhere because nobody actually uses DANE, not even curl.
LE is amazing because you can always forget to renew the cert. It was a quick and dirty hack to solve the issue of "everything lacks SSL" post-Snowden.
@PhenomX6@dcc This is why I am currently writing my own little ACME client, because 8000 lines of sh is frankly absurd, even for supporting however many systems it does (_time2str has comments noting BSD, linux, solaris and busybox). My client is about 10 lines so far and I'm halfway through account registration, so I'm expecting 50 lines, tops. Even if I did twice that many for 10 other systems, I'd still be well ahead of acme.sh? Not ahead of acmy-dns-tiny though, but it starts out by defining 4-5 functions inside one gigafunction that straight up tells pylint to not bitch about how big it is lol
@dcc@PhenomX6 Yeah. Wildcard is dns so I'm just going to shove a line in my zone file (I need to write a regex to replace the old one) and reload named, then wait a bit before continuing. For some reason this isn't enough to also get the root domain, but that's trivial by comparison; just echo $blah > $blah2.
By quick and dirty hack, I mean back when you had to spend $$$ for a cert from DigiCert (formerly VeriSign). Look how much they cost for a cert, and even a cheaper CA is a few bucks a year.
The idea of LE was to force everyone on the internet into using SSL and in particular newer versions of SSL/TLS. In particular, as much as normies seem to have forgotten the Snowden leaks (and it's very easy to write them off in their apathy to move off of centralized services), the #1 thing that did happen was the rise of HTTPS. That's the #1 difference before and after the leaks, and it definitely locked out a lot of old computer users and boomers still using the unencrypted web as well. In fact, if you look at old versions of IE (if you don't remember those days) or old shopping websites from the past, the mindset was that HTTPS was only for things like banking and online shopping.