System information

Configuring SSH or Bidilink Instead of Telnet for Device Connections
72 AlterPath OnBoard Administrator’s Guide
6. Save the changes.
Configuring SSH or Bidilink Instead of Telnet for
Device Connections
Telnet is not encrypted, so security can only be guaranteed if the service
processors are on a private network. If the service processors must be on the
public network for a pressing reason, then telnet should be replaced with
SSH or bidilink. Instructions on replacing telnet as the connection
method with SSH or bidilink are in the procedure “To Substitute SSH or
bidilink for Telnet for Device Connections” on page 72.”
The root user can configure ssh to be used instead of Telnet on service
processors that support SSH.
An OnBoard administrator who knows the root password and can connect to
the console can follow the instructions in the /etc/libexec/onboard/
ssh_login.exp file to enable ssh access.
T To Substitute SSH or bidilink for Telnet for
Device Connections
1. Log into the OnBoard console as root.
2.
Change to the /libexec/onboard directory.
3. To begin configuring bidilink as the device connection method, do the
following steps.
a. Copy bidi_login.exp to a new file, as shown in
the following
screen example.
b. Open the new file for editing and edit the appropriate options.
[root@OnBoard /]# saveconf
[root@OnBoard onboard] cd /libexec/onboard
[root@OnBoard onboard]# cp bidi_login.exp soe_login.exp