6 ms·
I've never seen a provider of SSL certificates (or any other service) allow you to "prove ownership" of a domain by receiving an email. Even from the early day
by smt88 12y ago
I've never seen a provider of SSL certificates (or any other service) allow you to "prove ownership" of a domain by receiving an email.
Even from the early days of email, it has never been the case that a majority of a domain's email addresses were assigned to owners of the entity.
That is just absolutely insane.
- justinsb 12y agoProving ownership by sending email to the contacts in the WHOIS record is the _only_ way I've seen for the cheapest certificates. What other ways are you thinking of, and can you point to any CAs that do them (for their cheapest certificates)?
- smt88 12y agoI have no problem with that, but that's not what happened in the article.
- stephenr 12y agoWhere does it say that isnt what happened? It's entirely possible the WHOIS data for the domain in question had several email addresses listed, at least one of which was not blacklisted for use by clients.
- ams6110 12y agoYears ago you had to do things like fax an approval letter printed on company letterhead.
- toast0 12y agoWhenever we need something on leterheas, our GC makes up letterhead on the spot using images on our media resources page.
- patio11 12y agoI think it's Old Webmaster Lore that there exist roughly ten email addresses which are Widely Considered To Be Special. abuse@, postmaster@, and administrator@ are three of them. There exist a lot of systems in the world which rely on this being true, irrespective of whether it is in fact true.
- tomjen3 12y agoI seem to recall DNS being one of them, that is that you have to have somebody monitor abuse@. But either way, this is yet another reason to ditch certificates: it is way too fragile a system (not the least because it gives users the "it has a lock, it means it is safe").
- helper 12y agoIs the rest of the list you are thinking of RFC2142?[1] [1]: https://www.ietf.org/rfc/rfc2142.txt https://www.ietf.org/rfc/rfc2142.txt
- mukyu 12y agoEmail is an incredibly common method for domain validated certificates. The other common options are a TXT/CNAME record or uploading a specific file to a certain URL. The requirements for domain validation are: 11.1.1 Authorization by Domain Name Registrant For each Fully-Qualified Domain Name listed in a Certificate, the CA SHALL confirm that, as of the date the Certificate was issued, the Applicant (or the Applicant’s Parent Company, Subsidiary Company, or Affiliate, collectively referred to as “Applicant” for the purposes of this section) either is the Domain Name Registrant or has control over the FQDN by: 1. Confirming the Applicant as the Domain Name Registrant directly with the Domain Name Registrar; 2. Communicating directly with the Domain Name Registrant using an address, email, or telephone number provided by the Domain Name Registrar; 3. Communicating directly with the Domain Name Registrant using the contact information listed in the WHOIS record’s “registrant”, “technical”, or “administrative” field; 4. Communicating with the Domain’s administrator using an email address created by pre-pending ‘admin’, ‘administrator’, ‘webmaster’, ‘hostmaster’, or ‘postmaster’ in the local part, followed by the at-sign (“@”), followed by the Domain Name, which may be formed by pruning zero or more components from the requested FQDN; 5. Relying upon a Domain Authorization Document; 6. Having the Applicant demonstrate practical control over the FQDN by making an agreed-upon change to information found on an online Web page identified by a uniform resource identifier containing the FQDN; or 7. Using any other method of confirmation, provided that the CA maintains documented evidence that the method of confirmation establishes that the Applicant is the Domain Name Registrant or has control over the FQDN to at least the same level of assurance as those methods previously described. Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates, v.1.2.3 https://cabforum.org/wp-content/uploads/BRv1.2.3.pdf https://cabforum.org/wp-content/uploads/BRv1.2.3.pdf
- smt88 12y agoAgain, email addresses are fine, but which email address is important. The address on the WHOIS record isn't bad, as long as that's disclosed to the certificate purchaser ahead of time. TXT records and uploading files are definitely better, though.
- ivanr 12y agoIf you're going to change your messages after posting them, at least disclose that you did so. Some of the replies don't make sense with the new content you added.
- deleted 12y ago[deleted]