public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Nick Clifton <nickc@redhat.com>, Binutils <binutils@sourceware.org>
Subject: Re: binutils as policy checker (was: RFC: Add a linker warning when creating segments with RWX permissions)
Date: Tue, 3 May 2022 22:29:51 +0200	[thread overview]
Message-ID: <cb671042-b801-bb7e-10ad-f355f65bd6e8@ubuntu.com> (raw)
In-Reply-To: <CAMe9rOq4RA+n8fXDAZJsO-09sj+bAfwQ=n=yeRokk6Lv6B5UyQ@mail.gmail.com>

On 03.05.22 21:57, H.J. Lu wrote:
> On Tue, May 3, 2022 at 12:35 PM Matthias Klose <doko@ubuntu.com> wrote:
>>
>> On 28.04.22 11:46, Nick Clifton via Binutils wrote:
>>> Hi Guys,
>>>
>>>     OK, attached is v2 of my proposed patch.  The main features of this
>>>     new version are:
>>>
>>>       * There are now configure options which can turn off the generation
>>>         of linker warnings about the creation of executable segments and
>>>         the creation of executable stacks.  By default however not using
>>>         these configure options will result in the creation of a linker
>>>         with all of the warnings enabled.
>>>
>>>       * There is new linker command line option: --no-warn-rwx-segments
>>>         which disables the warnings about executable segments.
>>>
>>>       * There are tests for the new features, plus extra regexps in the
>>>         testsuite's pruning proc to remove the warnings from the linker's
>>>         output for normal tests.
>>>
>>>       * The creation of a TLS segment with eXecute permission will trigger
>>>         a warning, regardless of whether it has the read and/or write
>>>         permissions set.
>>>
>>>       * There is a new configure time option which will disable the
>>>         creation of an executable stack simply because an input file is
>>>         missing a .note-GNU-stack section (for those architectures where
>>>         such a creation is the normal behaviour).  This option is not
>>>         enabled by default however.  At least not yet.
>>>
>>>     I think that this represents the best compromise between helping to
>>>     promote secure builds whilst also allowing toolchain creators and
>>>     program builders the option to disable the features if they wish.
>>>
>>>     Any comments ?
>>
>> this commit contains a ld/aclocal.m4 generated with automake 1.16.  Please
>> re-create that file with automake 1.15.1. And maybe re-create the Makefile.in
>> also with the correct automake version.
>>
>> Thanks, Matthias
> 
> I am checking in this.

thanks, I see that zlib also processed with automake 1.16..2

Matthias

  reply	other threads:[~2022-05-03 20:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 11:31 RFC: Add a linker warning when creating segments with RWX permissions Nick Clifton
2022-04-26 13:56 ` Jan Beulich
2022-04-26 16:39   ` Nick Clifton
2022-04-26 15:06 ` binutils as policy checker (was: RFC: Add a linker warning when creating segments with RWX permissions) Michael Matz
2022-04-26 15:20   ` Joel Sherrill
2022-04-28  9:46     ` Nick Clifton
2022-04-29  6:29       ` Sam James
2022-05-03 14:54       ` Michael Matz
2022-05-03 19:35       ` Matthias Klose
2022-05-03 19:57         ` H.J. Lu
2022-05-03 20:29           ` Matthias Klose [this message]
2022-04-26 16:47   ` Nick Clifton

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=cb671042-b801-bb7e-10ad-f355f65bd6e8@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).