Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34280 - [linux] Tomoyo kernel config options no longer works with systemd
Attached to Project:
Arch Linux
Opened by Abelardo Ricart (aricart) - Tuesday, 12 March 2013, 17:25 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 12 March 2013, 18:42 GMT
Opened by Abelardo Ricart (aricart) - Tuesday, 12 March 2013, 17:25 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 12 March 2013, 18:42 GMT
|
DetailsDescription:
When activated, Tomoyo fails to create new domains with this kernel. This is because the pathname specified via CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER (/usr/lib/systemd/systemd) is not yet passed to the execve() request after the pathname specified via CONFIG_SECURITY_TOMOYO_POLICY_LOADER (/sbin/tomoyo-init) became visible. CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER can now safely be changed to /sbin/init (symlink to /usr/lib/systemd/systemd) since our /init tries to pass /sbin/init to the execve() request. After this is done, Tomoyo behaves as expected and creates new domains in the kernel policy. Additional info: * linux 3.8.2-1 [testing] Steps to reproduce: 1) Install tomoyo-tools and the [core] or [testing] linux package. 2) Initialize policies with /usr/lib/tomoyo/init_policy 3) Reboot. 4) Run tomoyo-editpolicy and wonder why the kernel hasn't added new domains in the Domain Transition Editor =) |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Tuesday, 12 March 2013, 18:42 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#34057
Tuesday, 12 March 2013, 18:42 GMT
Reason for closing: Duplicate
Additional comments about closing: