Closed
Bug 696775
Opened 13 years ago
Closed 13 years ago
New authenticode signing cert for nightly builds
Categories
(Release Engineering :: General, defect, P1)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: catlee)
References
Details
We need a new signing cert for signing nightly builds (or parts thereof).
|
Assignee | |
Comment 1•13 years ago
|
||
Process in 677025#c4 worked for the most part. A few clarifications:
- Log in under "My Account" -> "Certificate Center"
- The Company / Department combination must be unique for all active certs. I used "Mozilla Corporation (Nightly Builds)" for this one. The department / OU is "Release Engineering".
|
|
Assignee | |
Comment 2•13 years ago
|
||
Trying again with CN="Mozilla Corporation (Nightly Builds)", OU="Mozilla Corporation"
|
|
Assignee | |
Comment 3•13 years ago
|
||
Ok, we finally have this. CN="Mozilla Corporation", OU="Release Engineering (Nightly Builds)".
Thawte has a lovely undocumented 19 character passphrase limit for their private keys. Took me a while to figure this out, having used a 20 character passphrase.
Keys are in D:\2011-nightly-keys
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•