Difference between revisions of "Generating a new GPG key"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
* https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key?platform=linux | * https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key?platform=linux | ||
| + | |||
| + | |||
* <code>[[gpg --full-generate-key]]</code> | * <code>[[gpg --full-generate-key]]</code> | ||
Revision as of 11:17, 4 July 2024
gpg --full-generate-keygpg --list-secret-keys --keyid-format=longgpg --armor --exportgpg --export --armor [email protected] > public_key.asc
gpg --encrypt --recipient [email protected] file.txt
Note: When asked to enter your email address, ensure that you enter the verified email address for your GitHub account. To keep your email address private, use your GitHub-provided no-reply email address. For more information, see "Verifying your email address" and "Setting your commit email address."
Related
See also
gpg, --batch | --generate-key | --full-generate-key | --recv-keys | --export | --encrypt | --import | --list-keys | --list-secret-key | --gen-key | --armor | --dearmor | --send-keys | --search-keys | --quick-set-expire | --keyserver | --delete-keys | --full-generate-key | --armor --export | gpg --help- GNU Privacy Guard (GPG),
gpg, gpg-agent, gpg-suite, GPGAuth,gpg --help,~/.gnupg/
Advertising:
