public inbox for kernel-hardening@lists.openwall.com
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] overview of PaX features
Date: Sat, 02 Jul 2011 21:06:20 -0400	[thread overview]
Message-ID: <4E0FC08C.8050600@gentoo.org> (raw)
In-Reply-To: <20110629194339.GA15379@openwall.com>

On 06/29/2011 03:43 PM, Solar Designer wrote:
> Vasiliy,
> 
> On Wed, Jun 29, 2011 at 10:37:28PM +0400, Vasiliy Kulikov wrote:
>> That's not only about old apps, but also a default relaxed policy for
>> the toolchain:
>>
>> http://www.gentoo.org/proj/en/hardened/gnu-stack.xml
> 
> Of course.  In my experience, most programs that currently get
> executable stack actually don't need it.
> 

Ditto.  When we couldn't fix the source code, we used to use execstack
from the prelink package to remove the X flag from PT_GNU_STACK phdrs.
Recently I wrote fix-gnustack.c to avoid all the extra prelink stuff [1]
and we're using that now.

Ref.

   [1] http://git.overlays.gentoo.org/gitweb/?p=proj/elfix.git;a=summary

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 8040 5A4D 8709 21B1 1A88  33CE 979C AF40 D045 5535
GnuPG ID  : D0455535

      parent reply	other threads:[~2011-07-03  1:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-26 18:33 [kernel-hardening] overview of PaX features Vasiliy Kulikov
2011-06-29 18:25 ` Solar Designer
2011-06-29 18:37   ` Vasiliy Kulikov
2011-06-29 19:43     ` Solar Designer
2011-06-30 16:03       ` Vasiliy Kulikov
2011-07-02 17:21         ` Solar Designer
2011-07-02 17:46           ` Vasiliy Kulikov
2011-07-03  1:06       ` Anthony G. Basile [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=4E0FC08C.8050600@gentoo.org \
    --to=blueness@gentoo.org \
    --cc=kernel-hardening@lists.openwall.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox