From: Paul Howarth <paul@city-fan.org>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: [refpolicy] Milter Mail Filters
Date: Wed, 08 Oct 2008 14:05:59 +0100 [thread overview]
Message-ID: <48ECB037.2070203@city-fan.org> (raw)
In-Reply-To: <1223302377.2165.5.camel@gorn>
Christopher J. PeBenito wrote:
> On Mon, 2008-09-22 at 13:27 +0100, Paul Howarth wrote:
>> Updated patch: sendmail, when run as "newaliases", tries to getattr()
>> milter sockets as well as the directories they live in, so I changed
>> the
>> milter_getattr_all_data_dirs interface to milter_getattr_all_sockets.
>>
>> I also moved the call to this interface in mta.te out from the middle
>> of
>> a bunch of postfix-related lines.
>>
>> Paul.
>
> I think my last two comments are
>
> * you can't require milter_port_t. It doesn't seem like a generic port
> type would be useful anyway, otherwise there would be a port defined.
So I should change "allow milter_$1_t milter_port_t:tcp_socket
name_bind;" to "corenet_tcp_bind_generic_port($1_milter_t)"?
I can do that but I don't understand why milter_port_t should be any
different than say stunnel_port_t, which also doesn't have a default
port defined, and would be used in a similar way, i.e. an admin would
set up an application to use a specific port (a milter running over tcp
needs to have a port specified, just a tunnel set up using stunnel does
- they don't just bind to random generic ports).
> * milter vs milters inconsistency of naming
I'll rename the module and the file to milter then, though I'd hoped
that "milter" would have been accepted as an abbreviation of "milters".
> * derived types should have the prefix first, eg, $1_milter_t not
> milter_$1_t.
I'll change those.
Paul.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2008-10-08 13:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 15:25 [refpolicy] Milter Mail Filters Paul Howarth
2008-06-13 12:51 ` Paul Howarth
2008-06-13 14:23 ` Christopher J. PeBenito
2008-06-13 17:30 ` Paul Howarth
2008-07-18 12:58 ` Christopher J. PeBenito
2008-08-05 10:03 ` Paul Howarth
2008-09-05 13:26 ` Christopher J. PeBenito
2008-09-09 16:15 ` Paul Howarth
2008-09-22 12:27 ` Paul Howarth
2008-10-06 14:12 ` Christopher J. PeBenito
2008-10-08 13:05 ` Paul Howarth [this message]
2008-10-08 19:22 ` Christopher J. PeBenito
2008-10-10 18:24 ` Paul Howarth
2008-11-06 15:09 ` Christopher J. PeBenito
2008-11-06 15:24 ` Paul Howarth
2008-11-14 15:26 ` Christopher J. PeBenito
2008-11-17 15:05 ` Paul Howarth
2008-11-24 14:11 ` Christopher J. PeBenito
2008-11-24 14:34 ` Paul Howarth
2008-11-24 15:17 ` Christopher J. PeBenito
2008-11-24 16:07 ` Paul Howarth
2008-11-24 17:47 ` 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=48ECB037.2070203@city-fan.org \
--to=paul@city-fan.org \
--cc=cpebenito@tresys.com \
--cc=selinux@tycho.nsa.gov \
/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.