Skip to content

Latest commit

 

History

History
42 lines (36 loc) · 2.21 KB

checking-for-existing-gpg-keys.md

File metadata and controls

42 lines (36 loc) · 2.21 KB
title intro redirect_from versions topics shortTitle
Checking for existing GPG keys
Before you generate a GPG key, you can check to see if you have any existing GPG keys.
/articles/checking-for-existing-gpg-keys
/github/authenticating-to-github/checking-for-existing-gpg-keys
/github/authenticating-to-github/managing-commit-signature-verification/checking-for-existing-gpg-keys
fpt ghes ghec
*
*
*
Identity
Access management
Existing GPG keys

{% data reusables.gpg.supported-gpg-key-algorithms %}

Note

GPG does not come installed by default on macOS or Windows. To install GPG command line tools, see GnuPG's Download page.

{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.list-keys-with-note %}

  1. Check the command output to see if you have a GPG key pair.

    • If there are no GPG key pairs or you don't want to use any that are available for signing commits and tags, then generate a new GPG key.

    • If there's an existing GPG key pair and you want to use it to sign commits and tags, you can display the public key using the following command, substituting in the GPG key ID you'd like to use. In this example, the GPG key ID is 3AA5C34371567BD2:

      $ gpg --armor --export 3AA5C34371567BD2
# Prints the GPG public key, in ASCII armor format

      You can then add your GPG key to your GitHub account.

Further reading