Issue 2170: Add AddTrust External CA Root to net/base/ev_root_ca_metadata.cc
http://code.google.com/p/chromium/issues/detail?id=2170
Comment #4 by [EMAIL PROTECTED]:
The patch qualifies for EV the root certificate with SHA-1 fingerprint {
0x02, 0xfa,
0xf3, 0xe2, 0x91, 0x43, 0x54, 0x68, 0x60, 0x78, 0x57, 0x69, 0x4d, 0xf5,
0xe4, 0x5b,
0x68, 0x85, 0x18, 0x68 },
CN = AddTrust External CA Root
OU = AddTrust External TTP Network
O = AddTrust AB
C = SE
with serial number 1,
which is listed in the Comodo EV CPS.
Comodo has passed a WebTrust EV audit performed by KPMG:
https://cert.webtrust.org/SealFile?seal=636&file=pdf
I have no objection with including this as an EV-qualified root. Assigning
to Wan-
teh.
Wan-teh, what change were you proposing, beyond the patch submitted? If the
certificate can chain up to two roots, and the chain to this certificate is
shorter,
do we have the information we need to traverse the longer chain to the
other root?
Issue attribute updates:
Owner: [EMAIL PROTECTED]
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to chromium-bugs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
