apparmor/libraries/libapparmor/testsuite
John Johansen c37586cd11 Merge Avoid aa-notify crash on log events without operation=
Some STATUS log events trigger a crash in aa-notify because the log
line doesn't have operation=. Examples are:

    type=AVC msg=audit(1630913351.586:4): apparmor="STATUS" info="AppArmor Filesystem Enabled" pid=1 comm="swapper/0"

    type=AVC msg=audit(1630913352.610:6): apparmor="STATUS" info="AppArmor sha1 policy hashing enabled" pid=1 comm="swapper/0"

Fix this by not looking at log events without operation=

Also add one of the example events as libapparmor testcase.

Fixes: https://gitlab.com/apparmor/apparmor/-/issues/194
MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/797
Acked-by: John Johansen <john.johansen@canonical.com>
2021-09-13 23:02:15 +00:00
..
config move libapparmor into the libraries directory 2008-05-19 22:48:31 +00:00
lib move libapparmor into the libraries directory 2008-05-19 22:48:31 +00:00
libaalogparse.test treewide: spelling/typo fixes in comments and docs 2020-12-01 12:47:11 -08:00
test_multi Merge Avoid aa-notify crash on log events without operation= 2021-09-13 23:02:15 +00:00
Makefile.am build: add and use global EXTRA_WARNINGS from common/Make.rules 2020-05-28 16:55:50 -07:00
test_multi.c libapparmor: logparse: fix RECORD_INVALID for valid log 2019-07-02 01:01:37 -07:00