From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Best approach for adding inet socket support for milters?
Date: Wed, 14 Sep 2011 12:27:59 -0400 [thread overview]
Message-ID: <4E70D60F.5090705@tresys.com> (raw)
In-Reply-To: <4E70B8C8.6000608@tresys.com>
On 09/14/11 10:23, Christopher J. PeBenito wrote:
> On 09/12/11 10:37, Paul Howarth wrote:
>> I'd rather return to my original suggestion of having a milter_port_t be
>> supported out of the box and then let admins use semanage to define any
>> ports they wanted to use as milter_port_t.
>
> This is fine. I can't remember if I originally rejected this (I'm guessing I did), but I'm fine with it now. We already have examples of this, eg, stunnel. We should look into augmenting the corenetwork infrastructure so that the network_port() macro can handle no defined ports, so that interfaces for the type will be created. I believe this already works for the interface generation, but the te side needs to be tweaked to not emit an incomplete portcon statement.
This ended up being straightforward. I updated corenetwork so that it supports defining a port type without labeling any specific ports. That'll get the interfaces generated so we can write policy correctly (look at the contrib commit if you're not sure what I mean).
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-09-14 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 14:37 [refpolicy] Best approach for adding inet socket support for milters? Paul Howarth
2011-09-14 14:23 ` Christopher J. PeBenito
2011-09-14 16:27 ` Christopher J. PeBenito [this message]
2011-09-15 14:17 ` Paul Howarth
2011-09-20 14:00 ` 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=4E70D60F.5090705@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.