mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
To: musl@lists.openwall.com
Subject: Re: noexecstack
Date: Mon, 6 Aug 2012 09:16:10 +0200	[thread overview]
Message-ID: <CAPLrYERO+Jc31kNAxt5h82U4nMWdxoYsqN414u383raxz1RamQ@mail.gmail.com> (raw)
In-Reply-To: <20120806144521.565b32cc@sibserver.ru>

2012/8/6 orc <orc@sibserver.ru>:
> On Sun, 5 Aug 2012 23:35:36 +0200

> Correct me if I'm wrong, but this is ugly stuff.
>
> - binutils ld has -z noexecstack command line option.
> - this (GNU_STACK) is binutils-specific (tinycc, for example, does not
>   generate ELFs with that section, and future direction should be on
>   that plain ELFs without any gnuish extensions IMO)
> - Kernel sets executable stack by default, kernel can be patched not to
>   do that (that's one line patch per architecture)

Can you give some example of how to do it? It might be worthwhile to
introduce it into the main repository of Linux. What do you think?

> - binutils can be patched to not produce ELFs with executable stack by
>   default
>
> While some of options I listed here may harm some GCC or binutils
> internals (I don't know), I see an utility that comes with grsecurity
> patches (paxctl) that operates that section (GNU_STACK), converting it
> into it's own.
> I tested a system with patched binutils and kernel (but binutils patch
> here will be enough) without any problems.

It would be very nice if we could solve this problem in this way. I'm
currently using this patch, but this is not the best solution in my
opinion. Ideally if the system (kernel, binutils, libc) enforce
noexecstack by default... definitely worth look closer at this issue.

Thanks,
Daniel


  reply	other threads:[~2012-08-06  7:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05 21:35 noexecstack Daniel Cegiełka
2012-08-05 21:41 ` noexecstack Anthony G. Basile
2012-08-05 21:46 ` noexecstack Rich Felker
2012-08-05 22:01   ` noexecstack Nathan McSween
2012-08-05 22:45     ` noexecstack Rich Felker
2012-08-06  6:43   ` noexecstack Szabolcs Nagy
2012-08-06  9:37     ` noexecstack Rich Felker
2012-08-06 11:19       ` noexecstack Szabolcs Nagy
2012-08-06 11:32         ` noexecstack Rich Felker
2012-08-06 21:11           ` noexecstack Kant
2012-10-03 15:54             ` noexecstack Rich Felker
2012-08-06  6:45 ` noexecstack orc
2012-08-06  7:16   ` Daniel Cegiełka [this message]
2012-08-06  7:55     ` noexecstack Justin Cormack
2012-08-06  8:05     ` noexecstack orc
2012-08-06  8:46       ` noexecstack Daniel Cegiełka
2012-08-06  9:11         ` noexecstack orc
2012-08-06  9:15           ` noexecstack orc
2012-08-07 11:57   ` noexecstack Vasily Kulikov

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=CAPLrYERO+Jc31kNAxt5h82U4nMWdxoYsqN414u383raxz1RamQ@mail.gmail.com \
    --to=daniel.cegielka@gmail.com \
    --cc=musl@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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).