Add workaround for EOL suites with expired GPG keys #60
Conversation
This file contains 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
For the sake of EOL releases (whose archive keys have often expired), we need a fake `gpgv` substitute that will essentially ignore *just* key expiration. (So we get *some* signature validation instead of using something like `--allow-unauthenticated` or `--force-yes` which disable security entirely instead.) This workaround *only* gets applied when we're doing an EOL build, and only when the APT version is new enough to need it (older APT versions didn't verify that).
|
I've also tested this against |
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.
For the sake of EOL releases (whose archive keys have often expired), we need a fake
gpgvsubstitute that will essentially ignore just key expiration.(So we get some signature validation instead of using something like
--allow-unauthenticatedor--force-yeswhich disable security entirely instead.)This workaround only gets applied when we're doing an EOL build, and only when the APT version is new enough to need it (older APT versions didn't verify that).
This is the last bits needed in
debuerreotypeitself to finally take care of debuerreotype/docker-debian-artifacts#65. With this, I have successfully verified the full reproducibility ofwoody/3.0 throughwheezy/7.0 across two days acrossi386,arm,armel,armhf, andamd64as applicable.