Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!cbosgd!ucbvax!info-vax
From: hobbit@AIM.RUTGERS.EDU ("*Hobbit*")
Newsgroups: mod.computers.vax
Subject: Terminal ACLs
Message-ID: <8511150004.AA03498@ucbvax.berkeley.edu>
Date: Thu, 14-Nov-85 19:05:20 EST
Article-I.D.: ucbvax.8511150004.AA03498
Posted: Thu Nov 14 19:05:20 1985
Date-Received: Sat, 16-Nov-85 00:54:11 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "*Hobbit*" <hobbit@aim.rutgers.edu>
Organization: The ARPA Internet
Lines: 11
Approved: info-vax@sri-kl.arpa

One way to avoid that ACL-related security hole is to run virtual terminals.
That way, the user can only set the ACL for the VTAnn: device [even if he
explicitly specifies the physical device name!  -- weird...], which goes
away after he logs out [taking the ACL with it].

Which brings to mind the following question: If, say vta3: was recreated
somewhere down the line [however improbable this may be], would it still
have the ACL attached?  I would think not, since it's a new device.

_H*
------