@aral @EUCommission @nlnet call me weird but the developments of @letsencrypt vs. @cacert shows everything wrong with the way #SSL works.
We would've had a superior alternative to #LetsEncrypt if #GAFAMs weren't able or even allowed to cockblock #CACert by refusing to import it's ROOT-CA, whilst every commercial #CA gets their keys imported, no matter how shit they are or that they are essentially a hostile state actor!
@leyrer
Ich sagte nicht, dass er tatsächlich "vertrauenswürdig" ist. Aber Faktum ist, dass es diesen und zwei weitere "Vertrauensdiensteanbieter" in Österreich gibt. Und es bieten alle Drei auch S/MIME kompatible Zertifikate an.
Aber Du hast im Grunde schon recht, da geniesst bei mir #CAcert höheres Vertrauen als die drei zusammen.
Just got a mail notification that #CAcert relocated its association from Australia to #Switzerland, namely to #Geneva.
Wasn't aware that they're still alive and active after all the degradation due to expired and cryptographically outdated root certificates, etc.
@drwho Shit like this makes me hate not just #snap but @letsencrypt because that's more code than the entire backend for @cacert ...
| R.I.P Natenom acme.sh & #CertBot scripts they made AND certainly not more than the #API for #CAcert back in it's days...I think there needs to be more and harder pushes for #FrugalComputing because there's no valid reason they basically shove an entire #OS onto an existing one...
@rysiek the only thing that pisses me off re: #LetsEncrypt is tuat they basically got #VC-#TechBro #FastLane in regards to acceptance whilst #CaCert got #Cockblocked by #GAFAMs all day despite doing actual #DueDiligence re: who gets a #certificate.
But better @letsencrypt than no #SSL, even tho I think #X509 is bad and ibstead we should've #OpenPGP-based #encryptioncfor everything...