System command on FreeBSD...

[Chad McWilliams]

> -----Original Message-----
> From: 
> filepro-list-bounces+fpmail=computiprint.com at lists.celestial.c
> om 
> [mailto:filepro-list-bounces+fpmail=computiprint.com at lists.cel
> estial.com] On Behalf Of Bill Vermillion
> Sent: Wednesday, December 29, 2004 12:54 PM
> To: filePro List
> Subject: Re: System command on FreeBSD...
> 
> 

> Since 'id' will return the id and group memberships [of which 
> there can be many in the BSD world] I think the only thing 
> you can really depened upon to find the calling user is to 
> use the 'who am i' command.  This will return the ID of the 
> actual login.  Do NOT confuse this with the 'whoami' command 
> which will return the EUID.
> 
> There aren't many things that are that different from the 
> Unix systems and the BSD systems - but his is certainly one of them.
> 
> I also have problem with the way part of the 'su' is 
> implemented as using multiple 'su's can give some permissions 
> they are not supposed to have.  I got a lively discussion 
> started and many didn't see the problem, but then in the end 
> those who run secure system think the su stack should be 
> limited to one - and that would
> fix any potential holes.    I had been using the FreeBSD for quite
> awhile when I discovered that one, and to my way of thinking 
> it is an anomoly.
> 
> But I think parsing the output of 'who am i' will do what you 
> need it to do.
> 

This was also the idea I came up with as a fallback.  The only problem
is a lot of programs will have to be changed, so I wanted to make sure
there wasn't another way.

This does have one other effect though: If the person, while shelled
into the second filepro program, were to add or modify a record, I'm
guessing the @cb and @ub (or whatever the system maintained field for
updated by is) would store the same as what @id was reporting which
would be filepro, not the actual user.

-Chad McWilliams