[Bug 169247] Review request: rt3 - Request tracker 3

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review request: rt3 - Request tracker 3


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169247





------- Additional Comments From paul at city-fan.org  2005-10-17 04:44 EST -------
(In reply to comment #20)
> (In reply to comment #19)
> > (In reply to comment #16)
> > > (In reply to comment #14)
> > > > I think we're all agreed that /var/cache/rt3 is a better option than
> > > > /var/lib/rt3, aren't we?
> > > Yes, but unless somebody tells me how to achieve this inside of an rpm,
without
> > > having to modify on of the centralized SELinux packages I don't seem any
> > > perspective to do so.
> > > 
> > > AFAIK, the current SELinux implementation doesn't allow this, except of
(may-be)
> > > running chcon inside of a %postin script directly.
> > 
> > I'm happy to handle the SELinux bug report and get it fixed, but I need
> > to make sure that I'm getting the right directories fixed. There's no 
> > point getting the
> > context of /var/cache/{mason,rt3} fixed if /var/lib/{mason,rt3} are being used
> > by the {mason,rt3} packages. So, are /var/cache/{mason,rt3} the 
> > directories that are going to be used?
> Yes, we want /var/cache/*, but are deadlocked and we can't switch to it, before
> _SELinux_ has been changed.

I don't get this. In what way is using /var/lib/rt3 any less broken than using
/var/cache/rt3? With SELinux enabled, apache can write to neither.

In the meantime I shall raise the bug to get SELinux to support
/var/cache/{mason,rt3}



-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.