From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Elena Reshetova <elena.reshetova@gmail.com>,
"SELinux@tycho.nsa.gov" <SELinux@tycho.nsa.gov>
Cc: "filippo.bonazzi@aalto.fi" <filippo.bonazzi@aalto.fi>
Subject: Re: setoolsv4: tracking origin of a policy element
Date: Mon, 26 Oct 2015 09:16:06 -0400 [thread overview]
Message-ID: <562E2796.8000308@tresys.com> (raw)
In-Reply-To: <CALrft9-5ZFbJgiLZnXoeroAgqhZ+rmzCENXSgdqtyC5+_6pZ-w@mail.gmail.com>
On 10/26/2015 7:20 AM, Elena Reshetova wrote:
> While looking into the policy parser from setools v4, we noticed one
> thing that is missing: origin of a policy element. For example, given a
> certain rule or attribute, it would be great to know in what source file
> it was defined.
>
> In Android you can find this information by looking at produced
> policy.conf and its comment lines that indicate source file. However I
> don't know if it is the same for desktop selinux policy.
>
> Would it be acceptable to have this information as part of python class
> representing the parsed policy? It would be really useful for tools like
> policy linter, because it would be very much needed to point to the
That would be acceptable. Past versions of SETools supported that, but
it has not yet been a priority for v4.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2015-10-26 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 11:20 setoolsv4: tracking origin of a policy element Elena Reshetova
2015-10-26 13:16 ` Christopher J. PeBenito [this message]
2015-11-10 15:45 ` Filippo Bonazzi
2015-11-10 16:33 ` 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=562E2796.8000308@tresys.com \
--to=cpebenito@tresys.com \
--cc=SELinux@tycho.nsa.gov \
--cc=elena.reshetova@gmail.com \
--cc=filippo.bonazzi@aalto.fi \
/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.