Xref: utzoo comp.unix.wizards:25454 alt.security:2477
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!munnari.oz.au!spool.mu.edu!cs.umn.edu!sctc.com!beede
From: beede@sctc.com (Mike Beede)
Newsgroups: comp.unix.wizards,alt.security
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <1991May7.160447.22954@sctc.com>
Date: 7 May 91 16:04:47 GMT
References: <7299: Apr2510:22:2091@kramden.acf.nyu.edu> <12535@dog.ee.lbl.gov> <7310@segue.segue.com>
Organization: SCTC
Lines: 15

psl@segue.segue.com (Peter Langston) writes:

>As it stands now, you can allow write access long enough for a friend to
>initiate a write(1) and then turn off write access and discourage any other
>interruption, (i.e. you can discriminate among users temporally).

If you want to descriminte between users, why not _do_ that instead of
using the kludge of turning message access on and off?  Have a
mechanism with smaller granularity (users instead of yes/no).

-- 
Mike Beede         SCTC
beede@sctc.com     1210 W. County Rd E, Suite 100           
			Arden Hills, MN  55112
                         (612) 482-7420