Enabling and Restricting SSH Access
SSH access to the VPN Gateway is disabled by default. However, depending on the severity
of your security policy, you may want to enable SSH access. You may also restrict SSH access
to one or more specific machines.
For more information about how to enable SSH access, see the
ssh
command in the
"Administrative Applications Configuration " section under Configuration Menu>System
Configuration in the
Command Reference
. For more information about how to restrict SSH
access to one or more specific machines, see the add command in the "System Access
Configuration " section in the same chapter.
Running an SSH Client
Connecting to the VPN Gateway using a SSH client is similar to connecting through Telnet.
As with Telnet, the IP parameters on the VPN Gateway need to be configured in advance and
SSH access must be enabled. After providing a valid user name and password, the command
line interface in the VPN Gateway is accessible the same way as when using a Telnet client.
However, because a secured and encrypted communication channel is set up even before the
user name and password is transmitted, all traffic sent over the network while configuring or
collecting information from the VPN Gateway is encrypted. For information about different user
accounts and default passwords, see
Accessing the AVG Cluster
on page 126.
During the initial setup of the VPN Gateway(s), you are provided with the choice to generate
new SSH host keys. It is recommended that you do so, to maintain a high level of security
when connecting to the VPN Gateway using a SSH client. If you fear that your SSH host keys
have been compromised, you can create new host keys at any time by using the
/cfg/sys/
adm/sshkeys/generate
command. When reconnecting to the VPN Gateway after having
generated new host keys, your SSH client will display a warning that the host identification (or
host keys) has been changed.
Accessing the AVG Cluster
To enable better AVG management and user accountability, five categories of users can
access the AVG cluster:
• Operator is only granted read access to the menus and information appropriate to this
user access level. The Operator cannot make any changes to the configuration.
• Administrator can make any changes to the AVG configuration. Thus, the Administrator
has read and write access to all menus, information and configuration commands in the
AVG software.
• A Certificate Administrator is a member of the certadmin group, and has sufficient user
rights to manage certificates and private keys. By default, only the Administrator user is
The Command Line Interface
126 User Guide
April 2013
Comments? infodev@avaya.com
Summary of Contents for 3050-VM
Page 1: ...User Guide Avaya VPN Gateway Release 9 0 NN46120 104 Issue 04 04 April 2013 ...
Page 4: ...4 User Guide April 2013 Comments infodev avaya com ...
Page 12: ...12 User Guide April 2013 ...
Page 20: ...New in this release 20 User Guide April 2013 Comments infodev avaya com ...
Page 30: ...Introducing the VPN Gateway 30 User Guide April 2013 Comments infodev avaya com ...
Page 36: ...Introducing the ASA 310 FIPS 36 User Guide April 2013 Comments infodev avaya com ...
Page 74: ...Upgrading the AVG Software 74 User Guide April 2013 Comments infodev avaya com ...
Page 86: ...Managing Users and Groups 86 User Guide April 2013 Comments infodev avaya com ...
Page 130: ...The Command Line Interface 130 User Guide April 2013 Comments infodev avaya com ...
Page 162: ...Supported Ciphers 162 User Guide April 2013 Comments infodev avaya com ...
Page 212: ...Syslog Messages 212 User Guide April 2013 Comments infodev avaya com ...
Page 242: ...Definition of Key Codes 242 User Guide April 2013 Comments infodev avaya com ...
Page 259: ...Creating a Port Forwarder Authenticator User Guide April 2013 259 ...
Page 266: ...Using the Port Forwarder API 266 User Guide April 2013 Comments infodev avaya com ...
Page 274: ...X 509 274 User Guide April 2013 Comments infodev avaya com ...