FS#38220 - [tomoyo-tools] 2.5.0.20130406-2 Advice for TOMOYO_trigger is wrong

Attached to Project: Community Packages
Opened by Florian (Katastrophe) - Saturday, 21 December 2013, 18:52 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 26 February 2014, 11:53 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,

when TOMOYO_trigger is set to the command line according to the installation advice to TOMOYO_trigger=/usr/bin/init Tomoyo does not work properly(at all?): For example tomoyo-editpolicy shows only the kernel domain.

dmesg output:

[ 0.003387] TOMOYO Linux initialized

Setting it to TOMOYO_trigger=/usr/lib/systemd/systemd fixes the issue

dmesg output

[ 0.003387] TOMOYO Linux initialized
[ 6.241253] TOMOYO: 2.5.0

How can I ensure that I always have the correct init path in my boot configuration?

Greetings
This task depends upon

Closed by  Sergej Pupykin (sergej)
Wednesday, 26 February 2014, 11:53 GMT
Reason for closing:  Fixed
Comment by Florian (Katastrophe) - Saturday, 21 December 2013, 20:32 GMT
Answering my own question:

> How can I ensure that I always have the correct init path in my boot configuration?

As CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER is set properly in the stock configuration files, leaving out TOMOYO_trigger is the best approach.

Loading...