public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to determine if the noexec stack is defined by an application
Date: Sat, 30 Jun 2007 00:15:19 +0200	[thread overview]
Message-ID: <jefy4aflvs.fsf@sykes.suse.de> (raw)
In-Reply-To: <1183153758.2894.1.camel@laptopd505.fenrus.org> (Arjan van de Ven's message of "Fri\, 29 Jun 2007 14\:49\:18 -0700")

Arjan van de Ven <arjan@infradead.org> writes:

> like this:
>
> $ eu-readelf -l /bin/true  | grep STACK
>   GNU_STACK      0x000000 0x00000000 0x00000000 0x000000 0x000000 RW 0x4
>
>
> (replace /bin/true with the binary or library you want to check)
>
> if it says "RW" like here, it'll have non-executable stack. If it says
> "RWX" or if this line is absent entirely, the stack will be executable.

The last part is not true.  Some architectures (especially newer ones)
default to non-exec stack.  The absense of a GNU_STACK header represents
the default.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2007-06-29 22:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 20:44 how to determine if the noexec stack is defined by an application Florin Andrei
2007-06-29 21:49 ` Arjan van de Ven
2007-06-29 22:15   ` Andreas Schwab [this message]
2007-06-29 22:27     ` Arjan van de Ven
2007-06-29 22:41       ` Andreas Schwab
2007-06-29 22:43         ` Arjan van de Ven
2007-06-30  1:21   ` Florin Andrei
2007-06-30  5:16     ` Arjan van de Ven

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=jefy4aflvs.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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