Closed Bug 425518 Opened 16 years ago Closed 16 years ago

Enable multiple roots for EV (and remove 1): Geotrust, Thawte, Verisign, Trustwave, Comodo

Categories

(Core :: Security: PSM, defect, P2)

Product:
Core
Component:
Security: PSM
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: KaiE, Assigned: KaiE)

References

Details

Attachments

(1 file, 1 obsolete file)

Patch v2
6.24 KB, patch
rrelyea
: review+
nelson
: review+
Details | Diff | Splinter Review 
This bug is meant to land a single patch that enables multiple roots for EV.
Blocks: 418902
Depends on: 425469
Attached patch Patch v1 (obsolete) — — Splinter Review 

    
  
Depends on: 425538

    
  
Blocks: 426572, 426575
Summary: Enable multiple roots for EV (and remove 1): Geotrust, Thawte, Verisign, Trustwave → Enable multiple roots for EV (and remove 1): Geotrust, Thawte, Verisign, Trustwave, Comodo

    
  
Flags: blocking1.9?

    
    

    
  

      
      
      
      

        Attached patch
          
          
        Patch v2
        — 
          — Splinter Review
      

    


  
This patch has Comodo's roots in addition.

        Attachment #312142 -
        Attachment is obsolete: true

    
  
Depends on: 426681

    
    

    
  
+'ing this so we get a resolution.  Don't want to hold this progress back.
Flags: blocking1.9? → blocking1.9+
Priority: -- → P2

    
  

        Attachment #313270 -
        Flags: review?(rrelyea)

    
    

    
  
Comment on attachment 313270 [details] [diff] [review]
Patch v2

I see nothing obviously wrong with this patch.  
It is correct in form.  
I have not verified that the serial numbers of the 8 certs being added are the expected 8 serial numbers.

        Attachment #313270 -
        Flags: review+

    
    

    
  
Comment on attachment 313270 [details] [diff] [review]
Patch v2

r+ rrelyea

        Attachment #313270 -
        Flags: review?(rrelyea) → review+

    
    

    
  
checked in, marking fixed.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED

          You need to log in
          before you can comment on or make changes to this bug.