From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: running make relabel from a cronjob
Date: Tue, 24 Aug 2004 15:53:15 +0100 [thread overview]
Message-ID: <20040824145315.GD4698@lkcl.net> (raw)
In-Reply-To: <1093348538.1800.45.camel@moss-spartans.epoch.ncsc.mil>
On Tue, Aug 24, 2004 at 07:55:38AM -0400, Stephen Smalley wrote:
> On Tue, 2004-08-24 at 07:07, Luke Kenneth Casson Leighton wrote:
> > the following patches allow the attached /etc/cron.d/selinux program
> > to successfully run.
> >
> > this is for a user-only system where root access will not be given
> > out, and there won't be any maintenance or support, either.
> >
> > i heard from someone that Fedora also has a cronjob doing a make
> > relabel too, so i am slightly confused that the strict selinux policy
> > doesn't presently have this already oh well.
>
> See the cron_can_relabel boolean in crond.te and the fixfiles.cron
> script in policycoreutils. If CRONTYPE=relabel is in
> /etc/selinux/config and the cron_can_relabel boolean is enabled, then
> cron will (and can) relabel. Otherwise, cron will merely check file
> contexts and mail a report about incorrect contexts. It doesn't need to
> access policy sources; there is an installed file_contexts file in
> /etc/selinux/$SELINUXTYPE/contexts/files that is used at runtime for
> restorecon, fixfiles, etc.
ah ha!
great. thank you v. much.
l.
--
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.
prev parent reply other threads:[~2004-08-24 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 11:07 running make relabel from a cronjob Luke Kenneth Casson Leighton
2004-08-24 11:55 ` Stephen Smalley
2004-08-24 14:53 ` Luke Kenneth Casson Leighton [this message]
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=20040824145315.GD4698@lkcl.net \
--to=lkcl@lkcl.net \
--cc=sds@epoch.ncsc.mil \
--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.