devfs
[Top] [All Lists]

Re: devfsd module for SE Linux

To: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Subject: Re: devfsd module for SE Linux
From: Russell Coker <russell@xxxxxxxxxxxx>
Date: Fri, 8 Mar 2002 14:10:13 +0100
Cc: devfs@xxxxxxxxxxx
In-reply-to: <200203080628.g286S5311927@vindaloo.ras.ucalgary.ca>
References: <20020307220939.1F80622B30@lyta.coker.com.au> <200203080628.g286S5311927@vindaloo.ras.ucalgary.ca>
Reply-to: Russell Coker <russell@xxxxxxxxxxxx>
Sender: owner-devfs@xxxxxxxxxxx
On Fri, 8 Mar 2002 07:28, Richard Gooch wrote:
> Russell Coker writes:
> > I've attached the source to a devfsd module for SE Linux security
> > settings with a sample config file (which mostly matches the
> > settings in file_contexts for /dev).
>
> What a huuuuuuuge config file!
>
> > Let me know what you think.
>
> Looks reasonable. Needs a copyleft notice, and can you put together a
> GNUmakefile rule so that it can be automatically built if the headers
> are available, and not built otherwise?

Actually I'm planning to ask the NSA to include it in their selinux-small 
archive, having that implies that you have the headers.

> Also, the devfsd shared objects are supposed to live in /lib/devfsd,
> not in /usr/lib.

Good point, it needs to be in the root file system.

As /lib/devfsd is the official place, could you make devfsd check 
"/lib/devfsd/%s", name first if the name doesn't include a '/'character?  
That'll cut down the size of the config files.

> Finally, can you change the name from flask to something more
> meaningful?

OK.  For the next version s/flask/se/g

-- 
If you send email to me or to a mailing list that I use which has >4 lines
of legalistic junk at the end then you are specifically authorizing me to do
whatever I wish with the message and all other messages from your domain, by
posting the message you agree that your long legalistic sig is void.


<Prev in Thread] Current Thread [Next in Thread>