All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Systemd policy
Date: Fri, 23 Oct 2015 15:23:31 -0400	[thread overview]
Message-ID: <562A8933.7010908@tresys.com> (raw)
In-Reply-To: <562533CF.2010205@tresys.com>

On 10/19/2015 2:17 PM, Christopher J. PeBenito wrote:
> The long-awaited (and long-overdue) policy changes for systemd are ready
> to be merged.  Because of the size of the changes, I have done this as
> GitHub pull requests. [1][2]

This has been merged.  There were several revisions of the original
patches and a few known issues that came from the final reviews (see the
github bug tracker[3] for more info)


> The policy was written against a RHEL7 system, so it likely needs more
> work to get it fully up to speed on today's systemd and on other
> distributions.
> 
> Credits:
> * Major contributions to the policy were from Mike Palmiotto of the
> Tresys CLIP team.
> * Laurent Bigonville also made some contributions.
> 
> The purpose of this notice is to allow for comment, in case there are
> concerns about the overall structure.  If you have concerns about
> individual rules, we can address them after the policy is merged.
> 
> I plan to merge the policy Friday afternoon (UTC -4).
> 
> [1] https://github.com/TresysTechnology/refpolicy/pull/8
> [2] https://github.com/TresysTechnology/refpolicy-contrib/pull/4
[3] https://github.com/TresysTechnology/refpolicy/issues


-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  parent reply	other threads:[~2015-10-23 19:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 18:17 [refpolicy] Systemd policy Christopher J. PeBenito
2015-10-20 11:35 ` Dominick Grift
2015-10-23 19:23 ` Christopher J. PeBenito [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-12  7:06 [refpolicy] systemd policy Russell Coker
2014-01-12 12:18 ` Laurent Bigonville
2014-01-13 12:52   ` Russell Coker
2014-01-13 15:10     ` Daniel J Walsh
2014-01-13 19:02       ` Dominick Grift
2014-01-13 20:16         ` Daniel J Walsh
2014-01-13 20:22           ` Dominick Grift
2014-01-13 21:07             ` Dominick Grift
2014-01-14 14:49               ` Daniel J Walsh
2014-01-14 11:24           ` Dominick Grift
2014-01-13 23:37       ` Russell Coker
2014-01-14  9:46         ` Dominick Grift
2014-01-14  9:58           ` Dominick Grift
2014-01-14 12:35           ` Laurent Bigonville
2014-01-14 13:03             ` Dominick Grift
2014-01-27  6:56           ` Russell Coker
2014-02-06 14:40             ` Christopher J. PeBenito
2014-01-14 10:12         ` Dominick Grift
2014-01-14 12:22         ` Laurent Bigonville
2014-01-14 13:34         ` Christopher J. PeBenito
2014-01-14 13:54           ` Dominick Grift
2014-01-14 14:41           ` Laurent Bigonville
2014-01-14 14:55             ` Daniel J Walsh
2014-01-27 14:17           ` Miroslav Grepl
2014-02-06 16:32             ` 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=562A8933.7010908@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.