Replying to @⁨Sibbo@sopuli.xyz⁩

What risk are you trying to mitigate, specifically?

If it’s the CA taking over your site, control over your CA specifically doesn’t really give any advantage to an attacker (they would have to hijack traffic and provide a new certificate - nobody will notice if the certificate is from a different CA).

Note that your CA cannot decrypt the exchanges between your server and its clients.

Replying to @⁨IpsumLauren@lemmy.world⁩

Edit: no, it doesn’t. Looking at the comments below, it’s public key crypto.

Original comment:

The problem is that if that is your threat model, then the VPS provider, ISP, and literally everything between you and letsencrypt can pull a conpromised key fro letsencrypt.

This actually happened btw, an xmpp server was attacked this way, they compromised not the server itself, but the VPS provider MITMed their traffic: www.devever.net/~hl/xmpp-incident

If your threat model involves this, then the only solution is Tor, which eliminates these requirements of trust.

Edited ⁨⁨Sep⁩ ⁨19⁩, ⁨2026⁩, ⁨18:18⁩⁩en