-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keys should not verify revoked email addresses #12486
Conversation
Fix go-gitea#6778 Signed-off-by: Andrew Thornton <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #12486 +/- ##
==========================================
+ Coverage 43.73% 43.75% +0.01%
==========================================
Files 631 631
Lines 69871 69873 +2
==========================================
+ Hits 30560 30570 +10
+ Misses 34352 34348 -4
+ Partials 4959 4955 -4
Continue to review full report at Codecov.
|
I think we need to double check against what GH does for revoked IDs. There's an issue with the way GH uses git signatures here - it uses them as committer verification and therefore a signature matching a revoked email address is not necessarily incorrect. Looks like this PR replicates this behaviour: and is therefore correct. |
Backport go-gitea#12486 Fix go-gitea#6778 Signed-off-by: Andrew Thornton <[email protected]>
It's worth noting that this will only result in non-verification if and only if the key does not match any other email address for the user. (Remember that Signature Verification in Gitea does not currently match Github - Github's signature verification is only committer verification we have a slightly different model.) |
Backport #12486 Fix #6778 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
When adding gpg keys, if the identity has been revoked do not match it with email addresses.
Fix #6778
Signed-off-by: Andrew Thornton [email protected]