Closed Bug 677701 Opened 13 years ago Closed 13 years ago

setup automated monitoring of RelEng Authenticode and GPG keys

Categories

(Release Engineering :: Release Automation, defect, P5)

Product:
Release Engineering
Component:
Release Automation
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 673303

People

(Reporter: joduinn, Unassigned)

Details

Recently, the GPG key expired during a release, because I forgot to add GPG key expiry to my personal calendar reminder. Instead of relying on my personal calendars, we should setup automated (nagios?) monitoring of the Authenticode and GPG keys used by Mozilla Corp. I believe warnings about expiring keys should be sent to entire RelEng group with 1?2? months advance notice so we have time to regen new keys.
See also bug 673303, don't think we need both.
Status: NEW → RESOLVED
Closed: 13 years ago
Component: Release Engineering → Release Engineering: Automation (Release Automation)
QA Contact: release → bhearsum
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.