From: Martin Orr <martin@martinorr.name>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Chris PeBenito <pebenito@gentoo.org>,
Eamon Walsh <ewalsh@tycho.nsa.gov>,
SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Xorg modprobe denials
Date: Thu, 03 Jan 2008 17:25:49 +0000 [thread overview]
Message-ID: <477D1A9D.7000900@martinorr.name> (raw)
In-Reply-To: <1199374256.12626.292.camel@gorn.columbia.tresys.com>
On 03/01/08 15:30, Christopher J. PeBenito wrote:
> On Wed, 2007-12-19 at 21:11 +0000, Martin Orr wrote:
>> On 18/12/07 13:57, Stephen Smalley wrote:
>>> On Tue, 2007-12-18 at 08:34 -0500, Stephen Smalley wrote:
>>>> On Mon, 2007-12-17 at 22:47 -0500, Chris PeBenito wrote:
>>>>> Based on the other kernel messages, I'm guessing that the insmod
>>>>> succeeded despite the tty and capability denials? If so I suppose we
>>>>> can dontaudit it.
>>>> I don't think we want to dontaudit the capability denials.
>>> And just to note, denials from insmod can be triggered either by
>>> userspace activity of insmod or by the module initialization code of the
>>> loaded module.
>> I find that on an SMP machine I need both the sys_nice capabability and
>> setsched on kernel_t to load modules.
>>
>> This is because stop_machine() is called by sys_init_module(), so it makes
>> sense to me to add these to kernel_load_module().
>>
>> Index: policy/modules/kernel/kernel.if
>> ===================================================================
>> --- policy/modules/kernel/kernel.if (revision 2560)
>> +++ policy/modules/kernel/kernel.if (working copy)
>> @@ -330,6 +330,9 @@
>>
>> allow $1 self:capability sys_module;
>> typeattribute $1 can_load_kernmodule;
>> +
>> + allow $1 self:capability sys_nice;
>> + kernel_setsched($1)
>> ')
>
> Are these rules are inherent to anything that loads a module or specific
> to insmod? This patch only makes sense if its the former.
>
It happens inside the init_module system call in the kernel, so anything
that loads a module needs it.
--
Martin Orr
--
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:[~2008-01-03 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 3:14 Xorg modprobe denials Eamon Walsh
2007-12-18 3:47 ` Chris PeBenito
2007-12-18 13:34 ` Stephen Smalley
2007-12-18 13:57 ` Stephen Smalley
2007-12-19 21:11 ` Martin Orr
2008-01-03 15:30 ` Christopher J. PeBenito
2008-01-03 17:25 ` Martin Orr [this message]
2008-05-22 12:29 ` refpolicy: syscall init_module needs sys_nice & setsched Václav Ovsík
2008-05-22 18:29 ` Christopher J. PeBenito
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=477D1A9D.7000900@martinorr.name \
--to=martin@martinorr.name \
--cc=cpebenito@tresys.com \
--cc=ewalsh@tycho.nsa.gov \
--cc=pebenito@gentoo.org \
--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.