Network Logins

[Kartik Subbarao]

In article <1991May28.174505.10471 at jato.jpl.nasa.gov> mwette at csi.jpl.nasa.gov (Matt Wette) writes:
>Here what I can suggest if you're willing to use rlogin instead of
>telnet.  You may be able to cook up something from it.
>
>Say the host machine is mach0 and the remote machine is mach1.  In
>the /etc/passwd file on mach0 I put in the following entry:
>
>  mach1::9999:999:remoteLogin:/usr/local:/usr/local/etc/rxlogin
>
>/usr/local has a .hushlogin file so that /etc/motd doesn't get
>printed.  The file /usr/local/etc/rxlogin is the following:
>  #!/bin/sh
>  machine=$USER
>  echo -n "$machine login: "; read username
>  exec /usr/ucb/rlogin $machine -l $username

What's to stop the user from hitting a ^C or something in the middle of this
shellscript? Of course, you could do a trap for every signal, but there's
really no need for a kludgey shellscript as a login shell. Just make
/usr/ucb/telnet the login shell; You don't need anything more than telling
the user to type "open" before the host that he wants to connect to...

		-Kartik

--
internet% whoami

subbarao at phoenix.Princeton.EDU -| Internet
kartik at silvertone.Princeton.EDU (NeXT mail)  
SUBBARAO at PUCC.BITNET			          - Bitnet