Are you tired of trying to memorize tons of passwords on different systems? Or do you simply want to have a faceless user SSH between two systems without being asked for a password? Well you are in luck because today we will be covering SSH keys.
SSH Servers have the ability to authenticate users using public/private keys. In the case of pass-phrase less keys this allows users to ssh from one system to another without typing a password.
This is great for faceless users or any lazy "people" users that don't feel like typing in their passwords when they connect to systems over ssh.
Generate the Private and Public Keys
To generate the SSH keys we will be using the ssh-keygen command. This command will generate an RSA public and private key. The ssh-keygen command will also support DSA keys. I will leave the discussion of RSA vs DSA for other places.
[email protected]:~$ ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/home/madflojo/.ssh/id_rsa): Created directory '/home/madflojo/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/madflojo/.ssh/id_rsa. Your public key has been saved in /home/madflojo/.ssh/id_rsa.pub. The key fingerprint is:
ssh-keygen will create a directory
.ssh,as well as two files
.ssh/id_rsa.pub. The first file
id_rsa is the private key that will stay only on the local system, that we will authenticate from. The second file
id_rsa.pub is the public key and the contents of this key will be dispersed to a remote system for key based authentication.
Configure the Remote Server
Creating a .ssh directory
On the remote system you may and may not already have a .ssh directory; if it already exists you can skip this step.
[email protected]:~# mkdir .ssh [email protected]:~#chmod 700 .ssh [email protected]:~#chown youruser:yourgroup .ssh
Pay close attention to the permissions on this directory. Key based authentication will not work if the permissions on the .ssh directory are not correct.
Append the public key to the authorized_keys file
Now that the directory is created we will put the public key information into the authorized_keys file on the remote system.
The below instructions are on two different systems so pay attention to the hostname.
[email protected]:~# cat .ssh/id_rsa.pub Copy the output [email protected]:~$ vi .ssh/authorized_keys Append the public key
At this point you should be able to ssh from local-server to remote-server using your ssh keys to authenticate.
Check the appropriate log files
If key based authentication is not working the best place to start troubleshooting is the log files. For Debian/Ubuntu based distributions the authentication logs are in
/var/log/auth.log. For Red Hat based distributions the authentication logs are in
Usually, I find it is due to permissions on the .ssh directory.
Check the sshd_config file
On most Linux distributions SSH servers have Public Key Authentication enabled by default. If you are having problems getting this to work make sure you un-comment the below lines in the
# vi /etc/ssh/sshd_config RSAAuthentication yes PubkeyAuthentication yes AuthorizedKeysFile %h/.ssh/authorized_keys
AuthorizedKeysFile line may be different depending on your distribution but it should be pointing to
.ssh/authorized_keys in the users home directory.
Recently Benjamin published his first book; Red Hat Enterprise Linux Troubleshooting Guide. In addition to writing, he has several Open Source projects focused on making Ops easier. These projects include Automatron, a project enabling auto-healing infrastructure for the masses.
Identify, capture and resolve common issues faced by Red Hat Enterprise Linux administrators using best practices and advanced troubleshooting techniques
What people are saying:
Excellent, excellent resource for practical guidance on how to troubleshoot a wide variety of problems on Red Hat Linux. I particularly enjoyed how the author made sure to provide solid background and practical examples. I have a lot of experience on Red Hat but still came away with some great practical tools to add to my toolkit. - Amazon Review