Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!hao!boulder!sunybcs!ugfailau
From: ugfailau@sunybcs.uucp (Fai Lau)
Newsgroups: comp.unix.questions
Subject: Re: Trapping yourself in csh.  (Fun with ignoreeof revisited)
Message-ID: <8716@sunybcs.UUCP>
Date: 21 Feb 88 10:17:37 GMT
References: <3282@psuvax1.psu.edu> <221@scovert>
Sender: nobody@sunybcs.UUCP
Reply-To: ugfailau@joey.UUCP (Fai Lau)
Organization: SUNY/Buffalo Computer Science
Lines: 25

In article <221@scovert> jonl@sco.COM (ScoMole #192-1232A) writes:
>
  [practical joke about putting a scary message into a friend's .login file]
>and then had a false port selector message come up. scared him quite
>a bit as i remember.. sometimes the best jokes are the simpliest..

	A Unix machine I used to work with had very loose securities.
But it really wasn't a problem because everything terminals to
the machine was hard wired and the company had a security system
that check everybody that comes into the building. But then
there was me.
	Anyway, once I found out that all the devices in /dev
was sccessable to everybody, I started doing things like writting
pseudo system messages to other terminals and monitoring their
activities. One thing though, the response of the system to a terminal
for some reason slowed down noticeably when I monitored inputs from
that terminal. I never found out although it might be because
there was heavy I/O between the terminal and the program it was
running. Unfortunately I wasn't smart enough so the idea of figuring
out the password to root never passed my mind. 8-)

Fai Lau
SUNY at Buffalo (The Arctic Wonderland)
UU: ..{rutgers,ames}!sunybcs!ugfailau
BI: ugfailau@sunybcs INT: ugfailau@joey.cs.buffalo.EDU