Thanks Alex. Sorry for the delayed response. I've been traveling today.
We're reaching out to each of the customers and getting their cert replaced.


Looking into this, we did not correctly implement the ballot:
1. We didn't add a check to our backend system too verify the cert included
a descriptor prior to issuance. 
2. On the front end, we missed requiring a Tor descriptor prior to
processing the order. 
3. The validation team received insufficient training on the Tor descriptor
requirement. 

In reality, the issue was too much reliance on the human component of
asserting the Tor descriptors instead of having a technical control in
place. We're working on putting those technical controls in place.  

Jeremy

-----Original Message-----
From: dev-security-policy
<dev-security-policy-bounces+jeremy.rowley=digicert....@lists.mozilla.org>
On Behalf Of Alex Cohn via dev-security-policy
Sent: Sunday, March 11, 2018 9:37 PM
To: [email protected]
Subject: DigiCert .onion certificates without Tor Service Descriptor Hash
extension

In the EV Guidelines [1], Appendix F states "The CA MUST include the CAB
Forum Tor Service Descriptor Hash extension in the TBSCertificate convey
hashes of keys related to .onion addresses." This language was added in
Ballot 201 [2], which had an effective date of 8 July 2017.

The following certificates (and precertificates if the corresponding
certificate is not in a public CT log) were issued by DigiCert after 8 July
for .onion domains, but lack the necessary extension:
https://crt.sh/?q=240277340 (revoked 26 October 2017)
https://crt.sh/?q=261570255
https://crt.sh/?q=261570338
https://crt.sh/?q=261570380
https://crt.sh/?q=261570384
https://crt.sh/?q=261579788
https://crt.sh/?q=261601212
https://crt.sh/?q=261601280
https://crt.sh/?q=261601281
https://crt.sh/?q=261601284
https://crt.sh/?q=261988060
https://crt.sh/?q=326491168
https://crt.sh/?q=326830043
https://crt.sh/?q=328308725
https://crt.sh/?q=328961187
https://crt.sh/?q=329559222
https://crt.sh/?q=330180704
https://crt.sh/?q=351449233 (revoked 10 March 2018 after initial email to
DigiCert)

This was previously discussed on m.d.s.p about a year ago [3].

[1]
https://cabforum.org/wp-content/uploads/CA-Browser-Forum-EV-Guidelines-v1.6.
8.pdf
[2] https://cabforum.org/2017/06/08/2427/
[3]
https://groups.google.com/d/msg/mozilla.dev.security.policy/6pBLHJBFNts/ZtNI
D_xfAgAJ
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to