All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Fwd: [PATCH] checkpolicy: add support for using last path component in type transition rules
Date: Tue, 29 Mar 2011 10:53:40 -0400	[thread overview]
Message-ID: <4D91F274.1000106@tresys.com> (raw)
In-Reply-To: <4D91EBAA.9020008@redhat.com>

On 03/29/11 10:24, Daniel J Walsh wrote:
> Any idea on how you what you would like to call these interfaces?
> 
> files_etc_named_filetrans', `
> 	gen_require(`
>      		type etc_t;
> 	')
> 
> 	type_transition $1 etc_t:file $2 $3;
> ')
> 
> interface(`sysnet_etc_filetrans_resolve_conf',`
> 	gen_require(`
> 		type net_conf_t;
> 	')
> 
> 	files_etc_named_filetrans($1, net_conf_t, resolv.conf)
> ')
> 
> sysnet_etc_filetrans_resolv_conf(unconfined_t)

I have two thoughts:

name_filetrans_pattern() and files_etc_name_filetrans()

or

nametrans_pattern() and files_etc_nametrans()


I like the second option because its shorter, but the first option is
probably the best choice as its more precise.  It also is future-proof,
in case the named type_transition statement is extended to some other
objects (e.g. KaiGai already feels it will be useful for databases).


> -------- Original Message --------
> Subject: [PATCH] checkpolicy: add support for using last path component
> in type transition rules
> Date: Mon, 28 Mar 2011 14:00:19 -0400
> From: Eric Paris <eparis@redhat.com>
> To: selinux at tycho.nsa.gov
> CC: method at manicmethod.com, sds at tycho.nsa.gov
> 
> This patch adds support for using the last path component as part of the
> information in making labeling decisions for new objects.  A example
> rule looks like so:
> 
> type_transition unconfined_t etc_t:file system_conf_t eric;
> 
> This rule says if unconfined_t creates a file in a directory labeled
> etc_t and the last path component is "eric" (no globbing, no matching
> magic, just exact strcmp) it should be labeled system_conf_t.
> 
> The kernel and policy representation does not have support for such
> rules in conditionals, and thus policy explicitly notes that fact if
> such a rule is added to a conditional.
> 
> Signed-off-by: Eric Paris <eparis@redhat.com>
> ---
[patch cut]

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

  reply	other threads:[~2011-03-29 14:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 14:24 [refpolicy] Fwd: [PATCH] checkpolicy: add support for using last path component in type transition rules Daniel J Walsh
2011-03-29 14:53 ` Christopher J. PeBenito [this message]
2011-03-29 20:25   ` Daniel J Walsh
2011-04-07 13:48     ` 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=4D91F274.1000106@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.