From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Cronjobs might create temporary directories
Date: Fri, 23 Sep 2011 21:11:54 +0200 [thread overview]
Message-ID: <20110923191154.GA31939@siphos.be> (raw)
In-Reply-To: <20110922184251.GA15227@siphos.be>
On Thu, Sep 22, 2011 at 08:42:51PM +0200, Sven Vermeulen wrote:
> If the system_cronjob_t domain is seen more like a "jump board" towards the
> application specific domains, I don't mind creating a makewhatis policy
> module and work from there onwards.
Giving the fact that the policy will probably read and write man_t together
with the usual suspects (_exec, _domtrans), is it okay to suggest a patch for
the miscfiles module? Or would you rather see an independent module?
I don't think I need to offer a _run or _role interface, since transitioning
from sysadm_t wouldn't be necessary. Or is it better to do that anyway?
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2011-09-23 19:11 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
2011-09-22 7:54 ` Dominick Grift
2011-09-22 18:42 ` Sven Vermeulen
2011-09-23 19:11 ` Sven Vermeulen [this message]
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=20110923191154.GA31939@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.