Skip to content

fix: don't restore revoked access from the gpg-id files - #15

Open
millaguie wants to merge 1 commit into
lyz-code:mainfrom
millaguie:fix/user-revocation
Open

fix: don't restore revoked access from the gpg-id files#15
millaguie wants to merge 1 commit into
lyz-code:mainfrom
millaguie:fix/user-revocation

Conversation

@millaguie

Copy link
Copy Markdown

When a user's access was revoked, the next reload imported the keys back from the gpg-id file, undoing the revocation. Now an already imported gpg-id file is not merged again, only warned about if it holds keys the access store doesn't know.

Also revoke users matching by key or email, not just by name, and sort the keys when writing the gpg-id files so the output is stable.

Checklist

  • Add test cases to all the changes you introduce
  • Update the documentation for the changes

When a user's access was revoked, the next reload imported the keys back
from the gpg-id file, undoing the revocation. Now an already imported
gpg-id file is not merged again, only warned about if it holds keys the
access store doesn't know.

Also revoke users matching by key or email, not just by name, and sort
the keys when writing the gpg-id files so the output is stable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant