All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@linux.ibm.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Eric Paris <eparis@redhat.com>,
	linux-audit@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] audit: add filterkey to special audit messages
Date: Wed, 04 May 2022 07:22:54 +0200	[thread overview]
Message-ID: <yt9dbkwddg7l.fsf@linux.ibm.com> (raw)
In-Reply-To: <CAHC9VhQ44G1oXLHTf7FmqwzYBRNW=5EPHod1uMTLhaY3sK_Qeg@mail.gmail.com> (Paul Moore's message of "Tue, 3 May 2022 12:57:21 -0400")

Paul Moore <paul@paul-moore.com> writes:

> On Tue, May 3, 2022 at 5:02 AM Sven Schnelle <svens@linux.ibm.com> wrote:
>>
>> For automated filtering/testing it is useful to have the
>> filter key logged in the message.
>>
>> Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
>> ---
>>  kernel/auditsc.c | 1 +
>>  1 file changed, 1 insertion(+)
>
> The SOCKETCALL record, along with all of the others generated inside
> show_special(), are associated with a SYSCALL record which carries the
> "key=" field.  As a general rule we try very hard not to duplicate
> fields across records in a single audit event.

Ok, thanks. Guess you can ignore both patches than.

Thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Sven Schnelle <svens@linux.ibm.com>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org,
	Eric Paris <eparis@redhat.com>
Subject: Re: [PATCH 2/2] audit: add filterkey to special audit messages
Date: Wed, 04 May 2022 07:22:54 +0200	[thread overview]
Message-ID: <yt9dbkwddg7l.fsf@linux.ibm.com> (raw)
In-Reply-To: <CAHC9VhQ44G1oXLHTf7FmqwzYBRNW=5EPHod1uMTLhaY3sK_Qeg@mail.gmail.com> (Paul Moore's message of "Tue, 3 May 2022 12:57:21 -0400")

Paul Moore <paul@paul-moore.com> writes:

> On Tue, May 3, 2022 at 5:02 AM Sven Schnelle <svens@linux.ibm.com> wrote:
>>
>> For automated filtering/testing it is useful to have the
>> filter key logged in the message.
>>
>> Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
>> ---
>>  kernel/auditsc.c | 1 +
>>  1 file changed, 1 insertion(+)
>
> The SOCKETCALL record, along with all of the others generated inside
> show_special(), are associated with a SYSCALL record which carries the
> "key=" field.  As a general rule we try very hard not to duplicate
> fields across records in a single audit event.

Ok, thanks. Guess you can ignore both patches than.

Thanks!

--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit


  reply	other threads:[~2022-05-04  5:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03  9:02 [PATCH 1/2] audit: add call argument to socketcall auditing Sven Schnelle
2022-05-03  9:02 ` Sven Schnelle
2022-05-03  9:02 ` [PATCH 2/2] audit: add filterkey to special audit messages Sven Schnelle
2022-05-03  9:02   ` Sven Schnelle
2022-05-03 16:57   ` Paul Moore
2022-05-03 16:57     ` Paul Moore
2022-05-04  5:22     ` Sven Schnelle [this message]
2022-05-04  5:22       ` Sven Schnelle
2022-05-03 13:32 ` [PATCH 1/2] audit: add call argument to socketcall auditing kernel test robot
2022-05-03 13:32   ` kernel test robot
2022-05-03 13:32 ` kernel test robot
2022-05-03 13:32   ` kernel test robot
2022-05-03 14:04 ` kernel test robot
2022-05-03 14:04   ` kernel test robot
2022-05-03 16:07 ` Paul Moore
2022-05-03 16:07   ` Paul Moore
2022-05-03 17:16 ` Steve Grubb
2022-05-03 17:16   ` Steve Grubb

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=yt9dbkwddg7l.fsf@linux.ibm.com \
    --to=svens@linux.ibm.com \
    --cc=eparis@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    /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.