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 5/7 v2] init.if: Add init_daemon_run_file interface
Date: Fri, 07 Dec 2012 00:26:20 -0500	[thread overview]
Message-ID: <50C17DFC.6000506@tresys.com> (raw)
In-Reply-To: <1354745711-27404-1-git-send-email-bigon@debian.org>

On 12/5/2012 5:15 PM, Laurent Bigonville wrote:
> From: Laurent Bigonville <bigon@bigon.be>
>
> This is allowing initscripts to create pidfile and to let them
> transition to their context
> ---
>   policy/modules/system/init.if |   27 +++++++++++++++++++++++++++
>   1 file changed, 27 insertions(+)
>
> diff --git a/policy/modules/system/init.if b/policy/modules/system/init.if
> index 3f0c2d3..66a4869 100644
> --- a/policy/modules/system/init.if
> +++ b/policy/modules/system/init.if
> @@ -444,6 +444,33 @@ interface(`init_daemon_run_dir',`
>
>   ########################################
>   ## <summary>
> +##	Mark the file type as a pid file, allowing initrc_t
> +##	to create it
> +## </summary>
> +## <param name="filetype">
> +##	<summary>
> +##	Type to mark as a pid file
> +##	</summary>
> +## </param>
> +## <param name="name" optional="true">
> +##	<summary>
> +##	The name of the object being created.
> +##	</summary>
> +## </param>
> +#
> +interface(`init_daemon_run_file',`
> +	gen_require(`
> +		attribute pidfile;
> +		type initrc_t;
> +	')
> +
> +	typeattribute $1 pidfile;
> +
> +	files_pid_filetrans(initrc_t, $1, file, $2)
> +')

pidfile isn't owned by this module.  Additionally, I'm thinking that it would probably be better to generalize init_daemon_run_dir to take object classes as a parameter.... but I don't know what to call it.

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

  reply	other threads:[~2012-12-07  5:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 20:39 [refpolicy] [PATCH 1/7] Properly label all the ssh host keys Laurent Bigonville
2012-12-05 20:39 ` [refpolicy] [PATCH 2/7] Allow udev_t domain to read files labeled as consolekit_var_run_t Laurent Bigonville
2012-12-07  5:48   ` Christopher J. PeBenito
2012-12-05 20:39 ` [refpolicy] [PATCH 3/7] Label /var/run/shm as tmpfs_t Laurent Bigonville
2012-12-07  5:13   ` Christopher J. PeBenito
2012-12-15 22:29     ` Laurent Bigonville
2012-12-16 16:41       ` grift
2012-12-05 20:39 ` [refpolicy] [PATCH 4/7] authlogin.if: Add auth_create_pam_console_data_dirs and auth_pid_filetrans_pam_var_console interfaces Laurent Bigonville
2012-12-07  5:49   ` Christopher J. PeBenito
2012-12-05 20:39 ` [refpolicy] [PATCH 5/7] init.if: Add init_daemon_run_file interface Laurent Bigonville
2012-12-05 21:58   ` grift
2012-12-05 22:15     ` [refpolicy] [PATCH 5/7 v2] " Laurent Bigonville
2012-12-07  5:26       ` Christopher J. PeBenito [this message]
2012-12-05 20:39 ` [refpolicy] [PATCH 6/7] Label /etc/rc.d/init.d/x11-common as xdm_exec_t Laurent Bigonville
2012-12-07  5:50   ` Christopher J. PeBenito
2012-12-05 20:39 ` [refpolicy] [PATCH 7/7] Drop /etc/rc.d/init.d/xfree86-common filecontext definition Laurent Bigonville
2012-12-07  5:51   ` Christopher J. PeBenito
2012-12-07  5:48 ` [refpolicy] [PATCH 1/7] Properly label all the ssh host keys 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=50C17DFC.6000506@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.