Keys should not verify revoked email addresses#12486
Conversation
Fix go-gitea#6778 Signed-off-by: Andrew Thornton <art27@cantab.net>
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 <art27@cantab.net>
|
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.) |
When adding gpg keys, if the identity has been revoked do not match it with email addresses.
Fix #6778
Signed-off-by: Andrew Thornton art27@cantab.net