This howto describes setting up SSH trust between two servers so that the two servers share the same SSH keys and can log into each other. This makes life convenient when using two servers together as a team for various scenarios including:
This guide can also be used to establish one-way trust.
We will use key-based authentication to establish trust between our servers. It is vital that you protect the private key of the server. By sharing the same key between the servers, the servers not only trust each other but themselves. This is useful for scripted management tasks.
<note> For this example, the main server is called primary and the secondary server is called backup. </note>
If you already have a key pair on a server, use that pair or overwrite it. You will need a passwordless key-pair. If your current key-pair has a password, you will need to overwrite it for this howto to be useful. If you are happy with your current key-pair, skip this step. On the first server run the following to create a key pair:
ssh-keygen -t rsa
Press <Enter> at the fields to accept the defaults and to leave the password blank. You will get a response like this:
Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa): Created directory '/root/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: 3a:54:d7:77:0b:c7:5b:cb:08:1d:f3:77:30:87:1c:88 email@example.com The key's randomart image is: +--[ RSA 2048]----+ | . =+o.| | E.o B+ | | . ...o.+=| | . . ..=.B| | . S . = | | . . | | o | | . | | | +-----------------+
This command creates a public and a private key pair in the /root/.ssh/ directory:
Now that we have a keypair, we can authorize the server to trust itself. This may seem odd but we can script commands that reference the server itself as well as the other server in the pair. Moreover, we can replicate this trust to the other server and this makes distribution of the trust simple. Run the following:
cat /root/.ssh/id_rsa.pub >> /root/.ssh/authorized_keys
To validate this works, ssh to the local server using the hostname you specified in the /etc/hosts file:
After accepting the fingerprint, it should log you on without specifying a password.
This next step assumes that the trust is limited between the servers you are trusting. Take care using this step if you already have certificates and trust set up on your box. You may need to manually input the entries as the following take a sledgehammer approach for convenience.
We will send all of these files to the other server and for this well will have to supply the password, but just this time. Copy the files to the other server by running the following:
scp -r /root/.ssh* backup:/root/
Your output will look similar to this:
root@backup's password: authorized_keys 100% 406 0.4KB/s 00:00 known_hosts 100% 805 0.8KB/s 00:00 id_rsa.pub 100% 406 0.4KB/s 00:00 id_rsa 100% 1675 1.6KB/s 00:00
Now test out connecting via SSH to each other server. For example:
Both servers should be able to log into one another and also they can issue commands. For example:
hostname && ssh backup hostname
would give the result:
[root@server1 ~]# hostname && ssh backup hostname server1.example.com server2.example.com
This is useful for scripting because you can use one server to execute commands on the other server and you can copy and sync files between the servers securely using certificated authentication. search?q=clearos%2C%20clearos%20content%2C%20app-ssh-server%2C%20clearos5%2C%20clearos6%2C%20clearos7%2C%20category-network%2C%20howto%2C%20maintainer_dloper&btnI=lucky