Closed Bug 1392852 Opened 5 years ago Closed 5 years ago

Disable EV treatment for old StartCom root certificates

Categories

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

51 Branch
defect

Tracking

()

RESOLVED FIXED
mozilla58
Tracking Status
firefox58 --- fixed

People

(Reporter: kwilson, Assigned: jcj)

References

Details

(Whiteboard: [psm-assigned])

Attachments

(1 file)

Please remove EV treatment for the following three StartCom root certificates. 

1) CN=StartCom Certification Authority, OU=Secure Digital Certificate Signing, O=StartCom Ltd., C=IL
SHA-1 Fingerprint: 3E:2B:F7:F2:03:1B:96:F3:8C:E6:C4:D8:A8:5D:3E:2D:58:47:6A:0F
SHA-256 Fingerprint: C7:66:A9:BE:F2:D4:07:1C:86:3A:31:AA:49:20:E8:13:B2:D1:98:60:8C:B7:B7:CF:E2:11:43:B8:36:DF:09:EA

2) CN=StartCom Certification Authority, OU=Secure Digital Certificate Signing, O=StartCom Ltd., C=IL
SHA-1 Fingerprint: A3:F1:33:3F:E2:42:BF:CF:C5:D1:4E:8F:39:42:98:40:68:10:D1:A0
SHA-256 Fingerprint: E1:78:90:EE:09:A3:FB:F4:F4:8B:9C:41:4A:17:D6:37:B7:A5:06:47:E9:BC:75:23:22:72:7F:CC:17:42:A9:11

3) CN=StartCom Certification Authority G2, OU=null, O=StartCom Ltd., C=IL
SHA-1 Fingerprint: 31:F1:FD:68:22:63:20:EE:C6:3B:3F:9D:EA:4A:3E:53:7C:7C:39:17
SHA-256 Fingerprint: C7:BA:65:67:DE:93:A7:98:AE:1F:AA:79:1E:71:2D:37:8F:AE:1F:93:C4:39:7F:EA:44:1B:B7:CB:E6:FD:59:95
Priority: -- → P2
Whiteboard: [psm-backlog]
Assignee: nobody → jjones
Status: NEW → ASSIGNED
Comment on attachment 8919084 [details]
Bug 1392852 - Disable EV treatment for old StartCom root certificates

https://reviewboard.mozilla.org/r/190000/#review195152

Thanks!
Attachment #8919084 - Flags: review?(dkeeler) → review+
Priority: P2 → P1
Whiteboard: [psm-backlog] → [psm-assigned]
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/d72d02a5f8ac
Disable EV treatment for old StartCom root certificates r=keeler
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/d72d02a5f8ac
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla58
You need to log in before you can comment on or make changes to this bug.