This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2019-10-16. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise.For help with the upgrade, contact GitHub Enterprise support.
Jan 18, 2012 We need to setup this PGP in our SAP PI 730 system. What is difference between Generating Key Pairs and Generate ASCII Armored Keys from GPG Keys? Do we need to login to server where we have installed on PI and generate key with Gpg4win? What if we have HA PI 730 system, Do we need to generate on both the nodes of HA system? GnuPG uses public-key cryptography so that users may communicate securely. In a public-key system, each user has a pair of keys consisting of a private key and a public key. A user's private key is kept secret; it need never be revealed. The public key may be given to anyone with whom the user wants to communicate.
If you don't have an existing GPG key, you can generate a new GPG key to use for signing commits and tags.
GitHub Enterprise supports several GPG key algorithms. If you try to add a key generated with an unsupported algorithm, you may encounter an error.
Note: Before generating a new GPG key, make sure you've verified your email address. If you haven't verified your email address, you won't be able to sign commits and tags with GPG.
Download and install the GPG command line tools for your operating system. We generally recommend installing the latest version for your operating system.
Open TerminalTerminalGit Bashthe terminal.
Generate a GPG key pair. Since there are multiple versions of GPG, you many need to consult the relevant man page to find the appropriate key generation command. Your GPG key must use RSA with a key size of 4096 bits.
If you are on version 2.1.17 or greater, paste the text below to generate a GPG key pair.
If you are not on version 2.1.17 or greater, the gpg --full-generate-key command doesn't work. Paste the text below and skip to step 6.
At the prompt, specify the kind of key you want, or press Enter to accept the default RSA and RSA.
Enter the desired key size. We recommend the maximum key size of 4096.
Enter the length of time the key should be valid. Press Enter to specify the default selection, indicating that the key doesn't expire.
Verify that your selections are correct.
Enter your user ID information.
Note: When asked to enter your email address, ensure that you enter the verified email address for your GitHub account.

Type a secure passphrase.
Use the gpg --list-secret-keys --keyid-format LONG/easeus-data-recovery-wizard-108-license-key-generator.html. command to list GPG keys for which you have both a public and private key. A private key is required for signing commits or tags.
Note: Some GPG installations on Linux may require you to use gpg2 --list-keys --keyid-format LONG to view a list of your existing keys instead. In this case you will also need to configure Git to use gpg2 by running git config --global gpg.program gpg2.
From the list of GPG keys, copy the GPG key ID you'd like to use. In this example, the GPG key ID is 3AA5C34371567BD2:
Paste the text below, substituting in the GPG key ID you'd like to use. In this example, the GPG key ID is 3AA5C34371567BD2:
Copy your GPG key, beginning with -----BEGIN PGP PUBLIC KEY BLOCK----- and ending with -----END PGP PUBLIC KEY BLOCK-----.
Add the GPG key to your GitHub account.
