4 ms·
The original idea with SSL was to give out certificates to organizations, not domain holders. The labour involved made this an expensive process and today domai
by xorcist 12y ago
The original idea with SSL was to give out certificates to organizations, not domain holders. The labour involved made this an expensive process and today domain validated certificates are the most common.
The idea was that users should want to validate they speak with the organization McDonald's, not with mcdonalds.com which may or may not belong to them. Turns out users don't, and that the distinction gets even less important over time. Domain names is an important identifier for an organization now. You can still however see the old process at work in EV certificates, which normally carries an extra cost.
If SSL had been designed for domain validation from the start, if would have looked like DNSSEC. Cryptographically verified domain assignments is a good idea, and infinitely more secure than the domain validation schemes we use today.
Here at HN there are a handful who can't resist going on about NSA every time DNSSEC is mentioned, so I expect a few of those now. Please do understand the whole picture and how the complete certificate stack works before taking those statements at face value.
- nailer 12y ago> The original idea with SSL was to give out certificates to organizations, not domain holders. FYI that's exactly what EV SSL does now - hence the company checks, and the green bar: Eg, here's a regular certificate openssl x509 -in example.com.crt -noout -text | grep Subject Subject: 1.3.6.1.4.1.311.60.2.1.3=GB/businessCategory=Private Organization/serialNumber=09378892, C=GB, ST=City of London, L=London, O=example Limited, CN=billing.example.com, DNS:billing.example.com, DNS:www.billing.example.com https://certsimple.com/blog/do-ev-ssl-certificates-have-better-encryption https://certsimple.com/blog/do-ev-ssl-certificates-have-bett...