feat(main/termux-keyring): add thunder-coding's PGP keys #25031
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
thunder-coding
requested review from
agnostic-apollo,
landfillbaby,
kcubeterm,
2096779623 and
MrAdityaAlok
thunder-coding
force-pushed
the
keyring-add-thunder-coding
branch
from
d41f30c to
00e1512
Compare
Maxython
changed the title
|
You need to use binary format for key. |
I was postponing this till I migrate to newer keys. It seems like finally I forced myself to do it. This only contains my newer PGP keys, as my older key is not recommended to be used, although available on my website, it's just available for historic reasons.
thunder-coding
force-pushed
the
keyring-add-thunder-coding
branch
from
00e1512 to
4d31e7c
Compare
TomJo2000
approved these changes
Jul 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I was postponing this till I migrate to newer keys. It seems like finally I forced myself to do it. This only contains my newer PGP keys, as my older key is not recommended to be used, although available on my website, it's just available for historic reasons.
For more information including signed message confirming the authenticity of the new key see: https://thunders.website/posts/2025-06-13-update-to-my-gpg-keys/