![Asentria Teleboss 850 Скачать руководство пользователя страница 89](http://html.mh-extra.com/html/asentria/teleboss-850/teleboss-850_user-manual_2981745089.webp)
TeleBoss 850 2.06.280_STD User Manual
Page 83
Secure Shell (SSH) and Secure FTP (SFTP)
The unit offers an SSH client and server. The unit supports SSH version 2 only; SSH version 1 is not supported. SSH
is implemented with OpenSSH_4.3p2 and OpenSSL 0.9.8d. The client is used for the SFTP Push feature. For more
detail on FTP (and SFTP) push, refer to the
The client (
SSH
command) is also usable by any user with at least VIEW rights. This section discusses how to
configure authentication and the login banner for the SSH server on the unit. Note that RADIUS security mode cannot
be used to authenticate SSH connections.
Configuring the SSH server for password authentication
First connect to the unit command processor via a conventional method in a trusted environment (serial port, Telnet,
modem) to make these configuration changes:
1. Generate the host key.
2. Make a user profile with a username and password.
3. Configure network settings.
4. Enable SSH access.
Here are the steps in detail:
1. By default the unit requires password authentication for SSH and does not require public key authentication. To
generate the host key, enter
sshc -ht rsa
(case sensitive) to create 1024-bit RSA host key.
2. Modify one or more of the user profiles (i.e., configure a strong password for the user profile(s)). This is done via
Setup Menu->Security,
sec.user.*
settings, or the Security->User Profiles portion of the Web UI.
3. Configure network settings such that the unit is reachable on your network(s). For more detail on this, refer to the
4. By default SSH access is enabled. To configure whether it is enabled, use the
sec.connectvia.ssh
setting,
also in Setup Menu->Security->General Security, and the Security->General Settings portion of the Web UI.
At this point the unit is ready to receive password-authenticated SSH connections. You can do the same tasks you
can do on a conventional connection, like unit administration and pass-through, only now it is secured by SSH.
Configuring the SSH server for public key authentication
With public key authentication you do not enter a password to authenticate yourself to the unit. Instead you load the
public part of a key bound to your identity onto the unit. In order to use public key authentication:
1. Ensure the unit has a host key.
2. Ensure a user profile is configured with a username and password. Even though the password will not be used
during SSH authentication, a password must be configured for the user profile.
3. Ensure SSH is configured for public key authentication. Do this by setting
sec.ssh.auth.pubkey
= ON. This
overrides password authentication.
4. Ensure an authorized key is loaded on the unit for each client that needs to connect. To load an authorized key,
enter
sshc -ao
(case sensitive). Then simply paste (or send directly via your terminal) the public key of each user.
Terminate loading authorized keys by entering "END" on a line by itself. “END on a line by itself” means you hit enter,
then type END, then hit enter again. It is recommended you do this on an error-correcting connection such as Telnet
or SSH.
At this point the unit is ready to receive public-key-authenticated SSH connections. The user you connect to the unit
as must be configured in a user profile. Also, the public key you use in your SSH client when connecting should be
the one of the authorized keys you load on the unit.
The SSH server on the unit has the following preferred ciphers list:
AES-256,3DES,Blowfish,AES-192,AES-128,[email protected],aes128-ctr,aes192-ctr,aes256-ctr
Содержание Teleboss 850
Страница 6: ......