All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@manicmethod.com>
To: russell@coker.com.au
Cc: SE-Linux <selinux@tycho.nsa.gov>, Karl MacMillan <kmacmillan@tresys.com>
Subject: Re: recommending interfaces for audit2allow
Date: Wed, 14 Jul 2010 08:26:14 -0400	[thread overview]
Message-ID: <4C3DACE6.7000706@manicmethod.com> (raw)
In-Reply-To: <201007101022.46235.russell@coker.com.au>

Russell Coker wrote:
> corenet_tcp_connect_mysqld_port(foo_milter_t)
>
> I think that we need a way for an interface file to recommend itself to have a
> higher priority for certain matches.  For example the above policy line does
> permit foo_milter_t to talk to a MySQL server on a different system.  But you
> probably want something like the following:
>
> mysql_tcp_connect(foo_milter_t)
> optional_policy(`
>    mysql_stream_connect(foo_milter_t)
> ')
>
> So it seems that audit2allow should know that mysql_tcp_connect() is a
> preferred option to corenet_tcp_connect_mysqld_port() and that having an
> option to connect to a Unix domain socket would be good.
>
> Also maybe we should have a single interface with an optional section for
> MySQL client access.
>

Agreed. This seems like it could be solved if sepolgen just 
automatically demoted corenet_* since that would probably be the 
majority of cases where this happens (since corenet is allowed to 
essentially break abstractions).

--
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.

      reply	other threads:[~2010-07-14 12:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10  0:22 recommending interfaces for audit2allow Russell Coker
2010-07-14 12:26 ` Joshua Brindle [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=4C3DACE6.7000706@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=kmacmillan@tresys.com \
    --cc=russell@coker.com.au \
    --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.