Configuration Guide SSH Terminal Service Configuration
For details of the above commands, see SSH Command Reference Manual.
Configuring SSH Public-Key Based Authentication
According to the SSH protocol, only SSHv2 supports public-key based
authentication. Run the following commands to associate the public-key file with
the user name on a client. During client login authentication, the public-key file
is specified by using the user name.
Ruijie# configure terminal
Enter the configuration mode.
Ruijie(config)# ip ssh peer test
public-key rsa flash:rsa.pub
Set the RSA public-key file associated with the user
test.
Ruijie(config)# ip ssh peer test
public-key dsa flash:dsa.pub
Set the DSA public-key file associated with the user
test.
Configuring the SCP Server Function
With the SCP server enabled on a network device, the user can directly
download files from the network device and upload local files to the network
device. Meanwhile, the user can transfer all interactive data in encrypted text
manner, featuring authentication and security.
Ruijie# configure terminal
Enter the configuration mode.
Ruijie(config)#ip scp server enable
Enable the SCP server function.
Ruijie(config)# no ip scp server enable
Disable the SCP server function.
Using SSH for Device Management
You may use the SSH for device management by first enabling the SSH Server
function that is disabled by default. Since the Telnet that comes with the
Windows does not support SSH, third-party client software has to be used.
Currently, the clients with sound forward compatibility include Putty, Linux and
SecureCRT. With the client software SecureCRT as an example, the SSH client
configuration is described as follows (see the UI below):
Figure-1