All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <brindle@quarksecurity.com>
To: Dominick Grift <dominick.grift@gmail.com>
Cc: selinux <selinux@tycho.nsa.gov>
Subject: Re: Is this a bug in sesearch, or ...?
Date: Sun, 15 Sep 2013 12:54:56 -0400	[thread overview]
Message-ID: <5235E660.2040602@quarksecurity.com> (raw)
In-Reply-To: <1379263465.20256.6.camel@d30>

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.


--
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:[~2013-09-15 16:55 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 [this message]
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
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=5235E660.2040602@quarksecurity.com \
    --to=brindle@quarksecurity.com \
    --cc=dominick.grift@gmail.com \
    --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.