From: Dennis Wronka <linuxweb@gmx.net>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux@tycho.nsa.gov
Subject: Re: Policy loading problem
Date: Wed, 20 May 2009 23:44:13 +0800 [thread overview]
Message-ID: <200905202344.16667.linuxweb@gmx.net> (raw)
In-Reply-To: <1242831553.20082.406.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]
Just an idea:
Wouldn't it be possible to split CONFIG_SECURITY_SELINUX_DEVELOP into two
options, pretty much like CONFIG_SECURITY_SELINUX_BOOTPARAM and
CONFIG_SECURITY_SELINUX_DISABLE?
I like the idea because it would prevent somebody that has physical access to
set SELinux to permissive (and thus practically disabling its protection) on
boot, but still keep the option for root (either as sysadm_r or, preferably,
as secadm_r) to switch to permissive mode after boot.
On Wednesday 20 May 2009 22:59:13 Stephen Smalley wrote:
> On Wed, 2009-05-20 at 22:57 +0800, Dennis Wronka wrote:
> > Okay, here we go:
> >
> > I unmounted /selinux and then got this:
> > load_policy: Can't load policy: Invalid argument
> >
> > I attached my kernel-config and the two traces (trace1 for the "Device or
> > resource busy"-error, trace2 for the "Invalid argument"-error).
>
> Ahem. Your kernel config has these SELinux options:
> CONFIG_SECURITY_SELINUX=y
> # CONFIG_SECURITY_SELINUX_BOOTPARAM is not set
> # CONFIG_SECURITY_SELINUX_DISABLE is not set
> # CONFIG_SECURITY_SELINUX_DEVELOP is not set
> CONFIG_SECURITY_SELINUX_AVC_STATS=y
> CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
> # CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
>
> Note that your kernel config does not support:
> 1) The selinux= kernel boot parameter
> (CONFIG_SECURITY_SELINUX_BOOTPARAM),
> 2) The ability to disable SELinux from /sbin/init based on
> SELINUX=disabled in /etc/selinux/config
> (CONFIG_SECURITY_SELINUX_DISABLE),
> 3) Permissive mode (CONFIG_SECURITY_SELINUX_DEVELOP)
>
> Is that what you intended? IOW, you cannot boot permissive, and the
> load policy logic is failing when it tries to switch to permissive mode
> (write to /selinux/enforce).
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-05-20 15:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 10:19 avc: denied null Dominick Grift
2009-05-18 12:50 ` Stephen Smalley
2009-05-18 12:59 ` Dominick Grift
2009-05-18 18:52 ` Eamon Walsh
2009-05-20 3:11 ` Eamon Walsh
2009-05-20 7:21 ` Policy loading problem Dennis Wronka
2009-05-20 11:46 ` Stephen Smalley
2009-05-20 13:46 ` Dennis Wronka
2009-05-20 13:49 ` Stephen Smalley
2009-05-20 14:07 ` Dennis Wronka
2009-05-20 14:09 ` Stephen Smalley
2009-05-20 14:21 ` Stephen Smalley
2009-05-20 14:42 ` Dennis Wronka
2009-05-20 14:40 ` Stephen Smalley
2009-05-20 14:57 ` Dennis Wronka
2009-05-20 14:59 ` Stephen Smalley
2009-05-20 15:22 ` Dennis Wronka
2009-05-20 15:44 ` Dennis Wronka [this message]
2009-05-20 16:44 ` Stephen Smalley
2009-05-20 21:01 ` Paul Howarth
2009-05-20 15:10 ` Stephen Smalley
2009-07-07 15:53 ` Joshua Brindle
2009-05-20 11:08 ` avc: denied null Dominick Grift
2009-05-21 2:36 ` Eamon Walsh
2009-05-21 12:19 ` Dominick Grift
2009-05-21 20:15 ` Dominick Grift
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=200905202344.16667.linuxweb@gmx.net \
--to=linuxweb@gmx.net \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@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.