From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] dccp socket support
Date: Tue, 27 Sep 2011 09:36:36 -0400 [thread overview]
Message-ID: <4E81D164.1030601@tresys.com> (raw)
In-Reply-To: <1317110300.2861.22.camel@x220.mydomain.internal>
On 09/27/11 03:58, Dominick Grift wrote:
> Can dccp socket support be merged/added to refpolicy?
>
> The dccp_socket class was added but refpolicy was never adapted to this
> addition.
I definitely don't oppose this, but I don't remember seeing much usage of DCCP. I wouldn't reject a patch because it has DCCP.
> We tried to do this in Fedora, so that might be usable to some degree.
> ( i guess it can at least be used as rough guide to what we think needs
> to be done to add this support )
>
> Please see the two commits regarding dccp sockets:
>
> http://git.fedorahosted.org/git/?p=selinux-policy.git&a=search&h=HEAD&st=commit&s=dccp
I took a cursory look, and it seems ok, but some of the unrelated changes would have to be filtered out.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2011-09-27 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 7:58 [refpolicy] dccp socket support Dominick Grift
2011-09-27 13:36 ` 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=4E81D164.1030601@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.