3 ms·
I think a major difference here is that LetsEncrypt relies on an already existing third-party authority, that generally has some scrutiny to it: DNS registrars.
by lostmsu 6y ago
I think a major difference here is that LetsEncrypt relies on an already existing third-party authority, that generally has some scrutiny to it: DNS registrars.
- kevingadd 6y agoNot sure what you mean here, code signing certs are issued by many of the same companies that were issuing SSL certs before LE existed
- gruez 6y agoHis point is that with webtrust certificates (what most people think of as "ssl certificates"), it's easy to validate the identity (DNS name), either by sending a email or validating a DNS record. For code signing certificates, they're not issued to DNS names, they're issued to legal entities (natural persons or corporations), which you can't easily validate.
- Zak 6y agoCode signing certificates could be issued to domain names, and that might provide a lower bar to clear while still offering a good way to establish a reputation.
- donmcronald 6y agoThey should be issued to domain names. I bet there are close to 100 domains I’d recognize from small or open source developers and I couldn’t tell you the name or company name of a single one of them. It’ll never happen though because Microsoft, Google, and Apple are doing everything they can to de-emphasize domains and online namespaces so they can become the gatekeepers of all content.