#StartSSL

2025-06-03

Remember the threads¹² about #LetsEncrypt removing a crucial key usage from certificates issued by them in predictive obedience to their premium sponsor Google?

We were at first concerned about #SMTP. While I had lived through this problem with #StartSSL by #StartCom back in 2011, I only had a vague recollection of Jabber but recalled in detail that it broke server-to-server SMTP verification (whether the receiving server acted on it or just documented it).

Well, turns out someone now reported that it indeed breaks #XMPP entirely: https://community.letsencrypt.org/t/do-not-remove-tls-client-auth-eku/237427/66

This means that it will soon no longer be possible at all to operate Jabber (XMPP) servers because the servers use the operating system’s CA certificate bundle for verification, which generally follows the major browsers’ root stores, which has requirements from the CA/Browser forum who apparently don’t care about anything else than the webbrowser, and so no CA whose root certificate is in that store will be allowed to issue certificates suitable for Jabber/XMPP server-to-server communication while these CAs are the only ones trusted by those servers.

So, yes, Google’s requirement change is after all breaking Jabber entirely. Ein Schelm, wer Böses dabei denkt.

Update: it also breaks the connections between domain registrars and registries, with most being unaware that there even is a problem at this time, let alone the crazily short timeframe. See the thread linked to in a self-reply, which also confirms that the CA/Browser forum is supporting Google in this (possibly by means of Google paying, my interpretation).

While https://nerdcert.eu/ by @jwildeboer would in theory help, it’s not existent yet, and there’s not just the question of when it will be included in operating systems’ root CA stores but whether it will be included in them at all.

Google’s policy has no listed contact point, and the CA/B forum isn’t something mere mortals can complain to, so I’d appreciate if someone who can, and who has significant skills to argument this in English and is willing to, to bring it to them.

① mine: https://toot.mirbsd.org/@mirabilos/statuses/01JV8MDA4P895KK6F91SV7WET8
② jwildeboer’s: https://social.wildeboer.net/@jwildeboer/114516238307785904

Charles-Édouard Costecharly@occitanie.social
2017-07-02

Vu sur le site de #StartSSL... Ils viennent de perdre un client.

Ollivier Robert 🇺🇦😷🌈Keltounet
2017-04-18
Ollivier Robert 🇺🇦😷🌈Keltounet
2017-04-18

@aeris just expressing my very intense frustration at

Ollivier Robert 🇺🇦😷🌈Keltounet
2017-04-18

OK, , you win.

Just installed acme.sh to replace everything you manage to botch over to get LE certs instead.

(no I didn't need to spend my limited time in this right now)

Oh, thanks for the free certs the last few years but you fscked up, deal with it.

Nobody [LinuxWalt (@lnxw48a1)]lnxw48a1@nu.federati.net
2017-02-12
@clacke @aaron It looks to me like they removed all their news releases since late 2015. Maybe related to the reason #Mozilla stopped trusting new Startcom / #StartSSL certs?
lnxw48 (Linux Walt)lnxw48@fresh.federati.net
2016-06-15
Seen via @aaron and @jpope on #diaspora #StartSSL announces #StartEncrypt automated certs. http://url.federati.net/5uwJv Feeling competition from #LetsEncrypt ? #LEcrypt

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst