From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH]: dontaudit sys_module wpa_supplicant
Date: Sun, 20 Mar 2011 16:05:04 +0100 [thread overview]
Message-ID: <20110320150504.GA16383@siphos.be> (raw)
In-Reply-To: <1300632793.28926.5.camel@tesla.lan>
On Sun, Mar 20, 2011 at 03:53:13PM +0100, Guido Trentalancia wrote:
> Not everybody likes that to happen. And surely there must be a good
> reason for having a "neverallow" rule in kernel/kernel.te which blocks
> everything.
The moment you set kernel_load_module(NetworkManager_t) you're all set. The
neverallow is on all domains that do not have the can_load_kernmodule
attribute set, and with kernel_load_moduel() you set it for the specified
domain.
There's a difference between "not everybody wants this" and "this is what is
needed to have the application work as it is intended to". In refpolicy, I
think we should aim at the latter. The former is more for security
administrators that want to create their own policy.
If the mass that doesn't want this is large enough, you might want to
introduce it with a tunable_policy...
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2011-03-20 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 1:24 [refpolicy] [PATCH]: dontaudit sys_module wpa_supplicant Guido Trentalancia
2011-03-20 7:12 ` Russell Coker
2011-03-20 14:53 ` Guido Trentalancia
2011-03-20 15:05 ` Sven Vermeulen [this message]
2011-03-20 15:47 ` Guido Trentalancia
2011-03-20 15:56 ` Sven Vermeulen
2011-03-20 16:18 ` Guido Trentalancia
2011-03-21 13:23 ` Christopher J. PeBenito
2011-03-20 21:55 ` Russell Coker
2011-03-20 22:41 ` Guido Trentalancia
2011-03-22 12:11 ` Daniel J Walsh
2011-03-22 13:42 ` Eric Paris
2011-03-23 14:59 ` Guido Trentalancia
2011-03-22 15:01 ` Guido Trentalancia
-- strict thread matches above, loose matches on Subject: below --
2011-03-21 14:07 [refpolicy] R: " Guido Trentalancia
2011-03-21 17:54 ` [refpolicy] " Guido Trentalancia
2011-03-19 20:13 Guido Trentalancia
2011-03-20 0:11 ` Russell Coker
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=20110320150504.GA16383@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=refpolicy@oss.tresys.com \
/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.