SSH keys are a way to identify trusted computers, without involving passwords. The steps below will walk you through generating an SSH key and adding the public key to the server. Step 1: Check for SSH Keys First, check for existing SSH keys on your computer. Open Git Bash, Cygwin, or Terminal, etc. If you're unsure whether you already have an SSH key, check for existing keys. If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase. Generating a new SSH key. Open Terminal Terminal Git Bash. Apr 25, 2017  Now you are thinking, what’s good is in the API key and Secret key. My answer is: As the API key and Secret key is not attached to Authentication header, so nobody will be able to decode the authentication keys.So, all issues solved!! Moreover, for each application to be configured to the API, the separate Secret key is generated. Using OpenSSH to generate a key pair. Now continue on your own computer if you are using Linux or any other OS that has OpenSSH. PuTTY users should skip to the next section. Generate a new key pair in a terminal with the next command ssh-keygen -t rsa. The key generator will ask for location and file name to which the key is saved to. After you've checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent. If you don't already have an SSH key, you must generate a new SSH key. If you're unsure whether you already have an SSH key. Getting Your Authorize.Net Transaction Key. To use Credit Card Terminal, you’ll need your Transaction Key for Authorize.Net. If you don’t already have your Transaction Key, you have to get a new one from Authorize.Net.

• Generate Auth Secret Key In Terminal 4
• Secret Key Pokemon

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

Generate Auth Secret Key In Terminal 4

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.

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:

Add the New Key to Your Linode

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.

Secret Key Pokemon

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.

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

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