Skip to contentSkip to conversation

var_log_ksyms_t

DISCUSSION Carsten Grohmann 2 participants 4 messages Jul 22, 2002 – Jul 24, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

Wich program use the var_log_ksyms_t, I don't found anyfing about this. But the initrc domain label new files under /var/log with this security context. Why?

Thanks

Carsten

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#1 lore raw
Quoted 3 lines · Carsten Grohmann

Wich program use the var_log_ksyms_t, I don't found anyfing about this. But the initrc domain label new files under /var/log with this security context. Why?

On RedHat, rc.sysinit rotates any existing /var/log/ksyms.N files and dumps the contents of /proc/cpuinfo, /proc/modules, and /proc/ksyms to a newly created /var/log/ksyms.0 file. Consequently, the initrc.te file in the example policy includes a rule to place these files into their own
type: file_type_auto_trans(initrc_t, var_log_t, var_log_ksyms_t).

--
Stephen D. Smalley, NAI Labs
[email protected]

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#2 lore raw

Am Dienstag, 23. Juli 2002 14:16 schrieb Stephen Smalley:

Quoted 10 lines · Carsten Grohmann
Quoted 3 lines

Wich program use the var_log_ksyms_t, I don't found anyfing about this. But the initrc domain label new files under /var/log with this security context. Why?

On RedHat, rc.sysinit rotates any existing /var/log/ksyms.N files and dumps the contents of /proc/cpuinfo, /proc/modules, and /proc/ksyms to a newly created /var/log/ksyms.0 file. Consequently, the initrc.te file in the example policy includes a rule to place these files into their own
type: file_type_auto_trans(initrc_t, var_log_t, var_log_ksyms_t).

If I understand you right, rc.sysinit is the scricpt, who is starting the single rc-scriptes. And then it is not possible to change the domain for this job.

It is possible to overwrite the file_type_auto_trans instruction in an later script? This is may be simplier than to edit the init script.

The other is to change the xfs start script.

On Red Hat the xfs starting with the -daemon option or not ?

On SuSE it starts via startproc (start_daemon) with -nodaemon option and redirect the output to the /var/log directory. And this file is labled with the false context.

Carsten

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#3 lore raw
Quoted 3 lines · Carsten Grohmann

If I understand you right, rc.sysinit is the scricpt, who is starting the single rc-scriptes. And then it is not possible to change the domain for this job.

rc.sysinit is run once at boot time for system initialization (the si entry in /etc/inittab). We could possibly place it into a different domain, but I'm not sure that it is worthwhile.

Quoted 10 lines

It is possible to overwrite the file_type_auto_trans instruction in an later script? This is may be simplier than to edit the init script.

The other is to change the xfs start script.

On Red Hat the xfs starting with the -daemon option or not ?

On SuSE it starts via startproc (start_daemon) with -nodaemon option and redirect the output to the /var/log directory. And this file is labled with the false context.

On RedHat 7.1 and 7.2, xfs is run with -daemon.

If your rc scripts do not create a /var/log/ksyms.N file, you can certainly drop the file_type_auto_trans rule from your copy of the example policy. I'm sure that you have to customize it anyway for SuSE.

You could place the init script for xfs into its own domain, and define a file type transition for it.

--
Stephen D. Smalley, NAI Labs
[email protected]

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.