New issue
Advanced search Search tips

Issue 691899 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Request for EV SSL Treatment for the "IdenTrust Commercial Root CA 1"

Reported by identr...@gmail.com, Feb 14 2017

Issue description

Chrome Version       : all

This is a request to include the the "IdenTrust Commercial Root CA 1" in the list of EV trusted roots in Chrome.  The SHA-1 certificate fingerprint is: ‎df 71 7e aa 4a d9 4e c9 55 84 99 60 2d 48 de 5f bc f0 3a 25

This root is currently included in the Microsoft, Mozilla, Apple, and Java programs and we are upgrading its use to include EV certificates.  

The associated CP and CPS can be found here: https://secure.identrust.com/certificates/policy/ts/

The base audits were completed June last year and reports can be found here: 
a. WebTrust for CAs: https://cert.webtrust.org/ViewSeal?id=2107 
b. WebTrust Baseline Requirements: https://cert.webtrust.org/ViewSeal?id=2106 

For the EV treatment, IdenTrust underwent a point-in-time audit late last year and the report has been attached to this request.  IdenTrust will include have the full EV audit completed in its standard cycle to be completed in June.

Test certificates for EV can be found in this site: 
http://testssl.identrust.com/

A valid EV SSL certificate is here: https://ev-valid.identrustssl.com/

The certificate include the CAB Forum Policy OID and an IdenTrust specific Policy OID.  They are:

Policy Identifier=2.23.140.1.1
Policy Identifier=2.16.840.1.113839.0.6.9


I would appreciate your processing this request and letting us know what are the next steps and potential timeline.

Thank you,

Renne Rodriguez
Trust Infrastructure, Product Manager
renne.rodriguez@identrust.com
Phone: 801-384-3522
www.identrust.com
 
2016 - EV SSL Audit Report.pdf
187 KB Download

Comment 1 by ajha@chromium.org, Feb 20 2017

Components: Internals>Network>SSL
Labels: Needs-Milestone
Cc: rsleevi@chromium.org
Components: -Internals>Network>SSL Internals>Network>Certificate
Cc: kkaluri@chromium.org
Labels: -Type-Bug -Needs-Milestone M-58 Type-Feature
Status: Untriaged (was: Unconfirmed)
Components: -Internals>Network>Certificate Internals>Network>EV
Labels: -M-58
Chrome Team,

Whes should we expect an update?  The request seems to be "untriaged" still.  Are there any other things you may need from us?

Thank you.
Owner: awhalley@chromium.org
Status: Assigned (was: Untriaged)
Thanks for the ping. We consider EV enabling CAs only after they've completed the Mozilla process. I believe that's still in process on Mozilla bug 1339292.

Sign in to add a comment