[cabf_validation] Domain Validation Requirement of Mozilla CAInclusion Policy

[Bruce Morton]

For OV and EV, the CAs do more. In both cases the identity, domain and authorization need to be validated. This combination has been working well for us over the last many years.

On the other hand, I do not think that it is best for DV.

Bruce.

From: validation-bounces at cabforum.org [mailto:validation-bounces at cabforum.org] On Behalf Of Rich Smith
Sent: Thursday, July 30, 2015 2:33 PM
To: 'Ben Wilson' <ben.wilson at digicert.com>; validation at cabforum.org
Subject: Re: [cabf_validation] Domain Validation Requirement of Mozilla CAInclusion Policy

+1
I tried to address this fact quite some time ago, and either I did not communicate the idea effectively, or at the time everyone simply disagreed with my reasoning.  Glad to see this topic resurrected.

From: validation-bounces at cabforum.org<mailto:validation-bounces at cabforum.org> [mailto:validation-bounces at cabforum.org] On Behalf Of Ben Wilson
Sent: Thursday, July 30, 2015 1:03 PM
To: validation at cabforum.org<mailto:validation at cabforum.org>
Subject: [cabf_validation] Domain Validation Requirement of Mozilla CAInclusion Policy

On today's call I mentioned that the Mozilla CA Inclusion Policy had something to say about method 1 - "Confirming the Applicant as the Domain Name Registrant directly with the Domain Name Registrar through a Reliable Method of Communication, for example using information provided through WHOIS"

Section 7 of the Mozilla CA Inclusion Policy states: "for a certificate to be used for SSL-enabled servers, the CA takes reasonable measures to verify that the entity submitting the certificate signing request has registered the domain(s) referenced in the certificate or has been authorized by the domain registrant to act on the registrant's behalf;"  https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/inclusion/

I don't have any objection to the current wording of method 1, but in my opinion, a simple WHOIS lookup, without more, doesn't establish that the entity submitting the CSR is the same entity that registered or is authorized to use the FQDN because anyone can submit a CSR and claim to be the entity listed in WHOIS.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://cabforum.org/pipermail/validation/attachments/20150730/f744d0b8/attachment.html