All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Allow search within postgresql var directory for the stream connect interface
Date: Tue, 9 Oct 2012 10:20:25 -0400	[thread overview]
Message-ID: <507432A9.2090703@tresys.com> (raw)
In-Reply-To: <20121006142330.GA2856@siphos.be>

On 10/06/12 10:23, Sven Vermeulen wrote:
> Domains that are granted postgresql_stream_connect() need to be able to search
> through the postgresql_var_run_t directory (in which the socket is located).
> 
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  policy/modules/services/postgresql.if |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/policy/modules/services/postgresql.if b/policy/modules/services/postgresql.if
> index ecef19f..79ccc90 100644
> --- a/policy/modules/services/postgresql.if
> +++ b/policy/modules/services/postgresql.if
> @@ -431,6 +431,7 @@ interface(`postgresql_stream_connect',`
>  	files_search_pids($1)
>  	allow $1 postgresql_t:unix_stream_socket connectto;
>  	allow $1 postgresql_var_run_t:sock_file write;
> +	allow $1 postgresql_var_run_t:dir search_dir_perms;
>  	# Some versions of postgresql put the sock file in /tmp
>  	allow $1 postgresql_tmp_t:sock_file write;
>  ')

Looks like a good candidate to use stream_connect_pattern().

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

      reply	other threads:[~2012-10-09 14:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-06 14:23 [refpolicy] [PATCH 1/1] Allow search within postgresql var directory for the stream connect interface Sven Vermeulen
2012-10-09 14:20 ` 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=507432A9.2090703@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.