https://bugzilla.suse.com/show_bug.cgi?id=1194332
https://bugzilla.suse.com/show_bug.cgi?id=1194332#c3
Knut Alejandro Anderssen Gonz�lez changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Knut Alejandro Anderssen Gonz�lez ---
We have moved back to the previous behavior in yast2-security module using the
security=module paramater instead of lsm as using it to specify only the Major
module to be activated looks wrong as we have seen in this bug report. We could
write also integrity in case it is AppArmor is selected during installation but
from implementation that would be strange.
The fix should be available in yast2-security-4.4.5
See https://github.com/yast/yast-security/pull/118 for more details.
SR: https://build.suse.de/request/show/261749
--
You are receiving this mail because:
You are on the CC list for the bug.