From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Joshua Brindle <method@manicmethod.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
SELinux List <selinux@tycho.nsa.gov>
Subject: Re: [PATCH] libselinux: introduce enforcing mode override option
Date: Tue, 06 Nov 2007 16:56:50 -0500 [thread overview]
Message-ID: <4730E322.4020203@tycho.nsa.gov> (raw)
In-Reply-To: <4730D9A6.6050306@manicmethod.com>
Joshua Brindle wrote:
> Eamon Walsh wrote:
>> Introduces an enforcing mode override option, so the object manager
>> can bring up the AVC in permissive mode on an enforcing system, or
>> vice versa.
>>
>
> This is probably more useful but we actually had something like this
> with the userspace security server where you could run the USS in
> permissive or enforcing independent of the kernel security server.
> Ofcourse this would mean its still a global setting across all access
> managers using the USS.
>
Interesting, I would think that the USS would only serve up "raw"
decisions like the kernel security server does. The permissive setting
is a construct of the AVC layer.
--
Eamon Walsh <ewalsh@tycho.nsa.gov>
National Security Agency
--
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:[~2007-11-06 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 18:31 [PATCH] libselinux: refactor AVC netlink code Eamon Walsh
2007-11-01 16:51 ` Stephen Smalley
2007-11-05 20:15 ` [PATCH] libselinux: introduce enforcing mode override option Eamon Walsh
2007-11-06 17:10 ` Stephen Smalley
2007-11-06 21:50 ` Eamon Walsh
2007-11-08 21:26 ` Stephen Smalley
2007-11-06 21:16 ` Joshua Brindle
2007-11-06 21:56 ` Eamon Walsh [this message]
2007-11-07 2:22 ` Joshua Brindle
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=4730E322.4020203@tycho.nsa.gov \
--to=ewalsh@tycho.nsa.gov \
--cc=method@manicmethod.com \
--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.