From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] system_udev.patch
Date: Thu, 18 Mar 2010 14:24:11 -0400 [thread overview]
Message-ID: <4BA26FCB.3000209@redhat.com> (raw)
In-Reply-To: <1268853470.13301.110.camel@gorn.columbia.tresys.com>
On 03/17/2010 03:17 PM, Christopher J. PeBenito wrote:
> On Tue, 2010-02-23 at 16:19 -0500, Daniel J Walsh wrote:
>
>> http://people.fedoraproject.org/~dwalsh/SELinux/F13/system_udev.patch
>>
>> Allow other domains to unlink udev_tbl_t
>>
> Needs a different interface, adding it to udev_rw_db() is an excessive
> permission for the interface.
>
>
>> Uses netlink sockets
>>
> Do you have any information on this? It would be best to get a specific
> class added for this socket, rather than use the generic netlink_socket.
>
>
Added during F11. Same time as netlink_kobj_uevent_socket. Might be
the same thing.
> Otherwise merged.
>
>
>> Creates device_t symlinks
>>
>> Reads consolekit_var_run
>>
>> dontaudit leaks from hal
>>
>> Searches rpm logs (probably a leak)
>>
>> Transitions to usbmux_d
>>
>>
>>
>>
>
Updated patch including new policy for usbmuxd.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: udev.patch
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20100318/aa7f25a4/attachment.pl
next prev parent reply other threads:[~2010-03-18 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 21:19 [refpolicy] system_udev.patch Daniel J Walsh
2010-03-17 19:17 ` Christopher J. PeBenito
2010-03-18 18:24 ` Daniel J Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-26 23:45 Daniel J Walsh
2009-11-12 22:16 Daniel J Walsh
2009-11-25 14:44 ` Christopher J. PeBenito
2009-03-20 17:00 Daniel J Walsh
2009-04-07 14:37 ` Christopher J. PeBenito
2009-03-02 22:36 Daniel J Walsh
2009-03-19 18:21 ` 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=4BA26FCB.3000209@redhat.com \
--to=dwalsh@redhat.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.