Add/update newest GPG signing key - #282
Merged
Merged
Conversation
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.
Roughly 4 years ago I attempted to upload a GPG key and use it for signing code related things. I immediately lost access to that key, and it made me re-think my setup, etc.
The revocation for this dead GPG key:
Moving forward, I hopefully have a better process, and have TWO GPG keys. The key presented here will be used for signing tagged releases for monero-lws, and other libraries I am maintaining. This key is cross-signed by mail@leeclagett.com, whose fingerprint is available on Twitter/X, and Yat. My Yat symbol has appeared on git code commits (in the name field), Twitter/X name field, and Github name field.
I can also confirm this key over IRC, Telegram, Matrix, and Reddit if necessary.