From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
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, 09 Jun 2020 13:35:14 -0400 [thread overview]
Message-ID: <2006844.2enhIMKrvE@x2> (raw)
In-Reply-To: <20200609171555.itbllvtgjdanbbk7@madcap2.tricolour.ca>
On Tuesday, June 9, 2020 1:15:55 PM EDT Richard Guy Briggs wrote:
> On 2020-06-09 10:00, Lakshmi Ramasubramanian wrote:
> > On 6/9/20 9:43 AM, Steve Grubb wrote:
> > > > The number in parenthesis is the error code (such as ENOMEM, EINVAL,
> > > > etc.) IMA uses this format for reporting TPM errors in one of the
> > > > audit
> > > > messages (In ima_add_template_entry()). I followed the same pattern.
> > > >
> > > > Would it be better if the value for "cause" is formatted as
> > > >
> > > > cause=hashing_error_-22
> > > >
> > > > cause=alloc_entry_-12
> > >
> > > Neither fit the name=value style that all other events follow. What
> > > would fit the style is something like this:
> > >
> > > cause=hashing_error errno=-22
> > > cause=alloc_entry errno=-12
> > >
> > > Would this be OK? Also, errno is only to illustrate. You can name it
> > > something else as long as there are no use case collisions with our
> > > dictionary of field names.
> > >
> > > https://github.com/linux-audit/audit-documentation/blob/master/specs/fi
> > > elds/ field-dictionary.csv
> >
> > I am fine with this.
Thanks, this makes interpreting it a couple lines of code.
> > "errno" is currently not listed in the dictionary of audit message field
> > names (Thanks for the pointer to this one Steve)
It can be easily added.
> > Mimi - please let me know if you have any concerns with adding the
> > "result" code in "errno" field in integrity_audit_msg().
>
> 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.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
WARNING: multiple messages have this Message-ID (diff)
From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
linux-integrity@vger.kernel.org, linux-audit@redhat.com,
zohar@linux.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] IMA: Add audit log for failure conditions
Date: Tue, 09 Jun 2020 13:35:14 -0400 [thread overview]
Message-ID: <2006844.2enhIMKrvE@x2> (raw)
In-Reply-To: <20200609171555.itbllvtgjdanbbk7@madcap2.tricolour.ca>
On Tuesday, June 9, 2020 1:15:55 PM EDT Richard Guy Briggs wrote:
> On 2020-06-09 10:00, Lakshmi Ramasubramanian wrote:
> > On 6/9/20 9:43 AM, Steve Grubb wrote:
> > > > The number in parenthesis is the error code (such as ENOMEM, EINVAL,
> > > > etc.) IMA uses this format for reporting TPM errors in one of the
> > > > audit
> > > > messages (In ima_add_template_entry()). I followed the same pattern.
> > > >
> > > > Would it be better if the value for "cause" is formatted as
> > > >
> > > > cause=hashing_error_-22
> > > >
> > > > cause=alloc_entry_-12
> > >
> > > Neither fit the name=value style that all other events follow. What
> > > would fit the style is something like this:
> > >
> > > cause=hashing_error errno=-22
> > > cause=alloc_entry errno=-12
> > >
> > > Would this be OK? Also, errno is only to illustrate. You can name it
> > > something else as long as there are no use case collisions with our
> > > dictionary of field names.
> > >
> > > https://github.com/linux-audit/audit-documentation/blob/master/specs/fi
> > > elds/ field-dictionary.csv
> >
> > I am fine with this.
Thanks, this makes interpreting it a couple lines of code.
> > "errno" is currently not listed in the dictionary of audit message field
> > names (Thanks for the pointer to this one Steve)
It can be easily added.
> > Mimi - please let me know if you have any concerns with adding the
> > "result" code in "errno" field in integrity_audit_msg().
>
> 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.
-Steve
next prev parent reply other threads:[~2020-06-09 17:37 UTC|newest]
Thread overview: 24+ 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-08 21:53 ` Lakshmi Ramasubramanian
2020-06-09 12:54 ` Richard Guy Briggs
2020-06-09 12:54 ` Richard Guy Briggs
2020-06-09 15:40 ` Steve Grubb
2020-06-09 15:40 ` Steve Grubb
2020-06-09 15:58 ` Lakshmi Ramasubramanian
2020-06-09 15:58 ` Lakshmi Ramasubramanian
2020-06-09 16:43 ` Steve Grubb
2020-06-09 16:43 ` Steve Grubb
2020-06-09 17:00 ` Lakshmi Ramasubramanian
2020-06-09 17:00 ` Lakshmi Ramasubramanian
2020-06-09 17:14 ` Mimi Zohar
2020-06-09 17:14 ` Mimi Zohar
2020-06-09 17:15 ` Richard Guy Briggs
2020-06-09 17:15 ` Richard Guy Briggs
2020-06-09 17:33 ` Mimi Zohar
2020-06-09 17:33 ` Mimi Zohar
2020-06-09 17:35 ` Steve Grubb [this message]
2020-06-09 17:35 ` Steve Grubb
2020-06-09 18:03 ` Lakshmi Ramasubramanian
2020-06-09 18:03 ` Lakshmi Ramasubramanian
2020-06-09 17:04 ` Mimi Zohar
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=2006844.2enhIMKrvE@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nramas@linux.microsoft.com \
--cc=rgb@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 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.