以下は /usr/local/doc/README.lsisshd の内容です

sshd を Logical Solutions (Thinklogical) の改修した sshd(lsisshd) に置き換えて，各シリアルポートに割りつけたIPアドレスに直接ｓｓｈで接続することを可能にします．一般的には ｓｓｈ で直接各シリアルポートに接続する際は

で接続しますが，この lsisshd を使うことで，

のように直接シリアルポートに reverse ｓｓｈ することが可能になります．

Logical Solutions Secure Console Server lsisshd README

$Date: 2004/03/22 22:11:24 $
$Revision: 1.3 $


Introduction

This README describes the features of the modified sshd program, how
to install it, and how to configure it for use. The modified sshd program,
configuraion files, make file, this README, etc. are included in a RPM
created by Logical Solutions, INC. The RPM is named
lsiscs-lsissh-(version info).i386.rpm. and is available from Logical's
ftp site: ftp.thinklogical.com.


1.1 Purpose for the package

The Secure Console Server product line from Logical Solutions offers a
means to manage up to 48 console ports in one server. These ports are
typically accessed using a LSI written application called 'connect'.

Using SSH, one means of gaining access to a port is to run the connect
command via ssh.

Example 1: ssh bob@SCS10 -tt connect 1
would connect user bob to port 1 located on SCS10.

In a large installation with hundreds of servers, trying to remember which
server console port is connected to which SCS is difficult, if not impossible.
By assinging an IP addresses to each SCS device port, DNS can be used to give
this address a name which hopefully can be easily determined if the server
name is known. You might append '_cp' to the name of the server and assign
that name to the SCS device port IP address.

For example: if 10.9.8.7 is assigned to server LaTimes, and 192.168.6.106 is
assigned to port 6 of the SCS that is connected to the console port of LaTimes,
the ssh command to connect to the SCS device port is: ssh bob@LaTimes_cp.

If limited IP address space is an issue, then we offer another means to access
the device ports. It only requires 1 IP address, but the user must know which
device port is connected to which server. This method is really a modified
version of Example 1. In this format, the device port number or name is placed
after the user name in the ssh command.

Example 2: ssh pete:thisport@scs12.my.net
would connect pete to the port named 'thisport' that is located on scs12.my.net

The names used in this format are defined locally on a SCS, and while they are
unique on 1 SCS, they can be used on other SCS's.

These are not socket numbers, you still use socket 22 to connect to the ssh
server. We feel that the fewer open sockets, the better.

Please note that the following commands are functionally identical:
a) ssh pete:thisport@scs12.my.net
b) ssh pete@scs12.my.net -t connect thisport

Some ssh clients make it awkward to issue (b), so format (a) is available.



1.2 Files included in this package

/usr/local/sbin/lsisshd
The LSI modified sshd daemon

/usr/localsbin/makefile.ssh
The makefile to install this package and configure it

/etc/sysconfig/lsi.ssh.conf
The configuration file used by the above makefile



1.3 Installing the package

This package is distributed as an RPM. It may already be installed on your SCS.
If not, then use rpm to install it (rpm -U lsiscs-lsissh*.i386.rpm).
By default, the standard sshd program is used. When the modified version
is in use, the original file is renamed, and a symlink to lsisshd is created.

To make the modified program the default ssh server, run the command (as root)
make -f /usr/local/sbin/makefile.ssh use.lsi.ssh

The sshd service will be restarted at this point.

To revert to the original program, run (as root)
make -f /usr/local/sbin/makefile.ssh use.std.ssh



1.4 Configuring the system

The file /etc/sysconfig/lsi.ssh.conf is used to assign IP addresses to
device ports, or to remove assignments.

IP addresses can be assigned sequentially or randomly. All addresses
have the same first 3 IP numbers. (i.e. 10.9.8.x) The config file has
detailed descriptions about each parameter.

Using the port number option (user:portnumber) does not require the
IP address option. Either one can be used independantly of the other.

Once the configuration file has been edited and saved, then the makefile is
run again, this time creating the network entries.

make -f /usr/local/sbin/makefile.ssh serial.ip



-----------------------------------------------------------------------------
Appendix A. About this README

A.1. Copyright

This document is copyright ・004 Logical Solutions, Inc., all rights reserved.

If you have any questions, please contact <support@thinklogical.com>.

-----------------------------------------------------------------------------

A.2. Disclaimer

No liability for the contents of this documents can be accepted. Use the
concepts, examples and other content at your own risk. As this is a new
edition of this document, there may be errors and inaccuracies, that may of
course be damaging to your system. Proceed with caution, and although this is
highly unlikely, the author(s) do not take any responsibility for that.

You are strongly recommended to take a backup of your system before major
installation and backups at regular intervals.