SSH (Secure SHell) is an encrypted terminal program that replaces the classic telnet tool on Unix-like operating systems.
In addition to remote terminal access provided by the main ssh binary, the SSH suite of programs has grown to include other tools such as scp (secure copy) and sftp (secure file transfer protocol).
Originally, SSH was not free. However, today the most popular and de-facto standard implementation of SSH is OpenBSD's OpenSSH, which comes pre-installed on Gentoo.
- 1 Installation
- 2 Running OpenSSH
- 3 Configuration
- 4 Troubleshooting
- 5 Intrusion prevention
- 6 See also
- 7 External resources
Most deployments of Gentoo Linux will already have OpenSSH installed on the system. This can be checked by running the ssh command. If it is installed a usage statement should be printed:
usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec] [-D [bind_address:]port] [-E log_file] [-e escape_char] [-F configfile] [-I pkcs11] [-i identity_file] [-L [bind_address:]port:host:hostport] [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port] [-Q cipher | cipher-auth | mac | kex | key] [-R [bind_address:]port:host:hostport] [-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]] [user@]hostname [command]
If no usage statement is printed ssh is either corrupted or not installed. It is also possible that a user is simply rebuilding OpenSSH to include a new USE configuration. Whatever the case, proceed on to view possible USE settings.
|USE flag (what is that?)||Default||Recommended||Description|
||No||Disable EC/RC5 algorithms in OpenSSL for patent reasons.|
||No||Enable high performance ssh|
||No||Add support for PAM (Pluggable Authentication Modules) - DANGEROUS to arbitrarily flip|
||No||Add support for TCP wrappers|
||No||Add kerberos support|
||No||Add support for storing SSH public keys in LDAP|
||No||Use the libedit library (replacement for readline)|
||No||!!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur|
||No||Enable S/Key (Single use password) authentication support|
||No||!!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically|
||No||Add support for X11|
||No||Adds support for X.509 certificate authentication|
After changing the necessary USE flags, do not forget to install (or rebuild) OpenSSH:
emerge --ask --changed-use net-misc/openssh
Add openssh to the default runlevel if this has not been done already:
rc-update add sshd default
Start the sshd daemon with:
The OpenSSH server can be controlled like any other OpenRC-managed service:
Active SSH connections to the server remain unaffected when issuing /etc/init.d/sshd restart.
In order to provide a secure shell, cryptographic keys are used to manage the encryption, decryption, and hashing functionalities offered by SSH.
On the first start of the SSH service, system keys will be generated. Keys can be (re)generated using the ssh-keygen command.
Be sure to substitute
<SecretPassphrase>in the following examples with a personal passphrase.
To generate the key used for SSH protocol version 1 (which usually is not enabled anymore; it has been deprecated in favor of protocol version 2) use:
/usr/bin/ssh-keygen -t rsa1 -b 1024 -f /etc/ssh/ssh_host_key -N "<SecretPassphrase>"
To generate the keys for SSH protocol version 2 (DSA and RSA algorithms):
/usr/bin/ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key -N "<SecretPassphrase>"
/usr/bin/ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key -N "<SecretPassphrase>"
The SSH server is usually configured in the /etc/ssh/sshd_config file, though it is also possible to perform further configuration in OpenRC's /etc/conf.d/sshd, including changing the location of the configuration file. For detailed information on how to configure the server see the sshd_config man page.
Users should study Sven's OpenSSH guide for a security focused configuration.
The ssh client and related programs (scp, sftp, etc.) can be configured using the following files:
For more information read the ssh_config manual:
Handy for git server management.
On the client run the following command:
ssh-keygen -t rsa
Generating public/private rsa key pair. Enter file in which to save the key (/home/larry/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/larry/.ssh/id_rsa. Your public key has been saved in /home/larry/.ssh/id_rsa.pub. The key fingerprint is: de:ad:be:ef:15:g0:0d:13:37:15:ad:cc:dd:ee:ff:61 larry@client The key's randomart image is: +--[ RSA 2048]----+ | | | . | | . .. n . | | . (: . . | | o . . : . | | . ..: >.> . | | * ?. . | | o.. .. .. | | :. . ! . | +-----------------+
Make sure an account for the user exists on the server, and then place the clients' id_rsa.pub file into the ~/.ssh/authorized_keys file.
Single machine testing
The above procedure can be tested out locally:
ssh-keygen -t rsa
Generating public/private rsa key pair. Enter file in which to save the key (/home/larry/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: ...
mv ~/.ssh/id_rsa.pub ~/.ssh/authorized_keys
There are 3 different levels of debug modes that can help troubleshooting issues. With the
-v option SSH prints debugging messages about its progress. This is helpful in debugging connection, authentication, and configuration problems. Multiple
-v options increase the verbosity. Maximum verbosity is three levels deep.
ssh example.org -v
ssh example.org -vv
ssh example.org -vvv
Death of long-lived connections
Many internet access devices perform Network Address Translation (NAT), a process that enables devices on a private network such as that typically found in a home or business place to access foreign networks, such as the internet, despite only having a single IP address on that network. Unfortunately, not all NAT devices are created equal, and some of them incorrectly close long-lived, occasional-use TCP connections such as those used by SSH. This is generally observable as a sudden inability to interact with the remote server, even though the ssh client program has not exited.
In order to resolve the issue, OpenSSH clients and servers can be configured to send a 'keep alive', or invisible message aimed at maintaining and confirming the live status of the link.
- To enable keep alive for all clients connecting to your local server, set ClientAliveInterval 30 (or some other value, in seconds) within the /etc/ssh/sshd_config file.
- To enable keep alive for all servers connected to by your local client, set ServerAliveInterval 30 (or some other value, in seconds) within the /etc/ssh/ssh_config file.
X11 forwarding, not forwarding, or tunneling
Problem: After having made the necessary changes to the configuration files for permitting X11 forwarding, it is discovered X applications are executing on the server and are not being forwarded to the client.
Solution: What is likely occurring during SSH login into the remote server or host, the
$DISPLAY variable is either being unset or is being set after the SSH session sets it.
Test for this scenario perform the following after logging in remotely:
The output should be something similar to
localhost2.local:10.0 using server side
X11UseLocalhost no setting. If the usual
:0.0 is not displayed, check to make sure the
$DISPLAY variable within ~/.bash_profile is not being unset or re-initializing. If it is, remove or comment out any custom initialization of
$DISPLAY to prevent the code in ~/.bash_profile from executing during a SSH login:
ssh -t larry@localhost2 bash --noprofile
Be sure to substitute "larry" in the command above with the proper username.
A trick that works to complete this task would be to define an alias within the users' ~/.bashrc file.
SSH is a commonly attacked service. Tools such as sshguard and fail2ban monitor logs and black list remote users who have repeatedly attempted, yet failed to login. Utilized them as needed to secure a frequently attacked system.