Overview
The original TCP/IP telnet server program has a severe security leak:
it uses the content of the environment variable
TELNET.PASSWORD.ID as the login password,
wich can easily be viewed and/or modified within CONFIG.SYS.
You can replace the program responsible for this, namely TNLOGIN.EXE,
by the LOGINUNX.EXE, which is also coming with standard
TCP/IP. It uses the unix-style %etc%\passwd file, which allows at least
to configure several telnet login accounts with a single password for each
account, but to create such a file, you additionally need a port of the
unix program called passwd.
A big disadvantage of this approach is, that everybody, who is allowed to login
via telnet, can view and/or edit this file, because a user allowed to login can
modify every file on the system, since there ist no file system security on normal
OS/2 workstations.
While it may be difficult to use and/or modify an existing account, because the password
is encrypted, it is quite easy to add a new account by adding the appropriate data to the
passwd file.
Other replacement programs for TNLOGIN.EXE even allow to sepcify a startup
directory and an alternate command processor. For that they use a slightly
modified structure of the passwd file, but they all use the passwd file as a
security database.
Only recently a TNLOGIN replacement like this UPMLOGIN package has
been released, that verifies userid/password combinations against the
OS/2 built-in local User profile management (UPM). This package is called
TnLogin 1.00 (TNLG100.ZIP) and was released by Dmitry Irtegov and
Konstantin Boyandin.
Its TNLOGIN.EXE replacement already has a big advance compared to the passwd approach.
You can configure user accounts and user groups within the UPM GUI, and
for to be able to modify the security database, one needs to be an admin.
The UPMLOGIN package can do much more for you:
- you can restrict telnet login access to admins only.
- you can restrict telnet login access to members of a default TNLOGIN user group.
- you can restrict telnet login access to users, who are members of at least one of a list of self defined user groups.
- you can optionally verify all userid/password combinations against the LAN/WARP Server domain
of your workstation.
See configuration scenarios and the
readme file coming with the package for further details on how to set up
those restrictions within the local UPM.
![[Top]](/img/top.gif)
Prerequisites
This program runs under OS/2 WARP V3.x or later.
More, it requires one of the following TCP/IP packages
- IBM TCP/IP for OS/2 or the
- Internet Access Kit for OS/2
being installed.
To get a local User Profile Management (UPM), you need to install one of
the following packages:
For OS/2 WARP 3 Connect:
For OS/2 WARP 4:
For all OS/2 versions:
- LAN/WARP Server Client for OS/2
![[Top]](/img/top.gif)
Download current version
You can download the current version (ca 24.18 Kb) from the following following sources: