From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH]: dontaudit sys_module wpa_supplicant
Date: Sun, 20 Mar 2011 15:53:13 +0100 [thread overview]
Message-ID: <1300632793.28926.5.camel@tesla.lan> (raw)
In-Reply-To: <201103201812.14967.russell@coker.com.au>
On Sun, 2011-03-20 at 18:12 +1100, Russell Coker wrote:
> On Sunday 20 March 2011 12:24:03 Guido Trentalancia wrote:
> > > Which kernel modules?
> >
> > Should be kernel modules which provide cryptographic algorithms needed by
> > wpa_supplicant for certain authentication and encryption functions
> > employed in some wireless ethernet protocols.
>
> Sounds like we want to allow the wpa_suplicant to do this.
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.
See Bug#515136 on Debian but even more importantly Bug#684415 on Fedora.
If there are specific requirements from different distributions we can
use ifdef(distro).
Regards,
Guido
next prev parent reply other threads:[~2011-03-20 14:53 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 [this message]
2011-03-20 15:05 ` Sven Vermeulen
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=1300632793.28926.5.camel@tesla.lan \
--to=guido@trentalancia.com \
--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.