All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: KaiGai Kohei <kaigai@ak.jp.nec.com>
Cc: Joshua Brindle <method@manicmethod.com>,
	SE Linux <selinux@tycho.nsa.gov>,
	Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: typebounds lookup from userspace
Date: Tue, 07 Oct 2008 15:30:54 -0400	[thread overview]
Message-ID: <48EBB8EE.7040906@tycho.nsa.gov> (raw)
In-Reply-To: <48EB9B57.5090304@tycho.nsa.gov>

Eamon Walsh wrote:
> KaiGai Kohei wrote:
>   
>> Joshua Brindle wrote:
>>   
>>     
>>> For symbol labeling purposes for policy access control we need to be able
>>>     
>>>       
>>  > to look up symbol hierarchy relationships. I expect we'll do this by exporting
>>  > the symbol hierarchy via selinuxfs. Does anyone have suggestions on what that
>>  > should look like? Do we want to export additional information on the symbols
>>  > at the same time?
>>
>> I noticed that userspace object manager also need an interface to get metadata
>> of types to support permissive domain. Currently, we don't have any interface
>> to know what domain should be handled as permissive domain.
>>
>> If "/selinux/access" can return the 6th value to show whether the given query
>> should be handled as permissive domain or not, it helps userspace object managers.
>>   
>>     
>
> Why does a userspace object manager need to know if a domain is marked
> permissive?  That should be hidden behind security_compute_av().
>   

Whoops, nevermind.

I looked at the patches and they seem reasonable, but there may be a
compatibility issue with the extra flags thing.  What happens if
libselinux expects it but it's not there?

Also minor nit, making the flags structure field into a bitmap would
eliminate the need for a #define, i.e.   "unsigned long permissive:1"


>   
>> It is undesirable for me to add a new interface to query whether the given domain
>> is permissive or not, because it cannot avoid atomicity matter.
>>
>> Thanks,
>>   
>>     
>
>
>   


-- 
Eamon Walsh <ewalsh@tycho.nsa.gov>
National Security Agency


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

  parent reply	other threads:[~2008-10-07 19:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 14:07 typebounds lookup from userspace Joshua Brindle
2008-09-19 14:26 ` Stephen Smalley
2008-09-19 14:32   ` Joshua Brindle
2008-09-19 15:07     ` Stephen Smalley
2008-09-19 15:42       ` Valdis.Kletnieks
2008-09-19 15:47       ` Joshua Brindle
2008-09-19 15:54         ` Stephen Smalley
2008-09-19 15:57           ` Joshua Brindle
2008-09-19 18:38           ` Joshua Brindle
2008-10-07  7:10 ` KaiGai Kohei
2008-10-07  9:45   ` permissive domain interface (Re: typebounds lookup from userspace) KaiGai Kohei
2008-10-07 17:24   ` typebounds lookup from userspace Eamon Walsh
2008-10-07 18:14     ` Stephen Smalley
2008-10-07 19:30     ` Eamon Walsh [this message]
2008-10-08  1:22       ` KaiGai Kohei

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=48EBB8EE.7040906@tycho.nsa.gov \
    --to=ewalsh@tycho.nsa.gov \
    --cc=kaigai@ak.jp.nec.com \
    --cc=method@manicmethod.com \
    --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.