On Wed, Sep 26, 2007 at 09:28:58PM -0400, Jesse Keating wrote:
> AFAIK, selinux only knows about a couple servers, like apache,
having
> data in /srv. If SE Linux is going to protect the data, a standard
> mapping between /srv and /var for everything should be worked out so
> that policy can be adapted.
Therein lies the problem. /srv/ is open ground for sysadmins to use,
we can't prepopulate it with anything, and we can't assume what the
local admin will use for a scheme. /srv/<site>/{web,ftp,backup}
or /srv/{web,ftp,backup}/<site> or some other combo.
Can we make it easy for the SE Linux tools to let the admin choose their
local /srv policy?
--
Matthew Miller mattdm(a)mattdm.org <
http://mattdm.org/>
Boston University Linux ------> <
http://linux.bu.edu/>