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

  1. 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):
    2. $ git clone --branch apertis/v2025 https://gitlab.apertis.org/tests/apparmor-dbus.git
  2. Copy the test directory apparmor-dbus to the target device:
    3. $ DUT_IP=<device-ip>
    $ scp -r apparmor-dbus user@$DUT_IP:
  3. Log into the target device:
    4. $ ssh user@$DUT_IP

Execution Steps

  1. Enter test directory:
    2. $ cd apparmor-dbus
  2. Execute the following command:
    3. $ 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.