SSH Daemon (Server)
1. Unpack and read README from ssh/2 archive :-)
2. Generate server key with command:
ssh-keygen -b 2048 -N "" -f /etc/ssh_host_key
Find key-file "random_seed" (located in %HOME%/.ssh/), rename it
to ssh_random_seed and place into %ETC%.
3. Check the configuration files, that should be located in %ETC%:
ssh_host_key
ssh_host_key.pub
ssh_random_seed
ssh_term
sshd_config
Also some nice things to know about sshd:
/etc/motd |
file can contain something nice to output upon logging on
to the server. A welcome message, server usage rules and so on.
|
/etc/nologin |
If this file is present, login will not be allowed. Instead,
the contents of this file will be sent to the client and session
closed.
|
/etc/sshrc ~/.ssh/rc |
These can be some shell scripts that will be automatically executed
when you log on. Unfortunately CMD.EXE can't do it.
|
/etc/environment ~/.ssh/environment |
This can be a file that can contain a number of VARIABLE=VALUE
lines. These variables will be added to your environment.
|
4. To allow multiple different users with different password the OS/2 port of
SSHD has a built-in parser for Unix-like passwd files.
For easier password database management a simple tool called "user"
is provided.
5. If you want to run full-screen VIO programs (such as File Commander etc)
through ssh you will need to make a special setup for given user: his shell
should be "tnpipe.exe". This is a special program which launches TELNETDC.EXE
(which comes with IBM TCP/IP) and redirects all input and output of TELNETDC
to sshd. Thus, the line for a user that wishes to use full-screen VIO programs
could look like this:
test:UkGfAuD60Pabg:101:101::$f/home:$f/path/to/tnpipe.exe
Remember that you should specify full path to tnpipe.exe.
When the user will log on, he will see the usual CMD.EXE prompt. But this time
when he'll run some VIO program, it will really work. Note that you cannot
DETACH the sshd daemon, otherwise it won't be able to launch a full-screen
session.
SSH client
You can use national codepages in SSH client.
See "Translation tables" section in ssh_term config file.
For better results, if you're connecting from an OS/2 machine using ssh, you
should use the /etc/ssh_term.os2 configuration file for the built-in terminal,
otherwise you will get bad and sometimes very bad output.
Download
ssh/2 1.2.30 (25/08/2000)
Author
Andrew Zabolotny
Discuss publication (replies:0)
Previous publication | Next publication |