From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
To: Steve Grubb <sgrubb@redhat.com>, Richard Guy Briggs <rgb@redhat.com>
Cc: linux-integrity@vger.kernel.org, linux-audit@redhat.com,
linux-kernel@vger.kernel.org, zohar@linux.ibm.com
Subject: Re: [PATCH v3] IMA: Add audit log for failure conditions
Date: Tue, 9 Jun 2020 11:03:28 -0700 [thread overview]
Message-ID: <2e3bc793-0d29-5434-1da3-2bcc34ed9012@linux.microsoft.com> (raw)
In-Reply-To: <2006844.2enhIMKrvE@x2>
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
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2020-06-09 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 21:53 [PATCH v3] IMA: Add audit log for failure conditions Lakshmi Ramasubramanian
2020-06-09 12:54 ` Richard Guy Briggs
2020-06-09 15:40 ` Steve Grubb
2020-06-09 15:58 ` Lakshmi Ramasubramanian
2020-06-09 16:43 ` Steve Grubb
2020-06-09 17:00 ` Lakshmi Ramasubramanian
2020-06-09 17:14 ` Mimi Zohar
2020-06-09 17:15 ` Richard Guy Briggs
2020-06-09 17:33 ` Mimi Zohar
2020-06-09 17:35 ` Steve Grubb
2020-06-09 18:03 ` Lakshmi Ramasubramanian [this message]
2020-06-09 17:04 ` Mimi Zohar
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=2e3bc793-0d29-5434-1da3-2bcc34ed9012@linux.microsoft.com \
--to=nramas@linux.microsoft.com \
--cc=linux-audit@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgb@redhat.com \
--cc=sgrubb@redhat.com \
--cc=zohar@linux.ibm.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 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).