Xref: utzoo news.groups:6245 news.sysadmin:1550
Path: utzoo!attcan!uunet!husc6!mailrus!ncar!boulder!ccncsu!longs.LANCE.ColoState.Edu!steved
From: steved@longs.LANCE.ColoState.Edu (Steve Dempsey)
Newsgroups: news.groups,news.sysadmin
Subject: Re: who, me?
Keywords: security, virus, summer job, TIOCSTI
Message-ID: <622@ccncsu.ColoState.EDU>
Date: 17 Nov 88 19:07:24 GMT
References: <718@convex.UUCP> <247@aplcen.apl.jhu.edu> <2975@ci.sei.cmu.edu>
Sender: news@ccncsu.ColoState.EDU
Reply-To: steved@longs.lance.colostate.edu
Followup-To: news.sysadmin
Organization: Colorado State University, Fort Collins, CO  80523
Lines: 23


In article <718@convex.UUCP>, tchrist@convex.UUCP (Tom Christiansen) writes:
> In article <2975@ci.sei.cmu.edu> pdb@sei.cmu.edu (Patrick Barron) writes:
> >You can't necessarily TIOCSTI a terminal if you can write to it.  TIOCSTI
> >only works if 1) the terminal in question is your process's control terminal,
> >or 2) you're root.
> 
> sadly, only the first condition need be satisfied, which is the whole problem.
>
>     Tom Christiansen              {uiucdcs,ut-sally,sun}!convex!tchrist 

We're getting very close to handing out the Keys to the Kingdom here.  A few more
clues and a little imagination will yield potential disaster.  I'm all for freedom
of information, etc., etc. but taking this one much further will only fuel the
brightly burning ambition of the curious {cr,h}ackers in our midst.

This is an excellent case in point for the restriction of the security list,
which is where such discussions belong.  Please, no more hints on TIOCSTI.

        Steve Dempsey,  Center for Computer Assisted Engineering             
  Colorado State University, Fort Collins, CO  80523    +1 303 491 0630
INET: steved@longs.LANCE.ColoState.Edu, dempsey@handel.CS.ColoState.Edu
UUCP: boulder!ccncsu!longs.LANCE.ColoState.Edu!steved, ...!ncar!handel!dempsey