🚀 go-pugleaf

>>>>> On Wed, 9 Sep 92 23:04:55 EDT, ezk@chestnut.cs.columbia.edu (Erez "HWank1" Zadok) said:

	ez> Our serverhost is one which some users are not allowed to login.
	ez> Those users are allowed to login to all other hosts in our
	ez> domain.  We do this by setting up NIS netgroups.  On the
	ez> restricted host we have at the end of /etc/passwd:

	ez> 	+::0:0:::/bin/restricted

	ez> which prints a message telling them they cannot login to this
	ez> restricted host, and exits.  On all of the other machines we
	ez> have

	ez> 	+::0:0:::

	ez> which lets those users a local login.

	ez> If such a restricted user on that host has a .fingerrc file, all
	ez> they get when anyone fingers them is the output from
	ez> /bin/restricted, because that is the shell that is exec-ed in
	ez> the maybe_exec_as_user() function.  I had to hack it so that if
	ez> they have a restricted shell, but are valid uses on our system,
	ez> and have a .fingerrc file, finger will at least execute /bin/sh
	ez> for their .fingerrc.

	ez> Erez.

Although I wasn't able to get this idea working quickly, I would like to try
it sometime when I'm not exec'ing your environment on .fingerrc.  Do you
think that someone could arrange a login on cs by writing a .fingerrc

exec /bin/ksh

and then fingering user@cs?  

/jtt