🚀 go-pugleaf

Apparently when I finger anyone who has a .fingerrc file, my .env gets
executed no matter what, and then the script does.  I even unset the value
of my ENV variable (in ksh) and thought that had something to do with it.
But that did not help.  What did help was when I removed my .env file.

Finger should exec() the .fingerrc script and nothing more.  In the top of
my .kshrc I put

	#!/bin/ksh -p

using the -p to explicitly ask for .env files not to be executed.  Your code
probably executes a shell on behalf of the fingered user, and then the
user's .fingerrc.

Another problem I have is that whenever I finger someone who has a .fingerrc
file (in -l mode), only the output from executing the .fingerrc file is
shown, and nothing more.  If the user did not have a .fingerrc file, I would
get the default long listing (in long mode): user name, id, shell, mail
status, .plan and .project.

I think that what you need to do is supply a few more options (compile time
or run time.)  These will allow me to always get the long "standard"
information no matter what, even if the user has a .fingerrc file.  Another
option would be to execute the .fingerrc instead, in addition to "standard"
information, or non at all.  The last option, one to turn off execution of
.fingerrc, controlled by the client, will be very popular among people with
tight computer security in mind.

Erez Zadok.
---
A wank's morning starts one machine   | Arpa:   ezk@cs.columbia.edu
clock cycle after midnight.           | Usenet: ...!rutgers!columbia!cs!ezk
 -HebrewWank #1 (US meaning, not UK!) | Bitnet: erzus@cuvmb.BITNET