Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!psuvax1!psuvax1!flee From: flee@shire.cs.psu.edu (Felix Lee) Newsgroups: comp.unix.wizards Subject: Re: File daemons Message-ID:Date: 28 Sep 89 03:55:41 GMT References: <14609@bloom-beacon.MIT.EDU> Sender: news@psuvax1.cs.psu.edu Distribution: na Organization: Penn State University Computer Science Lines: 15 In <14609@bloom-beacon.MIT.EDU>, Steve Summit writes: > The obvious fully-general solution is to allow arbitrary functions > to be attached to files, to perform any kind of authentication > checking or audit trails that the file's owner might desire. Scott Schwartz has been randomly working on a daemon that implements access control lists. The idea is, if you want to open a file you don't normally have access to, you ask the daemon to open it for you, and it will give you an open file descriptor (after checking the access list). This can be extended to arbitrary file hooks, such as audit trails. Making this transparent is a matter of replacing open() (and recompiling everything in sight). -- Felix Lee flee@shire.cs.psu.edu *!psuvax1!flee