ClickAppArmor

Differences between revisions 15 and 16
⇤ ← Revision 15 as of 2014-11-13 21:59:56 →
Size: 2584
Editor: jdstrand
Comment:
← Revision 16 as of 2014-11-13 22:02:38 → ⇥
Size: 2449
Editor: jdstrand
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * Reboot before installing the new MPs
Line 14: Line 15:
 * Examine `sudo aa-status` and verify it looks ok. It should report many profiles are loaded for click packages. Perform `sudo aa-status|wc -l`. You might want to save the output of `sudo aa-status` in $HOME for comparison later. '''IMPORTANT''': you should not have uninstalled or upgraded any click packages since the last reboot. If unsure, reboot now, then do `sudo aa-status|wc -l` before proceeding.  * Examine `sudo aa-status` and verify it looks ok. It should report many profiles are loaded for click packages. Perform `sudo aa-status|wc -l`. You might want to save the output of `sudo aa-status` in $HOME for comparison later.

Dependents/Clients

  • upstart-app-launch (uses apparmor kernel interface via upstart to load the AppArmor profile generated by click-apparmor)

  • ubuntu-sdk (eventually, once it uses the new aa-clickquery command)

Test Plan

  • Install image on phone
  • Reboot before installing the new MPs
  • Install freshly build MPs that are needed for landing

  • Examine sudo aa-status and verify it looks ok. It should report many profiles are loaded for click packages. Perform sudo aa-status|wc -l. You might want to save the output of sudo aa-status in $HOME for comparison later.

  • Reboot

  • Verify that sudo aa-status|wc -l has the same output after the reboot with the new packages as before the reboot with the old packages

  • Verify apps launch
    • Launch an app (eg, start the weather app). Does it start?

    • Run sudo aa-status, is the process for the app running under confinement (in enforce mode)?

  • Ensure that webapps launch
    • launch a webapp (eg, start the facebook webapp). Does it start?

    • Run sudo aa-status, is the process for the webapp running under confinement (in enforce mode)?

  • Run image tests on Ubuntu Touch (emulator or touch image):

    $ bzr branch lp:qa-regression-testing
$ cd qa-regression-testing
$ adb push ./tests /tmp/tests
$ adb shell /tmp/tests/image/unprivileged/click-apparmor
$ adb shell /tmp/tests/image/unprivileged/apparmor-easyprof-ubuntu

    • Note: if testing a new framework, be sure to declare the new framework in /usr/share/click/frameworks/<framework>.framework before running the above image tests

  • Run autopkgtests

    1. make sure the schroot is up to date (eg, autopkgtest-trusty-amd64)

    2. download the new AppArmor binaries to ../binary

    3. run the tests:

      • 14.04: 

        $ adt-run -B ../binary/*.deb --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-trusty-amd64 || echo "** AUTOPKGTESTS FAILED"

      • 14.10: 

        $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-utopic-amd64 || echo "** AUTOPKGTESTS FAILED"

Process/Merges/TestPlans/ClickAppArmor (last edited 2016-08-26 16:39:43 by jdstrand)