Closed Bug 1637269 Opened 5 years ago Closed 4 years ago

Add GlobalSign SMIME Roots to Mozilla root store

Categories

(CA Program :: CA Certificate Root Program, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: julie.olson, Assigned: bwilson)

References

Details

(Whiteboard: [ca-approved] - In NSS 3.63, FF 88)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

GlobalSign is requesting the addition of two SMIME roots to be embedded in the Mozilla root store. These roots are for SMIME issuance only, with the intent of chaining our SMIME product line to these roots rather than using our standard TLS roots.

Type: enhancement → task
Whiteboard: [ca-initial]

I have begun filling in a CCADB case to track these two root certificates. We are still awaiting copies of our audit statements for the most recent audit cycle ending 3/31/2020.

https://ccadb.force.com/5001J00000uqvJ6

Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true

Hi Mozilla review team,

Please note I have added the WebTrust Audit details to the above CCADB case.

Please let me know what other details should be added to move this request along in queue.

Thanks!

Performed initial case review. Asking about official corporate name. Also, next step is to review email verification practices.

Assignee: kwilson → bwilson
Whiteboard: [ca-initial] → [ca-verifying] BW 2020-08-11

Globalsign needs to complete the PKI Hierarchy section for each Root Case.

Flags: needinfo?(julie.olson)
Whiteboard: [ca-verifying] BW 2020-08-11 → [ca-verifying] BW 2020-08-13 - See Comment 4 for Needed Info

Hi Ben,

The hierarchies for these two sites are available on CCADB, please let me know if something else is needed for your review.

Thanks!

Flags: needinfo?(julie.olson)

This inclusion request has now been moved to the CP/CPS verification stage.

Whiteboard: [ca-verifying] BW 2020-08-13 - See Comment 4 for Needed Info → [ca-cps-review] - BW 2020-08-27 In review
Whiteboard: [ca-cps-review] - BW 2020-08-27 In review → [ca-cps-review] - BW 2020-12-07 Comment # 7

Hi Ben,

We have published a new version of our CP/CPS that should address most of your meh/bad comments above. The updated documents can be found in our repository: https://www.globalsign.com/en/repository

Let me know if you have any questions or need anything else. Thanks!

Whiteboard: [ca-cps-review] - BW 2020-12-07 Comment # 7 → [ca-ready-for-discussion 2021-01-08]
Whiteboard: [ca-ready-for-discussion 2021-01-08] → [ca-in-discussion] - 2021-01-11

Discussion period announced on the m.d.s.p. list - https://groups.google.com/g/mozilla.dev.security.policy/c/Lq0WgPiQJPk
Scheduled to close on 2-2-2021.

Ben closed the discussion yesterday and stated Mozilla's intent to approve this request.
https://groups.google.com/g/mozilla.dev.security.policy/c/Lq0WgPiQJPk/m/lpZ2X_5aBAAJ

According to Step 10 in https://wiki.mozilla.org/CA/Application_Process#Process_Overview, "After one week, if no further questions or concerns are raised, then a representative of Mozilla may approve the request, by stating so in the bug."

Flags: needinfo?(kwilson)
Whiteboard: [ca-in-discussion] - 2021-01-11 → [ca-pending-approval] 2021-02-02

As per Comment #11, and on behalf of Mozilla I approve this request from GlobalSign nv-sa to include the following root certificates:

  • 'GlobalSign Secure Mail Root R45' (Email)
  • 'GlobalSign Secure Mail Root E45' (Email)

I will file the NSS bug for the approved changes.

Flags: needinfo?(kwilson)
Whiteboard: [ca-pending-approval] 2021-02-02 → [ca-approved] - pending NSS code changes
Depends on: 1693173

I have filed bug #1693173 against NSS for the actual changes.

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Whiteboard: [ca-approved] - pending NSS code changes → [ca-approved] - In NSS 3.63, FF 88
Product: NSS → CA Program
You need to log in before you can comment on or make changes to this bug.