apparmor/libraries/libapparmor/testsuite/test_multi/exec02.profile

/usr/bin/wireshark {
  /usr/lib64/wireshark/extcap/androiddump mrix,

}
add log testcases for exec with and without target= - in complain mode, exec events include target=... - in enforce mode, the log message doesn't include target=... Note that the utils tests skip exec events (they'd be interactive), therefore exec*.profile doesn't contain an exec rule. 2019-07-27 22:23:15 +02:00			`/usr/bin/wireshark {`
test exec events/rules in test-libapparmor-test_multi.py So far, exec events were accidentally skipped in test-libapparmor-test_multi.py because aa[profile][hat] was not initialized, and ask_exec() exited early because of this. Initialize aa[profile][hat] in the test to fix this. To avoid that someone needs to select "inherit" each time the tests run, add an optional default_ans parameter to ask_exec(), and let the test call it with 'CMD_ix'. (In case you wonder - defaulting to CMD_cx would ask to sanitize the environment. CMD_ix avoids this.) Also, we have to copy over aa[profile][hat] to log_dict in the test because ask_exec() modifies aa[...], but the test only checks its local log_dict. Finally, add the expected exec rules to the *.profile files 2024-10-20 22:42:18 +02:00			`/usr/lib64/wireshark/extcap/androiddump mrix,`

add log testcases for exec with and without target= - in complain mode, exec events include target=... - in enforce mode, the log message doesn't include target=... Note that the utils tests skip exec events (they'd be interactive), therefore exec*.profile doesn't contain an exec rule. 2019-07-27 22:23:15 +02:00			`}`