Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC840302); site turing.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!turing!aeb
From: aeb@turing.UUCP
Newsgroups: net.unix-wizards
Subject: Re: deceptive mail
Message-ID: <223@turing.UUCP>
Date: Fri, 16-Nov-84 14:29:07 EST
Article-I.D.: turing.223
Posted: Fri Nov 16 14:29:07 1984
Date-Received: Sat, 17-Nov-84 20:05:11 EST
References: <331@uvm-cs.UUCP> <45@uwvax.UUCP> <221@turing.UUCP> <250@amdcad.UUCP>
Organization: CWI, Amsterdam
Lines: 28
Apparently-To: rnews@mcvax.LOCAL

>> It is even worse: if you are working at a terminal, somebody comes along
>> and in order to show you something logs in recursively: (login x)
>> then after his login process has finished your identity will be reported
>> as x by programs like who and routines like getlogin().
>> -- 
>>       Andries Brouwer -- CWI, Amsterdam -- {philabs,decvax}!mcvax!aeb
> 
> 
> Say What!
> 
> If someone comes up to your terminal and types "login name" you
> will be logged out and he will be logged in. If his login process
> "finishes" i.e. he logs out, the system will display a login 
> banner. YOU WILL BE GONE! I'd say whoever did this when you were
> at a terminal walked away without logging off. Are you confusing
> login with su???
> 
> Mike @ AMD

Please read carefully: if x says  (login x)  to my shell and his login
process finishes then I am back in my shell again. He might also have
said  /bin/login x . What you are thinking of is that most shells
recognize  login  as a special command and execute it directly without
forking.


-- 
      Andries Brouwer -- CWI, Amsterdam -- {philabs,decvax}!mcvax!aeb