mcelroyj
10th January 2005, 07:27 PM
I've recently become more and more annoyed with SELinux consistently barfing audit messages during the boot process and into my dmesg logs. It's set to run in permissive mode, which I know produces many more audit messages that enforcing would.
However, I would like to find a permament solution to this. I have the targeted policy and sources installed, and would really like to be able to add rules to selinux so that users, daemons, and programs have access to the proper resources.
Thus far, I haven't been able to find any good resources/tutorials on how to turn something like:
audit(1105292918.856:0): avc: denied { execute } for pid=732
path=/lib/tls/libc-2.3.4.so dev=sdb7 ino=2621453
scontext=user_u:system_r:syslogd_t tcontext=root:object_r:lib_t tclass=file
into an actual SELinux policy rule.
Are there any good tutorials on this process?
Thanks,
jeremiah
However, I would like to find a permament solution to this. I have the targeted policy and sources installed, and would really like to be able to add rules to selinux so that users, daemons, and programs have access to the proper resources.
Thus far, I haven't been able to find any good resources/tutorials on how to turn something like:
audit(1105292918.856:0): avc: denied { execute } for pid=732
path=/lib/tls/libc-2.3.4.so dev=sdb7 ino=2621453
scontext=user_u:system_r:syslogd_t tcontext=root:object_r:lib_t tclass=file
into an actual SELinux policy rule.
Are there any good tutorials on this process?
Thanks,
jeremiah