Verify the signatures of the MSYS2 and MINGW source archives #52

Closed
opened 2026-10-24 01:41:26 -05:00 by ethan-hann · 0 comments
Owner

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 .sig next 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.

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 `.sig` next 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.
ethan-hann added this to the Later milestone 2026-10-24 01:41:26 -05:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ethan-hann/SavePoint#52
No description provided.