selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: Nicolas Iooss <nicolas.iooss@m4x.org>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH] python/sepolicy: search() also for dontaudit rules
Date: Tue, 18 Dec 2018 13:24:57 +0100	[thread overview]
Message-ID: <pjd4lbbuina.fsf@redhat.com> (raw)
In-Reply-To: <CAJfZ7==ehVcSkb1NdMch1mErAVMTevWuvQzd_JdTsmkb2WOsUQ@mail.gmail.com> (Nicolas Iooss's message of "Sat, 15 Dec 2018 16:28:12 +0100")

Nicolas Iooss <nicolas.iooss@m4x.org> writes:

> On Wed, Dec 12, 2018 at 4:28 PM Petr Lautrbach <plautrba@redhat.com> wrote:
>>
>> dontaudit rules were accidentally dropped during rewrite to SETools 4 API in
>> 97d5f6a2
>>
>> Fixes:
>> >>> import sepolicy
>> >>> sepolicy.search(['dontaudit'])
>> []
>>
>> Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
>
> Acked-by: Nicolas Iooss <nicolas.iooss@m4x.org>
>

Merged.

>> ---
>>
>> Same patch as https://lore.kernel.org/selinux/20180918134401.22956-1-plautrba@redhat.com/
>> but with a slightly reworded commit message
>>
>>  python/sepolicy/sepolicy/__init__.py | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/python/sepolicy/sepolicy/__init__.py b/python/sepolicy/sepolicy/__init__.py
>> index cd7af7cf..fbeb731d 100644
>> --- a/python/sepolicy/sepolicy/__init__.py
>> +++ b/python/sepolicy/sepolicy/__init__.py
>> @@ -344,6 +344,8 @@ def search(types, seinfo=None):
>>          tertypes.append(NEVERALLOW)
>>      if AUDITALLOW in types:
>>          tertypes.append(AUDITALLOW)
>> +    if DONTAUDIT in types:
>> +        tertypes.append(DONTAUDIT)
>>
>>      if len(tertypes) > 0:
>>          q = setools.TERuleQuery(_pol,
>> --
>> 2.19.2
>>

      reply	other threads:[~2018-12-18 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 15:28 [PATCH] python/sepolicy: search() also for dontaudit rules Petr Lautrbach
2018-12-15 15:28 ` Nicolas Iooss
2018-12-18 12:24   ` Petr Lautrbach [this message]

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=pjd4lbbuina.fsf@redhat.com \
    --to=plautrba@redhat.com \
    --cc=nicolas.iooss@m4x.org \
    --cc=selinux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).