GitHub/gpg: Difference between revisions
< GitHub
(→gpg) |
(→gpg) |
||
| Line 13: | Line 13: | ||
gpg --armor --export 3AA5C34371xxx | gpg --armor --export 3AA5C34371xxx | ||
You will probably get an error about being unable to sign if you are in a remote console, to fix this: | You will probably get an error about being unable to sign if you are in a remote console, to fix this: <ref>https://stackoverflow.com/questions/51504367/gpg-agent-forwarding-inappropriate-ioctl-for-device</ref> | ||
export GPG_TTY=$(tty) | export GPG_TTY=$(tty) | ||
Latest revision as of 08:01, 4 February 2024
gpg
Adding a GPG key to your GitHub account - GitHub Docs https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account
Generate key:
gpg --full-generate-key
List keys to get keyID
gpg --list-keys
Export public key by keyID, and save to Github
gpg --armor --export 3AA5C34371xxx
You will probably get an error about being unable to sign if you are in a remote console, to fix this: [1]
export GPG_TTY=$(tty)
If you really hate security, you can remove the passphrase:
gpg --edit-key XXX passwd enter password to unlock then enter empty password twice then save