feat(apt): add OpenPGP signature verification for apt repository indices - #255
Open
loosebazooka wants to merge 1 commit into
Open
loosebazooka wants to merge 1 commit into
loosebazooka wants to merge 1 commit into
Conversation
loosebazooka
force-pushed
the
gpg-verify
branch
2 times, most recently
from
August 31, 2026 19:23
fae6790 to
1d95a0b
Compare
thesayyn
reviewed
Sep 1, 2026
thesayyn
reviewed
Sep 1, 2026
loosebazooka
force-pushed
the
gpg-verify
branch
8 times, most recently
from
September 3, 2026 15:04
16a5987 to
c6d64fd
Compare
loosebazooka
marked this pull request as ready for review
September 3, 2026 15:17
loosebazooka
force-pushed
the
gpg-verify
branch
from
September 11, 2026 15:46
c6d64fd to
b5afd0b
Compare
loosebazooka
marked this pull request as draft
September 11, 2026 15:54
loosebazooka
force-pushed
the
gpg-verify
branch
9 times, most recently
from
September 11, 2026 21:07
2c3e68b to
8dcaf0c
Compare
loosebazooka
marked this pull request as ready for review
September 11, 2026 21:10
Contributor
Author
|
oh lemme rebase this. FYI it is a breaking change (required attribute) |
- Verify InRelease / Release.gpg signatures via gpgv or sqv and enforce Release SHA256 checksums on package indices. - Now requiring either gpg_keys or explicit allow_unsigned = True. - Auto-dearmor ASCII-armored .asc keyrings (requires sq or gpg) - A new e2e test for test failure Signed-off-by: Appu <appu@google.com>
loosebazooka
force-pushed
the
gpg-verify
branch
from
September 14, 2026 20:03
8dcaf0c to
2a16644
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
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.
What breaks: Any existing apt.sources_list in a user's MODULE.bazel that does not specify gpg_keys will now fail Bazel evaluation with a clear error message.
How users migrate: Users must do one of two things:
1.. Explicitly opt out of verification: