All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 06/15] Add firefox file contexts for binary installations
Date: Wed, 09 Mar 2011 23:39:38 +0100	[thread overview]
Message-ID: <1299710378.2974.26.camel@tesla.lan> (raw)
In-Reply-To: <20110309211238.GA4704@siphos.be>

On Wed, 09/03/2011 at 22.12 +0100, Sven Vermeulen wrote:
> Binary installations of firefox provide binaries in /opt/firefox by default. 
> 
> Also, binary can be in /usr/bin (but most often this is a script that calls
> the binary in /opt/firefox). In both cases, this needs to be marked as
> mozilla_exec_t too.
> 
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  policy/modules/apps/mozilla.fc |   10 ++++++++++
>  1 files changed, 10 insertions(+), 0 deletions(-)
> 
> diff --git a/policy/modules/apps/mozilla.fc b/policy/modules/apps/mozilla.fc
> index 93ac529..ad59444 100644
> --- a/policy/modules/apps/mozilla.fc
> +++ b/policy/modules/apps/mozilla.fc
> @@ -7,6 +7,7 @@ HOME_DIR/\.phoenix(/.*)?		gen_context(system_u:object_r:mozilla_home_t,s0)
>  #
>  # /bin
>  #
> +/usr/bin/firefox(-bin)?		--	gen_context(system_u:object_r:mozilla_exec_t,s0)

I think the -bin would hardly get anywhere outside of the firefox
directory (independently of where that is) unless one works very hard
towards that.

>  /usr/bin/netscape		--	gen_context(system_u:object_r:mozilla_exec_t,s0)
>  /usr/bin/mozilla		--	gen_context(system_u:object_r:mozilla_exec_t,s0)
>  /usr/bin/mozilla-snapshot	--	gen_context(system_u:object_r:mozilla_exec_t,s0)
> @@ -27,3 +28,12 @@ HOME_DIR/\.phoenix(/.*)?		gen_context(system_u:object_r:mozilla_home_t,s0)
>  /usr/lib(64)?/[^/]*firefox[^/]*/firefox-bin -- gen_context(system_u:object_r:mozilla_exec_t,s0)
>  /usr/lib/[^/]*firefox[^/]*/firefox --	gen_context(system_u:object_r:mozilla_exec_t,s0)
>  /usr/lib64/[^/]*firefox[^/]*/firefox -- gen_context(system_u:object_r:mozilla_exec_t,s0)
> +
> +#
> +# /opt
> +#
> +/opt/firefox/libxul\.so		--	gen_context(system_u:object_r:textrel_shlib_t,s0)
> +/opt/firefox/firefox		--	gen_context(system_u:object_r:mozilla_exec_t,s0)
> +/opt/firefox/run-mozilla\.sh	--	gen_context(system_u:object_r:mozilla_exec_t,s0)
> +/opt/firefox/firefox-bin	--	gen_context(system_u:object_r:mozilla_exec_t,s0)
> +/opt/firefox/plugin-container	--	gen_context(system_u:object_r:mozilla_exec_t,s0)

The idea sounds desirable to me ! But apart from the second and the
fourth elements, I had anything else labelled generically bin_t and
lib_t and I wasn't experiencing problems...

Text relocations aren't that good (libxul.so) as far as I know. Is it
not possible to get rid of them ? I think I could avoid that on a test
system.

Regards,

Guido

  reply	other threads:[~2011-03-09 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 21:12 [refpolicy] [PATCH 06/15] Add firefox file contexts for binary installations Sven Vermeulen
2011-03-09 22:39 ` Guido Trentalancia [this message]
2011-03-10  8:27   ` Dominick Grift
2011-03-10 12:02     ` Guido Trentalancia
2011-03-10 13:37       ` Sven Vermeulen
2011-03-10 14:10         ` Sven Vermeulen
2011-03-10 14:34           ` Guido Trentalancia
2011-03-10 15:25         ` Guido Trentalancia
2011-03-23 13:08 ` 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=1299710378.2974.26.camel@tesla.lan \
    --to=guido@trentalancia.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.