From: Paul Eggleton <paul.eggleton@intel.com>
To: "Wold, Saul" <saul.wold@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: PATCH: openssl: disable execstack flag to prevent problems with SELinux
Date: Fri, 3 Dec 2010 16:09:03 +0000 [thread overview]
Message-ID: <201012031609.03784.paul.eggleton@intel.com> (raw)
In-Reply-To: <4CF7E972.6070308@intel.com>
On Thursday 02 December 2010 18:46:10 you wrote:
> On 11/19/2010 02:23 AM, Paul Eggleton wrote:
> > openssl: disable execstack flag to prevent problems with SELinux
> >
> > The execstack flag gets set on libcrypto.so by default which causes SELinux
> > to prevent it from being loaded on systems using SELinux, which includes
> > Fedora. This patch disables the execstack flag. (Note: Red Hat do this in
> > their openssl packaging.)
> >
> Should this be a native only CFLAG change?
>
> Since we are not SELinux on the target (that might be a layer someone
> else might provide).
AFAICT there's no benefit to leaving the execstack flag enabled for this library. However if we want to take the conservative approach and leave it as-is for the target that's fine. Let me know if that's the case and I will produce a new patch.
Cheers,
Paul
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
prev parent reply other threads:[~2010-12-03 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 10:23 PATCH: openssl: disable execstack flag to prevent problems with SELinux Paul Eggleton
2010-12-02 18:46 ` Saul Wold
2010-12-03 16:09 ` Paul Eggleton [this message]
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=201012031609.03784.paul.eggleton@intel.com \
--to=paul.eggleton@intel.com \
--cc=poky@yoctoproject.org \
--cc=saul.wold@intel.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.