From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Russell Coker <russell@coker.com.au>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: bug in policy (1.14-3+?) with apache.te unused
Date: Wed, 18 Aug 2004 11:02:23 +0100 [thread overview]
Message-ID: <20040818100223.GA19646@lkcl.net> (raw)
In-Reply-To: <200408181845.50618.russell@coker.com.au>
On Wed, Aug 18, 2004 at 06:45:50PM +1000, Russell Coker wrote:
> On Tue, 17 Aug 2004 21:29, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > i upgraded to 1.14-6 on the policycoreutils and i get
> > httpd_sysadm_content_t does not exist in file_contexts
> > on a make relabel.
>
> That's a minor bug in the apache policy for Debian, I'll fix it in the next
> upload.
ah, cool.
well, i removed apache.te and openca.te and that fixed it, too.
> > so.... well, i figured okay, let's make apache.te unused
> > (as i should have done in the first place) because apache
> > isn't on this system.
> >
> > i get a compile error on openca.te not being able to find
> > httpd_t.
>
> openca-ca.te depends on apache.te . Why do you want to use openca without
> Apache? Is it usable?
... i have _no_ idea :)
if it's a dependency, maybe it's good that it breaks.
it would be better to have some sort of more descriptive error
message saying "you don't have a policy for apache.te but are trying
to use openca.te".
then people can choose, based on now knowing what's going on, to either
install apache.te or remove openca.te.
*shrug* :)
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2004-08-18 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 11:29 bug in policy (1.14-3+?) with apache.te unused Luke Kenneth Casson Leighton
2004-08-18 8:45 ` Russell Coker
2004-08-18 10:02 ` Luke Kenneth Casson Leighton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040818100223.GA19646@lkcl.net \
--to=lkcl@lkcl.net \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.