From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Chris PeBenito <pebenito@gentoo.org>
Cc: Joshua Brindle <method@gentoo.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: semanage non MLS breakage
Date: Sat, 18 Feb 2006 15:06:03 -0500 [thread overview]
Message-ID: <43F77E2B.3050108@cornell.edu> (raw)
In-Reply-To: <1140288277.18548.28.camel@gorn.pebenito.net>
> gorn selinux-usr # semanage login -a -s staff_u pebenito
> libsemanage.validate_handler: MLS is disabled, MLS range s0 Unix user pebenito ignored
>
Ok.. message is missing a few words...
> gorn selinux-usr # semanage login -l
>
> Login Name SELinux User MLS/MCS Range
>
> __default__ user_u None
> pebenito staff_u s0
> root root None
>
>
Right, this is s0 being hardcoded in the semanage tool, so the bug needs
to be fixed there.
What I don't like about this is that libsemanage skips the MLS check
now, but still proceeds to write any MLS range found to disk. It should
invalidate an MLS range if it sees one. Will submit another patch on top
of the previous one...
--
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:[~2006-02-18 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 4:24 semanage non MLS breakage Chris PeBenito
2006-02-17 5:41 ` Ivan Gyurdiev
2006-02-17 14:23 ` Joshua Brindle
2006-02-17 15:04 ` Ivan Gyurdiev
2006-02-17 15:10 ` Joshua Brindle
2006-02-17 15:19 ` Ivan Gyurdiev
2006-02-17 15:28 ` Joshua Brindle
2006-02-17 15:39 ` Ivan Gyurdiev
2006-02-17 21:30 ` Ivan Gyurdiev
2006-02-18 18:44 ` Chris PeBenito
2006-02-18 20:06 ` Ivan Gyurdiev [this message]
2006-02-19 12:10 ` Ivan Gyurdiev
2006-02-19 16:54 ` Joshua Brindle
2006-02-19 17:17 ` Ivan Gyurdiev
2006-02-22 15:49 ` Stephen Smalley
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=43F77E2B.3050108@cornell.edu \
--to=ivg2@cornell.edu \
--cc=method@gentoo.org \
--cc=pebenito@gentoo.org \
--cc=sds@tycho.nsa.gov \
--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.