From: Tom <tom@lemuria.org>
To: Tracy R Reed <treed@ultraviolet.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: SE Linux on Debian
Date: Wed, 2 Oct 2002 09:24:04 +0200 [thread overview]
Message-ID: <20021002092404.B4475@lemuria.org> (raw)
In-Reply-To: <20021001235017.B28686@ultraviolet.org>; from treed@ultraviolet.org on Tue, Oct 01, 2002 at 11:50:17PM -0700
On Tue, Oct 01, 2002 at 11:50:17PM -0700, Tracy R Reed wrote:
> It seemed like make relabel would be a good idea to ensure everything is
> labelled properly after all of the messing around I have done and I got
> this:
Absolutely, yes. You should relabel twice: Once before rebooting into
the SELinux kernel, once after (to label the files created during
shutdown and boot).
> home:/etc/selinux# make relabel
> /usr/sbin/setfiles file_contexts/file_contexts `mount | awk '/(ext[23]|reiserfs)/{print $3}'`
> /usr/sbin/setfiles: Running on a SELinux kernel, using new system calls /usr/sbin/setfiles: read 767 specifications
> /usr/sbin/setfiles: invalid context system_u:object_r:home_root_t on line number 86
> /usr/sbin/setfiles: invalid context system_u:object_r:games_exec_t on line number 616
> /usr/sbin/setfiles: invalid context system_u:object_r:var_log_inetd_t on line number 647
> /usr/sbin/setfiles: invalid context system_u:object_r:rndc_conf_t on line number 759
> /usr/sbin/setfiles: invalid context system_u:object_r:useradd_exec_t on line number 995
> /usr/sbin/setfiles: invalid context system_u:object_r:useradd_exec_t on line number 996
> /usr/sbin/setfiles: invalid context system_u:object_r:useradd_exec_t on line number 997
> /usr/sbin/setfiles: invalid context system_u:object_r:useradd_exec_t on line number 998
> /usr/sbin/setfiles: invalid context system_u:object_r:vmware_user_conf_t on line number 1053
> /usr/sbin/setfiles: invalid context system_u:object_r:xauth_exec_t on line number 1058
> make: *** [relabel] Error 1
I've seen these during my yesterday burnout, too. Check if your loaded
policy, policy on disk and kernel all match in versions. Did it load
the policy correctly? Try make load again. Also, I think you can delete
the /etc/selinux/file_contexts/file_contexts file since it should be
created from the .fc files.
Also, when you remove .te files, don't forget to remove the
corresponding .fc files, too.
--
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub 1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
--
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.
next prev parent reply other threads:[~2002-10-02 7:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 22:36 SE Linux on Debian Tracy R Reed
2002-10-02 0:01 ` Russell Coker
2002-10-02 0:54 ` Tracy R Reed
2002-10-02 8:36 ` Russell Coker
2002-10-02 1:48 ` Brian May
2002-10-02 5:10 ` Tracy R Reed
2002-10-02 5:42 ` Tom
2002-10-02 6:17 ` Brian May
2002-10-02 6:27 ` Tracy R Reed
2002-10-02 7:20 ` Tom
2002-10-02 7:30 ` Tracy R Reed
2002-10-02 8:50 ` Russell Coker
2002-10-02 8:52 ` Russell Coker
2002-10-02 6:50 ` Tracy R Reed
2002-10-02 7:24 ` Tom [this message]
2002-10-02 8:54 ` Russell Coker
2002-10-02 21:31 ` Brian May
2002-10-02 21:42 ` Russell Coker
2002-10-02 22:10 ` Brian May
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=20021002092404.B4475@lemuria.org \
--to=tom@lemuria.org \
--cc=selinux@tycho.nsa.gov \
--cc=treed@ultraviolet.org \
/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.