From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCHv2 0/8] Portage-related updates
Date: Tue, 6 Sep 2011 14:08:30 -0400 [thread overview]
Message-ID: <4E66619E.40903@tresys.com> (raw)
In-Reply-To: <20110903141833.GA25374@siphos.be>
On 09/03/11 10:18, Sven Vermeulen wrote:
> This is a revised set of portage-related patches, excluding those that have
> been merged in the reference policy already.
>
> The patchset primarily adds
> - support for rc_exec_t (for Gentoo-based distributions)
> - make portage_fetch_t a full application domain for layman/emerge-webrsync
> - allow portage_fetch_t to execute gpg (introduces a portage_gpg_t file
> type)
> - allow portage commands to be ran within system cronjobs
Merged, with some adjustments. It needs one further change (see other email).
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2011-09-06 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 14:18 [refpolicy] [PATCHv2 0/8] Portage-related updates Sven Vermeulen
2011-09-03 14:19 ` [refpolicy] [PATCHv2 1/8] Introduce rc_exec_t as file entry for initrc_t Sven Vermeulen
2011-09-03 14:20 ` [refpolicy] [PATCHv2 2/8] Allow gcc-config to execute rc Sven Vermeulen
2011-09-03 14:20 ` [refpolicy] [PATCHv2 3/8] Gentoo integrated run_init support re-executes rc Sven Vermeulen
2011-09-03 14:21 ` [refpolicy] [PATCHv2 4/8] Allow the sysadm domain to execute rc Sven Vermeulen
2011-09-03 14:21 ` [refpolicy] [PATCHv2 5/8] Introduce portage_fetch_t as an application domain Sven Vermeulen
2011-09-06 18:09 ` Christopher J. PeBenito
2011-09-03 14:22 ` [refpolicy] [PATCHv2 6/8] Introduce gpg_exec interface Sven Vermeulen
2011-09-03 14:22 ` [refpolicy] [PATCH 7/8] Allow portage to call gpg Sven Vermeulen
2011-09-03 14:23 ` [refpolicy] [PATCH 8/8] Allow cron to execute portage commands Sven Vermeulen
2011-09-06 18:08 ` Christopher J. PeBenito [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=4E66619E.40903@tresys.com \
--to=cpebenito@tresys.com \
--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.