From: Dominick Grift <dominick.grift@gmail.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Joshua Brindle <brindle@quarksecurity.com>,
selinux <selinux@tycho.nsa.gov>
Subject: Re: Is this a bug in sesearch, or ...?
Date: Mon, 16 Sep 2013 14:09:29 +0200 [thread overview]
Message-ID: <1379333369.6787.32.camel@d30> (raw)
In-Reply-To: <1379333222.6787.30.camel@d30>
On Mon, 2013-09-16 at 14:07 +0200, Dominick Grift wrote:
> On Mon, 2013-09-16 at 07:57 -0400, Stephen Smalley wrote:
> > On 09/16/2013 03:35 AM, Dominick Grift wrote:
> > > On Sun, 2013-09-15 at 12:54 -0400, Joshua Brindle wrote:
> > >> Dominick Grift wrote:
> > >>> I was explaining the concept of (type) attributes using the domain type
> > >>> attribute as an example on IRC, and a sharp person embarrassed me by
> > >>> noting that the following rule returns nothing where he would have
> > >>> expected something:
> > >>>
> > >>> sesearch -A -d -s domain -c process -p fork
> > >>>
> > >>> Why does this not return anything? Is is because the target is "self"?
> > >>
> > >> "self" is resolved by the compiler, it isn't present in the kernel binary.
> > >>
> > >> You specified -d "do not search for type's attributes" and then gave an
> > >> attribute as the source. I'm not sure what the intended behavior was but
> > >> excluding the -d gave me back a large set of rules.
> > >
> > > The result i expected would have been the exact (direct) rule as
> > > specified in the policy:
> > >
> > > allow domain self : process fork;
> > >
> > > So not the large list that one gets without the -d option because that
> > > is not the direct rule
> >
> > direct means "granted to an individual type, not via attribute". So it
> > omits any rules written in terms of attributes.
> >
>
> Thanks, alright this is probably last attempt to understand this but really that is not my experience:
>
> Take for example this comparison:
>
> # sesearch -A -d -t file_type | head -n 3
> Found 383 semantic av rules:
> allow prelude_lml_t file_type : filesystem getattr ;
> allow files_unconfined_type file_type : filesystem { mount remount
> unmount getattr relabelfrom relabelto transition associate quotamod
> quotaget } ;
>
> # sesearch -A -t file_type | head -n 3
> Found 40415 semantic av rules:
> allow mscan_var_run_t mscan_var_run_t : filesystem associate ;
> allow xguest_usertype tetex_data_t : lnk_file { read getattr } ;
>
> The former does not "expand" the target type attribute whereas the
> latter expands the type attribute
>
Scratch the above. it now starts to sink in slowly here ( must be monday
)
So in that case would be nice if we have the functionality to query type
attribute av rules without them being expanded.
>
>
>
>
>
>
--
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:[~2013-09-16 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 16:44 Is this a bug in sesearch, or ...? Dominick Grift
2013-09-15 16:54 ` Joshua Brindle
2013-09-16 7:35 ` Dominick Grift
2013-09-16 11:57 ` Stephen Smalley
2013-09-16 12:07 ` Dominick Grift
2013-09-16 12:09 ` Dominick Grift [this message]
2013-09-16 12:10 ` Stephen Smalley
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=1379333369.6787.32.camel@d30 \
--to=dominick.grift@gmail.com \
--cc=brindle@quarksecurity.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.