There is a 3rd level of check that can be applied if those sha1sums don't match.
sys/kernel/security/apparmor/policy/profiles/usr.sbin.libvirtd.*/raw_hash should be the same as the sha1sum for raw_data i.e $ cat sys/kernel/security/apparmor/policy/profiles/usr.sbin.libvirtd.*/raw_hash bbdf01649dd59ab1bd3d3696788aa0be9f6f6b03 $ sha1sum /sys/kernel/security/apparmor/policy/profiles/usr.sbin.libvirtd.*/raw_data bbdf01649dd59ab1bd3d3696788aa0be9f6f6b03 /sys/kernel/security/apparmor/policy/profiles/usr.sbin.libvirtd.18/raw_data The raw_hash sum is taken at load time, and can be used to verify the sum of what was loaded and policy is applying. The raw_hash and sha1sum raw_data should always match unless there is memory corruption, or a bug in reading out the raw_data file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594902 Title: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1594902/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
