You are not logged in.
The long anticipated perl updates have finally arrived and, while in the case of apparmor-libapparmor, there are potential temporary fixes to the path variable, there is no clear consensus on the best method to adopt. (see here.)
Before I proceed to temporarily patch my local copy with a potentially unreliable fix, I have a slight issue I need to clear up, namely: “If I am not actively modifying, enforcing or disabling apparmor-profiles, does the path variable need an immediate fix?”
I am obviously not an expert, but I suspect the answer will largely depend on the individual ‘use-case’. So, for me:
I primarily use apparmor as a backend to Firejail and disable audit at boot.
I only occasionally modify, disable or enforce apparmor-profiles.
Systemctl shows Apparmor to be working as expected.
Tests show that the loaded apparmor profiles are behaving as expected.
I would be greatly interested in hearing your views on whether to try a temporary fix or leave it until the AUR package is patched.
Irvine
Edited to clarify it is the apparmor profiles which are working as expected
Last edited by IrvineHimself (2017-09-29 01:57:00)
Et voilà, elle arrive. La pièce, le sous, peut-être qu'il arrive avec vous!
Offline