All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: ivg2@cornell.edu
Cc: jwcart2@epoch.ncsc.mil, SELinux <selinux@tycho.nsa.gov>,
	Stephen Smalley <sds@epoch.ncsc.mil>,
	James Morris <jmorris@redhat.com>
Subject: Re: More patches
Date: Wed, 06 Apr 2005 14:48:34 -0400	[thread overview]
Message-ID: <42542F02.2020304@redhat.com> (raw)
In-Reply-To: <1112810151.7822.4.camel@cobra.ivg2.net>

Ivan Gyurdiev wrote:

>> allow hald_t bin_t:file getattr;
>>-allow hald_t self:netlink_socket create_socket_perms;
>> allow hald_t self:netlink_kobject_uevent_socket create_socket_perms;
>> allow hald_t self:netlink_route_socket r_netlink_socket_perms;
>> allow hald_t self:capability { net_admin sys_admin dac_override dac_read_search mknod };
>>    
>>
>
>Now I get one of these...
>
>audit(1112809767.410:0): avc:  denied  { create } for  pid=7363
>exe=/usr/sbin/hald scontext=root:system_r:hald_t
>tcontext=root:system_r:hald_t tclass=netlink_socket
>
>...and the console is flooded with those:
>
>audit(1112809741.307:0): avc:  denied  { read } for  pid=2525
>exe=/usr/sbin/hald scontext=system_u:system_r:hald_t
>tcontext=system_u:system_r:hald_t tclass=netlink_socket
>
>Was this removed because of the kobject_uevent rule below it?
>I can't remember if that rule was there to begin with, or if it 
>was put in to address what I was debugging w/ Protocol 15 (?) being
>denied. 
>
>  
>
My understanding was that

 netlink_kobject_uevent_socket was added so that we would not need the netlink_socket rule.

Either I am wrong or you might need an updated kernel.

Dan

-- 



--
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.

  reply	other threads:[~2005-04-06 18:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03 12:50 some policy patches Russell Coker
2005-02-10 15:19 ` James Carter
2005-02-10 21:13   ` Daniel J Walsh
2005-04-06 11:51   ` More patches Daniel J Walsh
2005-04-06 12:25     ` James Carter
2005-04-06 12:27       ` Daniel J Walsh
2005-04-06 12:36       ` Daniel J Walsh
2005-04-06 17:55         ` Ivan Gyurdiev
2005-04-06 18:48           ` Daniel J Walsh [this message]
2005-04-06 18:13             ` Ivan Gyurdiev
     [not found]               ` <42543BBD.4090308@redhat.com>
     [not found]                 ` <1112814718.3817.6.camel@cobra.ivg2.net>
     [not found]                   ` <42544387.6010706@redhat.com>
2005-04-06 21:39                     ` Ivan Gyurdiev
2005-04-07 17:31                       ` James Carter
2005-04-06 19:13             ` James Carter
2005-04-07 12:13             ` Stephen Smalley
2005-04-07 17:31         ` James Carter
  -- strict thread matches above, loose matches on Subject: below --
2010-06-14  9:48 Sascha Hauer
2005-07-15 19:31 Ivan Gyurdiev
2005-07-18 14:31 ` Stephen Smalley
2005-07-18 14:54   ` Ivan Gyurdiev
2005-04-19  1:48 Daniel Barkalow
2002-08-27 18:12 more patches 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=42542F02.2020304@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=ivg2@cornell.edu \
    --cc=jmorris@redhat.com \
    --cc=jwcart2@epoch.ncsc.mil \
    --cc=sds@epoch.ncsc.mil \
    --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.