Loading...
10-1
10. SSH Encryption
In addition to standard Telnet protocol, the RPC also supports SSH connections, which
provide secure, encrypted access via network. In order to communicate with the RPC
using SSH protocol, your network node must include an appropriate
SSH client.
Note that when the /K (Send SSH Key) command is invoked, the RPC can also provide
you with a public SSH key, which can be used to streamline connection to the RPC
when using SSH protocol.
Although you can establish an SSH connection to the unit without the public key,
the public key provides validation for the RPC, and once this key is supplied to the
SSH client, the client will no longer display a warning indicating that the RPC is not a
recognized user when the client attempts to establish a connection.
The /K command uses the following format:
/K <k> [Enter]
Where k is an argument that determines which type of public key will be displayed, and
the k argument offers the following options:
1. SSH1
2. SSH2 RSA
3. SSH2 DSA
For example, to obtain the public SSH key for an SSH2 RSA client, type /K 2 and then
press [Enter]. Note that when capturing the SSH key, you can either configure your
terminal application to receive the parameter file, or simply copy and paste the resulting
SSH key.
Notes:
• AlthoughtheRPCdoesnotsupportSSH1,the/K1commandwillstillreturna
keyforSSH1.
• WhencapturingtheSSHkey,youcaneitherconfigureyourterminal
application to receive the parameter file, or simply copy and paste the
resultingkey
Loading...
Terms of Use | Privacy Policy | DMCA Policy
2006-2020 Rsmanuals.com