All of lore.kernel.org
 help / color / mirror / Atom feed
From: dominick.grift@gmail.com (grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 10/11] Support stunnel_read_config for startup
Date: Sun, 09 Dec 2012 15:03:19 +0100	[thread overview]
Message-ID: <1355061799.1797.75.camel@localhost> (raw)
In-Reply-To: <1355000222-7297-11-git-send-email-sven.vermeulen@siphos.be>

On Sat, 2012-12-08 at 21:57 +0100, Sven Vermeulen wrote:
> When stunnel starts up, the init script reads in the configuration file to find
> the location of the PID file. As such, we need to provide initrc_t with read
> access to the stunnel configuration.

This was merged thanks

I made changes to it though to include listing of stunnel config dirs
and reading of stunnel config symlinks additionally for consistency

> Create a stunnel_read_config() interface for this purpose.
> 
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  stunnel.if |   19 +++++++++++++++++++
>  1 files changed, 19 insertions(+), 0 deletions(-)
> 
> diff --git a/stunnel.if b/stunnel.if
> index 47fea00..882db16 100644
> --- a/stunnel.if
> +++ b/stunnel.if
> @@ -23,3 +23,22 @@ interface(`stunnel_service_domain',`
>  	domtrans_pattern(stunnel_t, $2, $1)
>  	allow $1 stunnel_t:tcp_socket rw_socket_perms;
>  ')
> +
> +########################################
> +## <summary>
> +##	Read the stunnel configuration
> +## </summary>
> +## <param name="domain">
> +##	<summary>
> +##	Domain allowed access.
> +##	</summary>
> +## </param>
> +#
> +interface(`stunnel_read_config',`
> +	gen_require(`
> +		type stunnel_etc_t;
> +	')
> +
> +	files_search_etc($1)
> +	read_files_pattern($1, stunnel_etc_t, stunnel_etc_t)
> +')

  reply	other threads:[~2012-12-09 14:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-08 20:56 [refpolicy] [PATCH 00/11] Contrib changes Sven Vermeulen
2012-12-08 20:56 ` [refpolicy] [PATCH 01/11] Moving sandbox code to sandbox section (v2) Sven Vermeulen
2012-12-09 13:51   ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 02/11] Allow sandbox to log violations Sven Vermeulen
2012-12-09 13:55   ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 03/11] Initial policy for logsentry Sven Vermeulen
2012-12-08 22:03   ` grift
2013-10-05  7:22   ` Dominick Grift
2012-12-08 20:56 ` [refpolicy] [PATCH 04/11] Initial policy for makewhatis Sven Vermeulen
2012-12-08 21:57   ` grift
2012-12-09  9:44     ` Sven Vermeulen
2012-12-09 10:59       ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 05/11] Use rw_fifo_file_perms Sven Vermeulen
2012-12-09 13:58   ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 06/11] Apache should not depend on gpg Sven Vermeulen
2012-12-09 13:59   ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 07/11] Mark make.profile entry as portage_conf_t Sven Vermeulen
2012-12-08 21:46   ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 08/11] Named init script creates rundir Sven Vermeulen
2012-12-09 14:00   ` grift
2012-12-08 20:57 ` [refpolicy] [PATCH 09/11] Add ~/.maildir as a valid maildir destination Sven Vermeulen
2012-12-09 14:01   ` grift
2012-12-08 20:57 ` [refpolicy] [PATCH 10/11] Support stunnel_read_config for startup Sven Vermeulen
2012-12-09 14:03   ` grift [this message]
2012-12-08 20:57 ` [refpolicy] [PATCH 11/11] Updates on stunnel policy Sven Vermeulen
2012-12-09 14:04   ` grift

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=1355061799.1797.75.camel@localhost \
    --to=dominick.grift@gmail.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.