apparmor-bluez manual

high

Image Types:
target-armhf-internal / target-amd64
Image Deployment:
APT, OSTree
Type:
functional

Description

Test AppArmor profile for support for SPP profile (bluez-spp) and core functionalities (bluez-core).


Resources

  • Two Bluetooth adapters.

Pre Conditions

  1. From a PC, download and unpack the test data tarball from the gitlab test repository:
  2. $ wget https://gitlab.apertis.org/tests/apparmor-bluez/-/archive/master/apparmor-bluez.tar.gz

    $ tar -xvf apparmor-bluez.tar.gz

  3. Copy the apparmor-bluez-master-* to the target device:
  4. $ DUT_IP=<device-ip>

    $ scp -r apparmor-bluez-master-* user@$DUT_IP:

  5. Log into the target device:
  6. $ ssh user@$DUT_IP

  7. After log into the DUT, enter the test directory
  8. $ cd apparmor-bluez-master-*

  9. Note that the tarball may change depending on the release/branch being tested, please make sure to download the correct tarball for the release in question.
  10. Please note that connman disables bluetooth by default on a fresh image.
  11. Enable device:
  12. $ connmanctl enable bluetooth


Execution Steps

  1. Execute the following command:
  2. $ ./test-bluez


Expected

The following test results, which will appear in different places throughout the log:

R1.13a.1_bluez-spp.expected_underlying_tests: pass

R1.13a.1_bluez-spp.expected: pass

R1.13a.1_bluez-core.expected_underlying_tests: pass

R1.13a.1_bluez-core.expected: pass

Notes

  • This TC is based on other Bluez automated test cases, all of them should PASS in order to execute them against AppArmor.
  • If a subtest for this TC FAILs, check that the related test is PASSING.
  • It is worth to investigate AppArmor-side only if the original TC PASSes and the profiled version of it FAILs.
  • Any other scenario is either OK or worth waiting the original TC to PASS.