From: Jim Meyering <jim@meyering.net>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: "Ondřej Vašík" <ovasik@redhat.com>,
yaneti@declera.com, CoreutilsBugs <bug-coreutils@gnu.org>,
"SE Linux" <selinux@tycho.nsa.gov>
Subject: Re: [PATCH]: chcon: no longer abort on SELinux disabled kernel
Date: Mon, 05 Oct 2009 22:02:05 +0200 [thread overview]
Message-ID: <87d451boea.fsf@meyering.net> (raw)
In-Reply-To: <1254770225.2251.152.camel@moss-pluto.epoch.ncsc.mil> (Stephen Smalley's message of "Mon, 05 Oct 2009 15:17:05 -0400")
Stephen Smalley wrote:
...
> Must have previously booted an ancient kernel with SELinux permissive
> and no policy loaded. Kernel was fixed by the commit below in 2006.
> I'd recommend that he run the following to clean up the droppings in his
> filesystem:
> find / \( -fstype ext2 -o -fstype ext3 -o -fstype ext4 \) -exec setfattr -x security.selinux {} \;
>
> commit 8aad38752e81d1d4de67e3d8e2524618ce7c9276
> Author: Stephen Smalley <sds@tycho.nsa.gov>
> Date: Wed Mar 22 00:09:13 2006 -0800
>
> [PATCH] selinux: Disable automatic labeling of new inodes when no policy is loaded
Thanks for the quick explanation!
--
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:[~2009-10-05 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1254727932.3849.8.camel@dhcp-lab-219.englab.brq.redhat.com>
2009-10-05 18:44 ` [PATCH]: chcon: no longer abort on SELinux disabled kernel Jim Meyering
2009-10-05 19:17 ` Stephen Smalley
2009-10-05 20:02 ` Jim Meyering [this message]
2009-10-06 8:14 ` Jim Meyering
2009-10-07 12:37 ` Stephen Smalley
2009-10-07 12:48 ` Jim Meyering
2009-10-07 12:54 ` Stephen Smalley
2009-10-07 13:34 ` Jim Meyering
2009-10-07 15:30 ` Stephen Smalley
2009-10-10 9:59 ` Jim Meyering
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=87d451boea.fsf@meyering.net \
--to=jim@meyering.net \
--cc=bug-coreutils@gnu.org \
--cc=ovasik@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=yaneti@declera.com \
/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.