From: Guido Trentalancia <guido@trentalancia.com>
To: Eric Paris <eparis@redhat.com>
Cc: Eric Paris <eparis@parisplace.org>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: [refpolicy] pam_selinux(gdm-password:session): Security Context justin:staff_r:insmod_t:s0 Assigned
Date: Sat, 24 Sep 2011 00:38:19 +0200 [thread overview]
Message-ID: <1316817499.2487.89.camel@vortex> (raw)
In-Reply-To: <1316812634.28696.1.camel@localhost>
Hello Eric.
On Fri, 2011-09-23 at 17:17 -0400, Eric Paris wrote:
> On Fri, 2011-09-23 at 23:12 +0200, Guido Trentalancia wrote:
>
> > You seem to suggest that load_policy -i (and not the kernel) should make
> > sure that init has transitioned to its designated context...
>
> Can't speak for Justin's system.
That's for sure. But it seems to me that he already stated that it just
loaded plain refpolicy from git on a plain F15 system. Since we are on
the list he might even confirm once again...
> But that's not what I said. I said
> it's /sbin/init's problem to make sure it did the right thing and to
> handle errors correctly if it failed. If Justin has his box enforcing
> and can boot without loading a policy that's a bug and needs to be
> filed.
He has loaded the policy.
The point is that when init does not transition to init_t nothing
happens and the system keeps running with all processes in kernel_t or
insmod_t.
It surely use to happen with upstream components and policy back at the
beginning of this year (I did test that and reported it to the refpolicy
mailing list).
Apparently it also happens with Fedora 15 according to what Justin
reported on here when he started this thread...
Earlier on Daniel Walsh said Fedora and RHEL would crash in such case
(init has not transitioned properly to init_t). I said "very good" (as
that is what I expect from a SELinux system) and asked "how did you
achieved that ?" because I believe such behavior should be definitely be
imported in upstream. But then I thought Daniel's statement doesn't
match with what Justin reported.
Regards,
Guido
--
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:[~2011-09-23 22:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 3:40 [refpolicy] pam_selinux(gdm-password:session): Security Context justin:staff_r:insmod_t:s0 Assigned Justin Mattock
2011-09-16 14:59 ` Daniel J Walsh
2011-09-16 14:59 ` Daniel J Walsh
2011-09-16 15:22 ` Justin P. Mattock
2011-09-16 15:58 ` Daniel J Walsh
2011-09-16 15:58 ` Daniel J Walsh
2011-09-16 16:11 ` Guido Trentalancia
2011-09-16 16:11 ` Guido Trentalancia
2011-09-16 16:11 ` Justin P. Mattock
2011-09-23 16:30 ` Guido Trentalancia
2011-09-23 17:38 ` Daniel J Walsh
2011-09-23 19:09 ` Guido Trentalancia
2011-09-23 20:45 ` Eric Paris
2011-09-23 21:12 ` Guido Trentalancia
2011-09-23 21:17 ` Eric Paris
2011-09-23 22:38 ` Guido Trentalancia [this message]
2011-09-23 23:12 ` Eric Paris
2011-09-26 13:38 ` Daniel J Walsh
2011-09-27 12:46 ` Stephen Smalley
2011-09-27 16:40 ` Guido Trentalancia
2011-09-27 18:00 ` Daniel J Walsh
2011-09-16 16:02 ` Guido Trentalancia
2011-09-16 16:02 ` Guido Trentalancia
2011-09-16 16:18 ` Justin P. Mattock
2011-09-16 16:27 ` Guido Trentalancia
2011-09-16 16:27 ` Guido Trentalancia
2011-09-16 16:33 ` Justin P. Mattock
2011-09-16 16:24 ` Justin P. Mattock
2011-09-16 16:30 ` Guido Trentalancia
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=1316817499.2487.89.camel@vortex \
--to=guido@trentalancia.com \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--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.