From: Stefan Schulze Frielinghaus <stefan@seekline.net>
To: selinux@tycho.nsa.gov
Subject: prelink, cron-job and SELinux compliance
Date: Sat, 08 Mar 2008 11:01:05 +0100 [thread overview]
Message-ID: <1204970465.4229.10.camel@vogon> (raw)
In RHEL/CentOS 5.1 a cron job (/etc/cron.daily/prelink) runs prelink.
The cron job itself removes a file (/etc/prelink.cache) if necessary and
updates the database. This does not work with the strict SELinux policy.
To solve this I patched the prelink application to
use /var/cache/prelink/prelink.cache instead of /etc/prelink.cache
This would make it more easier to write SELinux policies. But know my
actual question is how to modify the cron job to work properly? All cron
jobs on my system are labeled as bin_t. This would mean that
system_crond_t needs write/create etc. permissions
on /var/cache/prelink. Thats not really nice and I would prefer to
create a domain like cron_script_prelink_t for /etc/cron.daily/prelink
which gets all the rights to manage /var/cache/prelink.
What are your ideas to handle cron scripts properly?
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2008-03-08 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 10:01 Stefan Schulze Frielinghaus [this message]
2008-03-10 13:00 ` prelink, cron-job and SELinux compliance Daniel J Walsh
2008-03-16 11:45 ` Stefan Schulze Frielinghaus
2008-03-17 18:37 ` Daniel J Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1204970465.4229.10.camel@vogon \
--to=stefan@seekline.net \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.