Verify the signatures of the MSYS2 and MINGW source archives #52
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ethan-hann/SavePoint#52
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The release source step pins each MSYS2 and MINGW source archive by SHA-256 (
build/msys2-sources.json). repo.msys2.org and Git for Windows' pacman-repo releases also publish a.signext to each archive. Checking those signatures when the list is generated would show that the pinned hashes came from the packagers, not only that the download matches what was pinned.Done when generating or refreshing the list checks each archive's signature against the MSYS2 and Git for Windows packager keys and fails on a bad one.