apparmor-dbus automated
critical
- Image Types:
- basesdk-amd64 / fixedfunction-armhf / fixedfunction-arm64 / fixedfunction-amd64 / hmi-armhf / hmi-arm64 / hmi-amd64 / sdk-amd64
- Image Deployment:
- APT, OSTree
- Type:
- functional
Description
Security infrastructure: AppArmor D-Bus mediation is part of strategic application and service confinement.
Pre Conditions
- Clone the tests repository from another computer (Note that the branch being tested may change depending on the release, please make sure to clone the correct branch for the release in question):
- Copy the test directory apparmor-dbus to the target device:
- Log into the target device:
$ git clone --branch apertis/v2025dev1 https://gitlab.apertis.org/tests/apparmor-dbus.git
$ DUT_IP=<device-ip>
$ scp -r apparmor-dbus user@$DUT_IP:
$ ssh user@$DUT_IP
Execution Steps
- Enter test directory:
- Execute the following command:
$ cd apparmor-dbus
$ LAUNCH_DBUS="no" common/run-aa-test ./dbus.expected ./dbus
Expected
The test should report pass and not fail:
dbus.expected: pass
Notes
- The results of the tests printed to the standard output are enough to determine whether they passed or fail.
- If you get a failure and need to report a bug please add the apparmor logs from sudo journalctl.