Xref: utzoo comp.unix.wizards:25266 alt.security:2376
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.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 4: What You Can Look Forward To
Message-ID: <1991Apr30.231235.7874@mp.cs.niu.edu>
Date: 30 Apr 91 23:12:35 GMT
References: <3600: Apr2614:04:4391@kramden.acf.nyu.edu> <1991Apr30.224740.17040@pcserver2.naitc.com>
Organization: Northern Illinois University
Lines: 19

In article <1991Apr30.224740.17040@pcserver2.naitc.com> kdenning@pcserver2.naitc.com (Karl Denninger) writes:
>
>The most obvious attempts, taking over "unused" ptys slave ends, result in
>the system skipping them when assignment time comes around.  This prevents
>
>The RS/6000 dynamically creates ptys, and thus doesn't suffer from the
>problem at all.

 And what exactly is there to stop somebody running a daemon which grabs
access to a pty immediately after it has been assigned, or immediately
after it has been dynamically created, but before public write access has
been turned off.


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