[1099] in linux-net channel archive
Re: login, telnetd and utmp
daemon@ATHENA.MIT.EDU (Miquel van Smoorenburg)
Thu Sep 14 17:19:02 1995
To: submit-linux-dev-net@ratatosk.yggdrasil.com
From: miquels@cistron.nl (Miquel van Smoorenburg)
Date: 14 Sep 1995 11:33:19 +0200
In article <199509131548.RAA07098@i17linuxb.ists.pwr.wroc.pl>,
Marek Michalkiewicz <marekm@i17linuxb.ists.pwr.wroc.pl> wrote:
>Hi,
>
>after looking at various login sources which all claim to support Linux
>(util-linux, shadow, logdaemon) I noticed that we have no standard way
>of utmp handling. The problem is that we have a SysV-style utmp but
>we use BSD-style networking programs like telnetd and rlogind.
>
>- modify telnetd to create an utmp entry with all known fields filled in
> (including ut_line: why use slow ttyname() if telnetd already knows
> the tty name?) and add a built-in tcp wrapper (using libwrap.a from
> tcp-wrappers-7.2)
>- modify login to require a valid utmp entry for the current process
> (like SysV login does) and don't fill in the ut_addr field
I've been thinking of adding the utmp support for external programs
to sysvinit for some time. Some BSD versions have an <initreq.h> file
and a /etc/INITFIFO fifo file. You can then send commands to init
and let it start a login session on a certain terminal. Init will
then handle all utmp and wtmp related stuff. In addition, it
would be possible to bind telnet and rlogin sessions to one or
more runlevels, just as with the regular getty's.
It would mean that we'd have to rewrite some major parts of
in.telnetd, in.rlogind and wat-have-you.
As I've asked several times before, is there anyone who has more
information about <initreq.h> ? The only pinter I've seen to
it is in the BSD 4.4 telnetd source.
--
--
Miquel van Smoorenburg, miquels@cistron.nl Cistron Internet Services
Mail info@cistron.nl An independent Dutch Internet Provider
for more information <A Href = "http://www.cistron.nl/">CIS</A>
+31-1720-19445 (Voice) 30979 (Fax) 42580 (Data) - Alphen a/d Rijn