Accept ? or ! or % as validity for expired/invalid sigs (see T7547)#16
Open
dkg wants to merge 1 commit intobestpractical:masterfrom
Open
Accept ? or ! or % as validity for expired/invalid sigs (see T7547)#16dkg wants to merge 1 commit intobestpractical:masterfrom
dkg wants to merge 1 commit intobestpractical:masterfrom
Conversation
https://dev.gnupg.org/T7547 contains discussion about shifting expectations for the validity field for expired signatures. In 2.4, which considers these expired signatures using SHA1 as too weak, it emits '%' for the validity field. For flexibility, accept all three variants, in accordance with GnuPG upstream wishes.
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.
https://dev.gnupg.org/T7547 contains discussion about shifting expectations for the validity field for expired signatures.
In 2.4, which considers these expired signatures using SHA1 as too weak, it emits '%' for the validity field.
For flexibility, accept all three variants, in accordance with GnuPG upstream wishes.