Closed Bug 1264670 Opened 9 years ago Closed 9 years ago

Create a signing certificate for signing remote-newtab

Categories

(Cloud Services :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mgoodwin, Assigned: jvehent)

References

Details

Please create production and staging secp384r1 certificates for signing remote-newtab content. The certificates should: * Have the following SAN: remote-newtab-signer.mozilla.org * Have the codeSigning EKU * Chain to their respective roots (previously agreed upon).
The certificate has been create for remotenewtab.content-signature.mozilla.org in the staging environment. Production cert is not yet created. Needinfo myself to take care of it later.
Flags: needinfo?(jvehent)
Chain published at https://content-signature.cdn.mozilla.net/chains/remotenewtab.content-signature.mozilla.org-20160610.prod.chain . Valid for 6 months. Autograph does not yet return it, waiting on bug 1263793 to be merged in central then I'll update the service.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(jvehent)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.