On Thu, 2020-06-25 at 15:14 -0400, Paul Moore wrote:
> On Wed, Jun 24, 2020 at 1:25 PM Lakshmi Ramasubramanian
> wrote:
> >
> > On 6/23/20 12:58 PM, Mimi Zohar wrote:
> >
> > Hi Steve\Paul,
> >
> > >> Sample audit messages:
> > >>
> > >> [6.303048] audit: type=1804 audit(1592506281.627:2):
On Wed, Jun 24, 2020 at 1:25 PM Lakshmi Ramasubramanian
wrote:
>
> On 6/23/20 12:58 PM, Mimi Zohar wrote:
>
> Hi Steve\Paul,
>
> >> Sample audit messages:
> >>
> >> [6.303048] audit: type=1804 audit(1592506281.627:2): pid=1 uid=0
> >> auid=4294967295 ses=4294967295 subj=kernel
On 6/23/20 12:58 PM, Mimi Zohar wrote:
Hi Steve\Paul,
Sample audit messages:
[6.303048] audit: type=1804 audit(1592506281.627:2): pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel op=measuring_key
cause=ENOMEM comm="swapper/0" name=".builtin_trusted_keys" res=0
errno=-12
My only
On Thu, 2020-06-18 at 14:10 -0700, Lakshmi Ramasubramanian wrote:
> process_buffer_measurement() and ima_alloc_key_entry() functions need to
> log an audit message for auditing integrity measurement failures.
>
> Add audit message in these two functions. Remove "pr_devel" log message
> in
process_buffer_measurement() and ima_alloc_key_entry() functions need to
log an audit message for auditing integrity measurement failures.
Add audit message in these two functions. Remove "pr_devel" log message
in process_buffer_measurement().
Sample audit messages:
[6.303048] audit: