linux-kernel - Re: [PATCH v3] IMA: Add audit log for failure conditions

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:   Tue, 9 Jun 2020 11:03:28 -0700
From:   Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>
To:     Steve Grubb <sgrubb@...hat.com>,
        Richard Guy Briggs <rgb@...hat.com>
Cc:     linux-integrity@...r.kernel.org, linux-audit@...hat.com,
        zohar@...ux.ibm.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] IMA: Add audit log for failure conditions

On 6/9/20 10:35 AM, Steve Grubb wrote:
>>
>> If it is added, it should be appended to the end of the record since it
>> is an existing record format, then in the case of res=1, errno= should
>> still be present (not swing in and out) and just contain zero.  (Or
>> another value if there is a non-fatal warning?)
> 
> This is not a searchable field, so it can go anywhere. If it is searchable,
> ausearch expects ordering of other searchable fields.
> 

Thank you for the clarification Steve.

I'll add "errno=" right after "cause=".

Also, "errno" will always be present - will be set to 0 if status is 
"success" (res=1) and a non-zero value for failure (res=0)

thanks,
  -lakshmi