Closed Bug 710200 Opened 13 years ago Closed 8 years ago

Signed release deliverables should be verified

Categories

(Release Engineering :: Release Automation: Other, defect, P3)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: rail, Unassigned)

References

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2154] [releases][automation][signing]) 

Since we're going to obsolete signing procedure as a separate process, we'll need to implement signing sanity checks for all signed deliverables. This includes internal and external signature checks, integrity checks using checksums (MD5SUMS and SHA1SUMS) files.
OS: Linux → All
Priority: -- → P3
Hardware: x86_64 → All
Found in triage.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
QA Contact: bhearsum
Product: mozilla.org → Release Engineering
Whiteboard: [releases][automation][signing] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2144] [releases][automation][signing]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2144] [releases][automation][signing] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2153] [releases][automation][signing]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2153] [releases][automation][signing] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2154] [releases][automation][signing]
Let's kill this because:

* we run update verify tests which rely on signed binaries on Windows (and Mac?)
* chain of trust will make everything perfect! :)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.