GPG Guide #289
aceforeverd
started this conversation in
Show and tell
GPG Guide
#289
Replies: 0 comments 9 replies
-
Chen22: 5EAE89C255C79CC0 |
Beta Was this translation helpful? Give feedback.
7 replies
-
for those who has problem still, maybe checkout external resource like |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
This is a tutorial in order to help following gpg commit convention in 4paradigm/rfcs
What is gpg
According to the official website:
Install
brew install gnupg
gnupg
from your package managerBasic Config
gnupg's default locate at $HOME/.gnupg, you may generate some default config via
you may interest in the file
~/.gnupg/gpg.conf
,~/.gnupg/gpg-agent.conf
Generate GPG Key
run:
follow the instruction and offer your name, email and expire date, default option should be fine.
note the email you provided must be one GitHub knows, checkout your emails in settings/email
you can check your gpg key via:
Export public key
run:
user-id can be your email or key fingerprint
Enable GPG in GitHub
go to
settings > SSH and GPG Keys
, copy the public key context and add to gpg keys section.You may like GitHub's GPG Tutorial
Enforce GPG Sign in Git
run
git config --global commit.gpgsign true
If you have multiple keys, you can specify the sign key via
try git commit in your code and push, GitHub should know you :)
Send/Receive Keys
One important usage of GPG is the web of trust. You can export you key to gpg servers, then everybody on web can receive your public key without contact directly
to share:
to receive:
you can pass the extra
--keyserver <server address>
to send/receive key to/from that key server.Share your key :-)
aceforeverd: CE4AA0AE5B7E8112
Upcomming
Some References
Beta Was this translation helpful? Give feedback.
All reactions