Closed Bug 418701 Opened 13 years ago Closed 13 years ago

Enable Quo Vadis root CA certificate for EV use

Categories

(Core :: Security: PSM, enhancement)

PowerPC
macOS
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: hecker, Assigned: KaiE)

References

Details

Attachments

(1 file)

Per bug 403665 I've approved enabling Quo Vadis's existing root CA certificate
(QuoVadis Root CA 2) for Extended Validation use. The corresponding EV policy OID is 1.3.6.1.4.1.8024.0.2.100.1.2.

Thanks in advance for your help getting this change made to PSM!
Blocks: 403665
Attached patch Patch v1Splinter Review
This patch
+
having the required intermediates installed manually
  (I visited http://trust.quovadisglobal.com/qvsslica.crt 
   but clicked cancel, which seems to have installed the valid intermediate)
+
visiting the demo site 
  https://www.boxoffice.bm/SignIn.asp
=
  I get the EV identity UI
Attachment #304764 - Flags: review?(rrelyea)
Comment on attachment 304764 [details] [diff] [review]
Patch v1

r+
Attachment #304764 - Flags: review?(rrelyea) → review+
Attachment #304764 - Flags: approval1.9?
Comment on attachment 304764 [details] [diff] [review]
Patch v1

a=beltzner for 1.9
Attachment #304764 - Flags: approval1.9? → approval1.9+
fixed.
forgot to mark as fixed
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Quoting from bug 403665:

> Hello:  QuoVadis EV certs were showing the correct EV indicators properly in
> the nightlies until the past few days when uniformly they started acting like
> plain SSL again.  Is this known/expected?
> Best, Stephen

Kai - should we reopen?  Or is there a known regression here?
I'm ok to reopen, although the task requested in this bug has been completed successfully. It might be this is a variation of bug 406755. I want to hear answers to my latest question in bug 403665.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
The latest patch in bug 406755 fixes the issue for me.
I think bug 406755 should be marked as blocking.
Depends on: 406755
I'm resolving this as fixed again.
The bug should be fixed with today's checkins for bug 420151 and bug 406755.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.