If the purpose is to create a backup key, you should use the backup option: gpg -output backupkeys.pgp -armor -export -export-options export-backup user@email This will export all necessary information to restore the secrets keys including the trust database information. This command generates a key pair that consists of a public and a private key. Other people use your public key to authenticate and/or decrypt your communications. Distribute your public key as widely as possible, especially to people who you know will want to receive authentic communications from you, such as a mailing list. Gpg -import private.key If the key already existed on the second machine, the import will fail saying 'Key already known'. To force import, you will have to delete both the private and public key first (gpg -delete-keys and gpg -delete-secret-keys)Enigmail / GnuPG v2. Apr 04, 2017 It is based on the use of a pair of keys, one public and one private (or secret). Data encrypted with one key can only be decrypted with the other. To encrypt a message to you, someone would use your public key to create a message that could only be unlocked with your private key. Delete public key from Private for Private key storage with GPG. Ask Question Asked 4 years, 9 months ago. QR codes are big enough for a single 4096 bit key, but not for both the private and the public key (which is automatically included with the private key).

• Gpg Add Public Key
• Gpg Generate Public Key From Private Key
• Generate Public Key From Private Key Gpg Download
• Gpg Create Public Key
• Generate Public Key From Private Key Gpg File

Fortunately a private key has the same fingerprint as its corresponding public key so we can just use the number we already found to export it. Now, for backing up private keys, there are two options (and you might want to do them both): a digital key or a paper key. Now you should make a backup of your private key. Creating GPG Keys Using the Command Line. Use the following shell command: gpg2 -full-gen-key This command generates a key pair that consists of a public and a private key. Other people use your public key to authenticate and/or decrypt your communications.

A lost SSH public-key or a web service generates an SSH key but does not provide the public-key part to you. What to do now? There is a solution for this situation.

When you have an SSH key you need the public key to setup SSH passwordless login with SSH-key. But if you have lost the public key part but still have the private key, there is a way to regenerate the key.

With the public key missing, the following command will show you that there is no public key for this SSH key.

The -l option instructs to show the fingerprint in the public key while the -f option specifies the file of the key to list the fingerprint for.

To generate the missing public key again from the private key, the following command will generate the public key of the private key provided with the -f option.

The -y option will read a private SSH key file and prints an SSH public key to stdout. The public key part is redirected to the file with the same name as the private key but with the .pub file extension. If the key has a password set, the password will be required to generate the public key.

To check the details of the generated public key execute the following command as shown above.

The output of this command shows the key size as the first column, the fingerprint as the second column and after the file name, the type is shown in brackets. In the example above, a 4096 bit RSA key.

Read more of my posts on my blog at http://blog.tinned-software.net/.

Updated by Alex FornutoContributed byHuw Evans

Report an Issue View File Edit File

You may be familiar with public key authentication for Secure Shell (SSH) on your Linode. But you may not have known that you can also use a GNU Privacy Guard (GPG) keypair to authenticate with SSH.

The chief benefit of this method is that instead of having separate keys for GPG messaging and SSH authentication, they can both belong to the same GPG keyring. This configuration really shines, however, when used with a GPG smartcard or YubiKey, because the card/dongle can store the underlying private key and only authenticate SSH sessions when it’s plugged in. WIRED reported that engineers at Facebook use this method for authenticating with local servers, so why shouldn’t you?

This guide will show you how to generate a GPG key, set up your computer to serve it in place of an SSH key, and put the new public key onto your server for authentication. It will also detail how to optionally move your GPG private key onto a smartcard or YubiKey to prevent authentication when the device isn’t plugged into your computer.

Before You Begin

This guide assumes:

• You have a fully functional Linode
• You have followed the Getting Started and Securing Your Server guides, and updated your Linode with sudo apt-get update && sudo apt-get upgrade)
• You are familiar with the command line

You don’t necessarily need to be familiar with SSH public key authentication or GPG encryption, but an understanding of their operation will help you out if you run into problems.

Generate a GPG Keypair

This section explains how to generate a new GPG keypair. If you already have one, you may skip these steps, as the next section will include instructions for how to create a subkey to use specifically for authentication. You will just need the 8-digit ID for your existing key to do so.

All of these steps should be performed on a local machine, not your Linode.

1. Install GPG:

   On Debian and its derivatives:

   On OS X:

   GPGTools provides the simplest implementation of GPG for OS X. Otherwise, you could run brew install gnupg2 if you have Homebrew.

   On other operating systems, this process should be fairly clear. GPG is likely already installed, but if it isn’t, a quick internet search should give you the instructions you need.

2. Open a command prompt and execute:

3. When prompted to select the kind of key you want, select (1) RSA and RSA.

4. When asked for a keysize, type 4096. If you want to store your key on a YubiKey Neo or certain smartcards, you may be restricted to a 2048-bit key size, so ensure that you aware of limitations for your device, if applicable.

5. Choose an expiration period that you think will be suitable for this key. After that date, the key will no longer work, so choose carefully.

6. Enter your full name, email address, and a comment (if you want). Select O for ‘Okay’.

7. After looking over your shoulders for secret agents, enter a long and secure passphrase that will be used to encrypt your key in local storage. Write this down somewhere you know to be physically secure while your computer generates the keypair.

Once this is done, your output should resemble the following:

This process has created a master GPG key and a subkey for encrypting messages and files. To authenticate with SSH, we need to generate a second subkey for authentication.

Generating the Authentication Subkey

1. In a command prompt or terminal, type:

   Replace key-id with the eight-character string output from the key generation process. This will be found in the line beginning with pub. In the example above, the ID is 71735D23.

2. At the new gpg> prompt, enter:

3. When prompted, enter your passphrase.

4. When asked for the type of key you want, select: (8) RSA (set your own capabilities).

5. Enter S to toggle the ‘Sign’ action off.

6. Enter E to toggle the ‘Encrypt’ action off.

7. Enter A to toggle the ‘Authenticate’ action on. The output should now include Current allowed actions: Authenticate, with nothing else on that line.

8. Enter Q to continue.

9. When asked for a keysize, choose 4096. The same limitation from Step 4 in the first section applies, so ensure your card/YubiKey can support this key size.

10. Enter an expiration date, just as before. You should probably keep this the same as the first one. If you choose a lower expiration date, your main private key will continue to function but your SSH authentication will break on this date.

11. When you’re sure all of the information entered is correct, enter y at the Really create? (y/N) prompt to complete the process.

12. Once the key is created, enter quit to leave the gpg prompt, and y at the prompt to save changes.

Your terminal should now look like this:

Secure Your GPG Key

You should always have a backup of your private key in case something goes wrong and you end up locked out of everything that requires it. This private key, along with the instructions in this guide, will be enough to get your setup working again if you need to start afresh on a new computer.

1. Back up your ~/.gnupg folder with the following command, replacing USB_DEVICE with the name of your device:

   This assumes you have a storage device mounted at /Volumes/USB_DEVICE/. Different operating systems may use different naming conventions for this path. You can safely ignore any Operation not supported on socket warnings that appear when you enter this command.

2. Back up your private key, replacing key-id with the eight-character key ID for your private key:

3. Back up your subkeys, replacing key-id with the eight-character key ID for each subkey:

If something bad happens and you lose your keys, you can re-import them by overwriting the ~/.gnupg directory with your copy, and using:

Be sure to replace key-file with the location of each of your files.

Export Your Public Key

If you’re working on a VM or offline machine, you’ll also need to export your public key to be reimported later:

Be sure to replace key-id with your own key ID.

You can reimport it with the ever-handy gpg2 --import key-file command.

Move Your Key to a Smartcard or YubiKey (Optional)

Secure Your Card

It is assumed that you have already configured your card/YubiKey’s (herein referred to as ‘GPG device’) owner information. It is highly recommended that you secure your card before you start this section.

1. Plug in the device and execute:

2. Enable admin commands:

3. Enter the password change menu:

4. Change the password to your device by selecting 2 - unblock PIN. This will unblock your PIN, and prompt you to change it. This PIN will be required every time you want to access your GPG key (e.g. every time you authenticate with SSH), and has a limit of eight characters.

5. Change the admin PIN by selecting 3 - change Admin PIN. This PIN is required to make administrative changes, like in step 2, and has a limit of 6 characters. For optimum security, never store this PIN in a digital location, since it will be unnecessary for daily use of the YubiKey.

6. Exit these menus by selecting Q and then typing quit.

For reference, your window should resemble the following. This example is abbreviated:

Transfer Your Subkey

1. Enter the key edit menu from a normal command prompt, replacing key-id with your own key ID:

2. Switch to the private key editor:

3. Select only the authentication subkey:

   Remember, if you have more subkeys this command should be changed as appropriate.

4. Transfer the key:

5. Select (3) Authentication key to store your key on the third slot of the device. If this is not an option, ensure that you’ve selected the appropriate subkey.

6. Enter your passphrase.

7. Type save to exit this menu.

8. If you’re working on a VM or offline machine, export the subkey stubs (pointers so GPG knows your subkeys are on the device):

   Be sure to substitute your own key ID for key-id. You can reimport these with an ordinary gpg2 --import <stub file> on your private machine.

After all this, your output should resemble the following:

Congratulations! You’ve successfully transferred your authentication subkey to your device.

Gpg Add Public Key

Serve Your GPG key Instead of an SSH key

In this section, we’ll configure your local machine so the connection between GPG and SSH works properly.

Return to your local machine, import all of the appropriate GPG keys and insert the appropriate GPG device. Install GPG if you don’t already have it on your local computer (e.g. if you performed all the above steps on a VM).

1. Edit the ~/.bash_profile file (or similar shell startup file) to include:

   Linux:

   ~/.bash_profile

   OS X

   ~/.bash_profile

   This ensures that SSH can ‘see’ your GPG keys and automatically starts gpg-agent as needed.

2. Edit or create ~/.gnupg/gpg-agent.conf:

   ~/.gnupg/gpg-agent.conf

   If you’re on OS X and previously installed GPGTools, you can also add the line:

   This allows you to use the PIN entry program provided by GPGTools.

3. Restart the GPG agent:

Gpg Generate Public Key From Private Key

Add the New Key to Your Linode

Generate Public Key From Private Key Gpg Download

The steps from the previous sections will take your GPG keys and pipe them through SSH so they can be used for authentication. The result of this process is that you’ve created a new RSA public key for use with SSH authentication.

1. On your local machine, extract the public key:

   You should see a long output of alphanumeric characters. If you see The agent has no identities, try the steps to restart the GPG agent from above.

2. Copy the whole string of output, including ssh-rsa. If you see multiple strings beginning with ssh-rsa, copy the one that ends with cardno:. It might look like this:

3. Paste this into a new file (for example, ~/gpg-key.pub) and save it.

4. Copy the file to your Linode:

5. Log into your Linode and append the key to the authorized_hosts file:

You’re done! Disconnect, and all new logins should now use your GPG key instead of a passphrase. This SSH key can also be used with GitHub, Bitbucket, other SSH-based Version Control Systems, or anywhere else that accepts SSH keys.

Gpg Create Public Key

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

Join our Community

Generate Public Key From Private Key Gpg File

This guide is published under a CC BY-ND 4.0 license.