From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] SELinux (targeted policy) and invalid context
Date: Wed, 17 Nov 2010 22:30:20 +0100 [thread overview]
Message-ID: <20101117213020.GA28354@siphos.be> (raw)
In-Reply-To: <AANLkTik8d=NqEZwkMuBq5MdcedwpYoBMuwHgA8t07oPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
On Wed, Nov 17, 2010 at 09:41:49PM +0100, luc nac wrote:
> Now I am trying to use SELinux (targeted policy) in a brand new Gentoo
> stage3 (Kernel 2.6.32-hardened-r9), I tried all versions of
> selinux-base-policy available, but relabeling the file system always
> fails with the same error: "filespec_add: Conflicting specifications
> for ...".
> Am I still doing something wrong? The only thing that I can do to run
> SELinux in Gentoo is try to make my own ebuild?
This is a cosmetic error and shouldn't really be an issue (though I don't
have it myself with a more recent policy snapshot). It means that there are
multiple rules that match the given file, and that the rules might apply a
different label to the inode.
You can see the matching rule(s) using matchpathcon I think:
~# matchpathcon /usr/lib/misc/glibc/getconf
/usr/lib/misc/glibc/getconf system_u:object_r:lib_t
> # rlpkg -a -r
> Relabeling filesystem types: ext2 ext3 jfs xfs
> filespec_add: conflicting specifications for /usr/bin/getconf and
> /usr/lib/misc/glibc/getconf/POSIX_V6_ILP32_OFFBIG, using
> system_u:object_r:lib_t.
Looks like it got the right one (unless I'm also running the wrong one ;-)
Wkr,
Sven Vermeulen
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-11-17 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 0:44 [gentoo-hardened] SELinux (targeted policy) and invalid context luc nac
2010-11-15 1:14 ` Chris Richards
2010-11-17 20:07 ` Sven Vermeulen
2010-11-17 20:41 ` luc nac
2010-11-17 21:30 ` Sven Vermeulen [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=20101117213020.GA28354@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=gentoo-hardened@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox