About addition of GPG keys to your account
To sign commits associated with your account on GitHub Enterprise Cloud, you can add a public GPG key to your personal account. Before you add a key, you should check for existing keys. If you don't find any existing keys, you can generate and copy a new key. For more information, see Checking for existing GPG keys and Generating a new GPG key.
You can add multiple public keys to your account on GitHub Enterprise Cloud. Commits signed by any of the corresponding private keys will show as verified. Once a commit has been verified, any commits signed by the corresponding private key will continue to show as verified, even if the public key is removed.
To verify as many of your commits as possible, you can add expired and revoked keys. If the key meets all other verification requirements, commits that were previously signed by any of the corresponding private keys will show as verified and indicate that their signing key is expired or revoked.
Supported GPG key algorithms
GitHub Enterprise Cloud supports several GPG key algorithms. If you try to add a key generated with an unsupported algorithm, you may encounter an error.
- RSA
- ElGamal
- DSA
- ECDH
- ECDSA
- EdDSA
When verifying a signature, GitHub Enterprise Cloud extracts the signature and attempts to parse its key ID. The key ID is then matched with keys added to GitHub Enterprise Cloud. Until a matching GPG key is added to GitHub Enterprise Cloud, it cannot verify your signatures.
Adding a GPG key
- In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
- In the "Access" section of the sidebar, click SSH and GPG keys.
- Next to the "GPG keys" header, click New GPG key.
- In the "Title" field, type a name for your GPG key.
- In the "Key" field, paste the GPG key you copied when you generated your GPG key.
- Click Add GPG key.
- If prompted, authenticate to your GitHub account to confirm the action.