SSH is a cryptographic network protocol for operating network services securely over an unsecured network. The standard TCP port for SSH is 22. The best known example application is for remote login to computer systems by users.
SSH provides a secure channel over an unsecured network in a client-server architecture, connecting an SSH client application with an SSH server. Common applications include remote command-line login and remote command execution, but any network service can be secured with SSH. The protocol specification distinguishes between two major versions, referred to as SSH-1 and SSH-2.
The most visible application of the protocol is for access to shell accounts on Unix-like operating systems, but it sees some limited use on Windows as well. In 2015, Microsoft announced that they would include native support for SSH in a future release.
SSH was designed as a replacement for Telnet and for unsecured remote shell protocols such as the Berkeley rlogin, rsh, and rexec protocols. Those protocols send information, notably passwords, in plaintext, rendering them susceptible to interception and disclosure using packet analysis. The encryption used by SSH is intended to provide confidentiality and integrity of data over an unsecured network, such as the Internet.
VyOS 1.1 supported login as user
root. This has been removed due
to tighter security in VyOS 1.2.
Enabling SSH only requires you to specify the port
<port> you want SSH to
listen on. By default, SSH runs on port 22.
Specify IPv4/IPv6 listen address of SSH server. Multiple addresses can be defined.
Define allowed ciphers used for the SSH connection. A number of allowed ciphers can be specified, use multiple occurrences to allow multiple ciphers.
List of supported ciphers:
Disable password based authentication. Login via SSH keys only. This hardens security!
Disable the host validation through reverse DNS lookups - can speedup login time when reverse lookup is not possible.
Specifies the available MAC algorithms. The MAC algorithm is used in protocol version 2 for data integrity protection. Multiple algorithms can be provided.
List of supported MACs:
Add access-control directive to allow or deny users and groups. Directives
are processed in the following order of precedence:
Specify timeout interval for keepalive message in seconds.
Specify allowed KEX algorithms.
List of supported algorithms:
sshd log level. The default is
Protects host from brute-force attacks against SSH. Log messages are parsed, line-by-line, for recognized patterns. If an attack, such as several login failures within a few seconds, is detected, the offending IP is blocked. Offenders are unblocked after a set interval.
Whitelist of addresses and networks. Always allow inbound connections from these systems.
Block source IP in seconds. Subsequent blocks increase by a factor of 1.5 The default is 120.
Remember source IP in seconds before reset their score. The default is 1800.
Restart the SSH daemon process, the current session is not affected, only the background daemon is restarted.
Re-generated the public/private keyportion which SSH uses to secure connections.
Already learned known_hosts files of clients need an update as the public key will change.
Re-generated a known pub/private keyfile which can be used to connect to other services (e.g. RPKI cache).
[email protected]:~$ generate ssh client-key /config/auth/id_rsa_rpki Generating public/private rsa key pair. Your identification has been saved in /config/auth/id_rsa_rpki. Your public key has been saved in /config/auth/id_rsa_rpki.pub. The key fingerprint is: SHA256:XGv2PpdOzVCzpmEzJZga8hTRq7B/ZYL3fXaioLFLS5Q [email protected] The key's randomart image is: +---[RSA 2048]----+ | oo | | ..o | | . o.o.. o.| | o+ooo o.o| | Eo* =.o | | o = +.o*+ | | = o *.o.o| | o * +.o+.+| | =.. o=.oo| +----[SHA256]-----+
Two new files
will be created.
Generate the configuration mode commands to add a public key for Key Based Authentication.
<location>can be a local path or a URL pointing at a remote file.
Supported remote protocols are FTP, FTPS, HTTP, HTTPS, SCP/SFTP and TFTP.
[email protected]:~$ generate public-key-command user alyssa path sftp://example.net/home/alyssa/.ssh/id_rsa.pub # To add this key as an embedded key, run the following commands: configure set system login user alyssa authentication public-keys [email protected] key AAA... set system login user alyssa authentication public-keys [email protected] type ssh-rsa commit save exit [email protected]:~$ generate public-key-command user ben path ~/.ssh/id_rsa.pub # To add this key as an embedded key, run the following commands: configure set system login user ben authentication public-keys [email protected] key AAA... set system login user ben authentication public-keys [email protected] type ssh-dss commit save exit