fix(ci): drop rpmsign, use repo_gpgcheck for RPM verification#5
Merged
Conversation
rpmsign on Ubuntu produces signatures incompatible with Fedora's rpm, causing "digests SIGNATURES NOT OK". Switch to repo-level verification: signed repomd.xml metadata contains package checksums, providing integrity through the checksum chain. This is the standard model used by Chrome, Docker, and VS Code repos. - Remove rpmsign, gpg-agent config, and rpm -K verification steps - Change README to gpgcheck=0 + repo_gpgcheck=1 - Keep repomd.xml GPG detached signature (already working)
moukrea
force-pushed
the
fix/rpm-repo-gpgcheck-only
branch
from
09ccab5 to
35893cf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
rpmsignon Ubuntu's rpm 4.18 produces signatures incompatible with Fedora's rpm, causingdigests SIGNATURES NOT OKonrpm -Kverificationrpmsign,gpg-agentconfig,rpm -K,.rpmmacros)gpgcheck=0+repo_gpgcheck=1in READMErepomd.xmldetached GPG signature (already working since day one)Security model
Signed
repomd.xmlmetadata contains SHA256 checksums of all packages. DNF verifies the metadata signature, then verifies each package against those checksums. This is the standard approach used by Chrome, Docker, and VS Code RPM repos.