Closed
Bug 720777
Opened 12 years ago
Closed 12 years ago
Please add a release MAR signing key to the database of known keys
Categories
(Toolkit :: Application Update, defect)
Toolkit
Application Update
Tracking
()
RESOLVED
FIXED
People
(Reporter: rail, Assigned: bbondy)
Details
Attachments
(2 files, 2 obsolete files)
Attached is the public MAR signing key for release builds (betas and final ones). See bug 718804 for the details.
Assignee | ||
Comment 1•12 years ago
|
||
Is this bug relating to the work on my end? I.e. to make sure updater.exe knows about this key?
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Brian R. Bondy [:bbondy] from comment #1) > Is this bug relating to the work on my end? I.e. to make sure updater.exe > knows about this key? yup, I was following https://bugzilla.mozilla.org/show_bug.cgi?id=701087#c1 BTW, it seems like the cert is valid only for 3 months. Let me know if I should regenerate it with different command line parameters.
Assignee | ||
Comment 3•12 years ago
|
||
I think it would be best to generate in the past that way nothing will change after 3 months. We do not use the expiry aspect of the cert. CCing bsmith and catlee in case they disagree with what I proposed.
Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Brian R. Bondy [:bbondy] from comment #3) > I think it would be best to generate in the past that way nothing will > change after 3 months. We do not use the expiry aspect of the cert. CCing > bsmith and catlee in case they disagree with what I proposed. Great idea. Attached is a public key generated 2011-09-24 (4 months ago).
Attachment #591197 -
Attachment is obsolete: true
Reporter | ||
Comment 5•12 years ago
|
||
Comment on attachment 591258 [details]
release MAR signing public key
Typo in the subject, will regenerate. sorry for the nose.
Attachment #591258 -
Attachment is obsolete: true
Reporter | ||
Comment 6•12 years ago
|
||
The correct one. I hope :)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → netzen
Assignee | ||
Comment 7•12 years ago
|
||
Thanks for the cert Rail, we need a secondary cert as well though. The secondary cert won't be used initially, but it should be kept in a safe place in case we ever need to use it. Please attach another for that.
Assignee | ||
Comment 8•12 years ago
|
||
I included the first cert in Bug 704285, I still the second one though.
Reporter | ||
Comment 9•12 years ago
|
||
Assignee | ||
Comment 10•12 years ago
|
||
I included these certs inside the patch in bug 704285. I'm going to mark this as resolved.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•