From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 06/15] Add firefox file contexts for binary installations
Date: Thu, 10 Mar 2011 16:25:50 +0100 [thread overview]
Message-ID: <1299770750.2990.2.camel@tesla.lan> (raw)
In-Reply-To: <20110310133705.GB12988@siphos.be>
On Thu, 10/03/2011 at 14.37 +0100, Sven Vermeulen wrote:
> On Thu, Mar 10, 2011 at 01:02:03PM +0100, Guido Trentalancia wrote:
> > Plain F14 policy has text relocations for libxul.so but does that
> > privately. Text relocations are bad if they can be avoided and usually
> > that is the case. Now we have at least two confirmed cases that this is
> > possible (me and you)...
>
> I believe that the textrel_shlib_t is needed if you use the 32-bit binary
> distribution as offered by Mozilla (for firefox), not if it is built from
> source.
Perhaps someone could drop a note to mozilla.org ? When I build it, I
don't even need to pass the -fPIC flag and it does not require text
relocations...
> I'll build a firefox here and give feedback.
>
> In any case, you're correct in that textrel_shlib_t contexts should be
> considered in the libraries.fc one instead. But I'll first see if I can
> confirm if it is always necessary or only in particular situations.
>
> Wkr,
> Sven Vermeulen
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
>
next prev parent reply other threads:[~2011-03-10 15:25 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
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 [this message]
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=1299770750.2990.2.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.