How to Log in to SSH Server with GPG Key

This practical guide walks through how to log in to SSH Server with GPG Key. It organizes the required steps, settings, and checks so you can complete the task with fewer mistakes.

Prepare GPG key for SSH

The first step when using GPG keys on SSH is to create a new subkey. Doing this will allow SSH authentication details to be shared without affecting your main GPG identity.

Start by opening the GPG prompt for the master key:

gpg --expert --edit-key YOUR-KEY@EMAIL.ADDRESS

Note : You can find the email address for your master key by listing the key's contents: Gpg --list-keys .

Type 'addkey' On the GPG prompt, select '8' , then choose Enter.

Set the subkey capability to '=A' Then choose Enter.

Enter '4096' In the key size prompt, then choose Enter .

Set a reasonable time period for subkey validity. In this case, the example would be typing '1y' To make the new subkey only valid for one year.

Create a new GPG subkey by typing 'y' , then pressing Enter On the wizard's confirmation prompt.

Type 'quit' , then choose Enter To exit the GPG prompt.

Confirm that the new subkey is working properly by getting details about the master key:

gpg --list-keys YOUR-KEY@EMAIL.ADDRESS

Enable SSH Support in GPG

Once the subkey is up and running, you can now configure your SSH daemon to accept incoming gpg-agent requests. To do that, add 'enable-ssh-support' To the current user's 'gpg-agent. conf' file:

echo "enable-ssh-support" >> ~/.gnupg/gpg-agent.conf

Open the '. bashrc' file with your favorite text editor:

nano ~/.bashrc

Paste the following lines of code at the end of the. bashrc file:

export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket)
gpgconf --launch gpg-agent

Save the bashrc file, then print the subkey's keygrip:

gpg --list-keys --with-keygrip

Copy the subkey's keygrip, then create the file 'sshcontrol' in the. gnupg Directory:

nano ~/.gnupg/sshcontrol

Paste your identity keygrip into the new file, then save it.

Apply the new SSH and GPG configuration by reloading the bashrc file on the current terminal session:

source ~/.bashrc

Check if the SSH daemon is currently working properly by listing its SSH public key:

ssh-add -l

Export and Check GPG Key

At this point, you should have the SSH daemon correctly linked to your GPG agent. To use it, generate an SSH export key with the following command:

gpg --ssh-export-key YOUR-KEY@EMAIL.ADDRESS > ~/authorized_keys

Set the export key's permission bits to be readable and writable only by the user:

chmod 600 ~/authorized_keys

Send new authorization file to remote server using scp:

scp ~/authorized_keys YOUR-REMOTE.SERVER.DOMAIN:~/.ssh/authorized_keys

Log in to the remote server, then restart the SSH daemon to apply the new key:

sudo systemctl restart ssh.service

Select Ctrl + D , then log back into the remote SSH server. This will bring up a new prompt asking to enter the master GPG key password.

Binding a GPG key to the SSH daemon and exporting it to a remote server are just some of the things you can do with SSH. Discover what can be done with this amazing software using SSH with UNIX pipes in Linux.