From: pebenito@gentoo.org (Chris PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] optional_policy blocks
Date: Tue, 18 Jan 2011 18:51:26 -0500 [thread overview]
Message-ID: <4D36277E.3010400@gentoo.org> (raw)
In-Reply-To: <1295384185.7557.5.camel@tesla.lan>
On 1/18/2011 3:56 PM, Guido Trentalancia wrote:
> Hello again !
>
> On Tue, 18/01/2011 at 17.05 +0100, Dominick Grift wrote:
>> Sounds strange indeed. Are you sure it is not including any of the
>> policy in optional policy block or just some?
>>
>> If it is just incidental then it could be an error in the interface in
>> the optional policy block.
>>
>> If this really applies to all optional policy then i guess something
>> else is going on.
>
> Everything has been sorted out now. Maybe I was just getting confused by
> the many denials...
>
> Optional policy blocks get included in the build.
>
> I shall post my patch to the git reference policy very soon. Should it
> be posted with PATCH or RFC in the subject of the message ? I need
> comments... How do you generally post patches that need comments here ?
>
> It would be a patch that allows the latest reference policy to work on a
> modern system with dbus and xserver...
>
> I look forward to hearing from you.
Here's the info for contributing:
http://oss.tresys.com/projects/refpolicy/wiki/HowToContribute
--
Chris PeBenito
<pebenito@gentoo.org>
Developer,
Hardened Gentoo Linux
next prev parent reply other threads:[~2011-01-18 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 14:39 [refpolicy] optional_policy blocks Guido Trentalancia
2011-01-18 14:58 ` Dominick Grift
2011-01-18 15:53 ` Guido Trentalancia
2011-01-18 16:05 ` Dominick Grift
2011-01-18 20:56 ` Guido Trentalancia
2011-01-18 23:51 ` Chris PeBenito [this message]
2011-01-18 16:16 ` Guido Trentalancia
2011-01-18 16:27 ` Dominick Grift
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=4D36277E.3010400@gentoo.org \
--to=pebenito@gentoo.org \
--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.