Xref: utzoo comp.unix.wizards:25390 alt.security:2434
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uwm.edu!linac!mp.cs.niu.edu!rickert
From: rickert@mp.cs.niu.edu (Neil Rickert)
Newsgroups: comp.unix.wizards,alt.security
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <1991May4.132953.30925@mp.cs.niu.edu>
Date: 4 May 91 13:29:53 GMT
References: <12535@dog.ee.lbl.gov> <15896: Apr2714:35:3991@kramden.acf.nyu.edu> <1991May1.121058.20933@osceola.cs.ucf.edu>
Organization: Northern Illinois University
Lines: 16

In article <1991May1.121058.20933@osceola.cs.ucf.edu> ssd@engr.ucf.edu (Steven S. Dick) writes:
>I didn't think of putting in a pause before sending the next 20
>lines...  This might be useful.  I wouldn't actually pause--just record
>the time, and make sure that some decent amount of time (like at least
>1 sec per line) has passed before sending anything more.  Nobody can
>actually type that fast anyway.  :-)

 How about not just 'pausing', but also closing and re-opening the file
descriptor before sending any more.  This would honor any change in
permissions.

-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
  Neil W. Rickert, Computer Science               <rickert@cs.niu.edu>
  Northern Illinois Univ.
  DeKalb, IL 60115                                   +1-815-753-6940