3 ms·
The downside is that due to a lack of serious competition, Let's Encrypt seems like an obvious choice, and thus it can be tempting to hardcode it. I have a hom
by tgsovlerkhgsel 6y ago
The downside is that due to a lack of serious competition, Let's Encrypt seems like an obvious choice, and thus it can be tempting to hardcode it.
I have a homebrew Internet-of-shit device that I know has LE hardcoded. I'll have to take it of the wall and reflash if I switch to a new CA (or potentially when some of the changes described by tialaramex happen - I think I hardcoded the new root but I'm not 100% sure).
- manquer 6y agoThe acme protocol is well defined , and code is open source you could always implement your own service. Let’s encrypt only real hold is their root certificate is now in many trust stores , if you control both sides self signed certificates are perfectly fine you don’t need a CA at all
- jrockway 6y agoI think he's talking about the temptation to set up a pin to their root. That can break just as easily as any other pin, and of course you won't be prepared.