|Main Archive Page > Month Archives > selinux archives|
In a modular policy context file
does not with the following error during installation:
libsepol.mls_from_string: invalid MLS context SystemHigh
libsepol.mls_from_string: could not construct mls context structure
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert
system_u:object_r:jcdx_icm_var_t:SystemHigh to sid
/etc/selinux/mls/contexts/files/file_contexts: line 818 has invalid
context system_u:object_r:jcdx_icm_var_t:SystemHigh libsemanage.semanage_install_active: setfiles returned error code 1.
In both cases the creation of the .pp file works.
This concerns me because we have a number of daemons that run at labels other than SystemHigh. The raw context for these daemons must be hardcoded in the policy developers environment, which presumes we know the mapping on the target machine, which we don't.
We can work around this in the RPM spec file, creating the .fc files on the fly using the setrans.conf of the target machine and compiling during the installation, but this is complex and feels like we are working around a bug.
How can I specify a file context with a human readable label in a modular policy?
joe -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to firstname.lastname@example.org with the words "unsubscribe selinux" without quotes as the message.