Admin Guide

Table Of Contents
Chapter 12: Secure Shell
The following sections describe how to use Secure Shell (SSH) to enable secure communications
support over a network for authentication, encryption, and network integrity.
Secure Shell fundamentals
Methods of remote access such as Telnet or FTP generate unencrypted traffic. Anyone that can see
the network traffic can see all data, including passwords and user names. Secure Shell (SSH) is a
client and server protocol that specifies the way to conduct secure communications over a network.
Secure Shell can replace Telnet and other remote login utilities. Secure File Transfer Protocol
(SFTP) can replace FTP with an encrypted alternative.
Note:
If both SSH and SFTP are concurrently active, you have the ability to disable SFTP while
allowing SSH to remain active. For more information, see Disabling SFTP without disabling
SSH on page 170.
VOSS 5.0 introduces Secure CoPy protocol (SCP) which is a secure file transfer protocol. SCP is
used for securely transferring files between a local host and a remote host. SCP is in off state by
default, but you can turn it on when you enable SSH using the boot config flags command in
the global config mode. VOSS supports SCP only as an SCP server, which means that clients can
send files to the VOSS switch or can request files from the switch. Secure CoPy (SCP) can replace
FTP with an encrypted alternative.
Note:
To enable SSH, enable RSA or DSA authentication, or both using command ssh rsa-auth or
ssh dsa-auth.
Secure Shell supports a variety of the different public and private key encryption schemes available.
Using the public key of the host server, the client and server negotiate to generate a session key
known only to the client and the server. This one-time key encrypts all traffic between the client and
the server. The VSP switch supports Secure Shell version 2 (SSHv2).
Note:
Different releases can support different DSA host key, RSA host key, and DSA user key sizes. If
you need to upgrade or downgrade to an earlier release that does not support the same key
size, you must delete all of the keys from the .ssh directory and generate new keys for SSH. For
more information about supported software, see Release Notes for VSP Operating System
Software, NN47227-401.
January 2017 Administering Avaya VSP 7200 Series and 8000 Series 147
Comments on this document? infodev@avaya.com