From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Cronjobs might create temporary directories
Date: Thu, 22 Sep 2011 08:04:05 +0200 [thread overview]
Message-ID: <20110922060405.GA13992@siphos.be> (raw)
In-Reply-To: <1316636711.24149.11.camel@x220.mydomain.internal>
On Wed, Sep 21, 2011 at 10:25:11PM +0200, Dominick Grift wrote:
> On Wed, 2011-09-21 at 21:23 +0200, Sven Vermeulen wrote:
> > Cronjobs, like makewhatis, want to create temporary directories
> > (and not only just temporary files).
>
> system_cronjob_t is a unconfined_domain(), did you disable or de-install
> the unconfined module?
Yup, in Gentoo we support "strict" (i.e. without the unconfined domain) for
servers and hope that this moves to workstations as well.
> Although allowing this for system_cronjob_t makes sense to me, it does
> make me wonder whether its better to just make the makewhatis and other
> known scripts cron_system_entry() instead.
In that case, makewhatis would require its own domain, and perhaps all other
scripts that want to create a temporary directory. I think that might give
too much overhead, although I do feel this is necessary in case of your next
paragraph:
> Some of these scripts need a lot of specific access (for example
> prelink), extending the system-cronjob domain to just allow all that
> makes it a very permissive domain. Oh wait, it is a unconfined domain
> already ;)
Indeed. It's about finding a good balance between manageability and security
I guess.
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2011-09-22 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 19:23 [refpolicy] [PATCH 1/1] Cronjobs might create temporary directories Sven Vermeulen
2011-09-21 20:25 ` Dominick Grift
2011-09-22 6:04 ` Sven Vermeulen [this message]
2011-09-22 7:54 ` Dominick Grift
2011-09-22 18:42 ` Sven Vermeulen
2011-09-23 19:11 ` Sven Vermeulen
2011-09-23 20:26 ` Dominick Grift
2011-09-27 12:49 ` Christopher J. PeBenito
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=20110922060405.GA13992@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=refpolicy@oss.tresys.com \
/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.