All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stefan Schulze Frielinghaus <stefan@seekline.net>
Cc: selinux@tycho.nsa.gov
Subject: Re: prelink, cron-job and SELinux compliance
Date: Mon, 10 Mar 2008 09:00:12 -0400	[thread overview]
Message-ID: <47D530DC.5030606@redhat.com> (raw)
In-Reply-To: <1204970465.4229.10.camel@vogon>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Schulze Frielinghaus wrote:
> 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.
Does labeling the directory cron_var_run_t make it work?

Please open a bug report on prelink to put the cache file in this new
directory.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkfVMNwACgkQrlYvE4MpobM2fACcCsoJisgY2LL9x19bwqiN7W6F
IQUAoIRGXttjVPA5mkVIenfP2DEGpvGi
=ybll
-----END PGP SIGNATURE-----

--
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.

  reply	other threads:[~2008-03-10 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-08 10:01 prelink, cron-job and SELinux compliance Stefan Schulze Frielinghaus
2008-03-10 13:00 ` Daniel J Walsh [this message]
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=47D530DC.5030606@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=stefan@seekline.net \
    /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.