linux-kernel - Re: [PATCH 2/2] audit: add filterkey to special audit messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 04 May 2022 07:22:54 +0200
From:   Sven Schnelle <svens@...ux.ibm.com>
To:     Paul Moore <paul@...l-moore.com>
Cc:     Eric Paris <eparis@...hat.com>, linux-audit@...hat.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] audit: add filterkey to special audit messages

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

> On Tue, May 3, 2022 at 5:02 AM Sven Schnelle <svens@...ux.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@...ux.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!