From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/2] annobin: New package
Date: Wed, 6 Feb 2019 16:40:27 +0100 [thread overview]
Message-ID: <20190206164027.502ae567@windsurf> (raw)
In-Reply-To: <62ae845de2ae3fe09dbdb9c0cc00cddd92e86362.camel@spectralink.com>
Hello,
On Wed, 6 Feb 2019 15:27:52 +0000
"S?rensen, Stefan" <Stefan.Sorensen@spectralink.com> wrote:
> On Wed, 2019-02-06 at 16:04 +0100, Thomas Petazzoni wrote:
>
> > This one is already in Buildroot, and is a lot easier to integrate
> > than a gcc plugin. So unless you see an issue with checksec that is
> > solved by annobin, we'll probably stick to using checksec.
>
> The issue with checksec is that is only checks if *some* of the code in
> the binary is compiled with the correct security options - it does not
> detect that the correct options has not been used for compiling all of
> the code.
Ah, OK.
> Unfortunately I do not have any time right now to spend on this, but I
> hope that I will be able to update this to a more recent annobin relase
> soon.
Yes, please send a new series when you have some time then.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-06 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 14:31 [Buildroot] [RFC PATCH 0/2] Verify hardened builds Stefan Sørensen
2018-05-03 14:31 ` [Buildroot] [RFC PATCH 1/2] annobin: New package Stefan Sørensen
2018-05-03 22:13 ` Arnout Vandecappelle
2018-05-04 8:32 ` Sørensen, Stefan
2018-05-04 10:35 ` Arnout Vandecappelle
2019-02-06 15:04 ` Thomas Petazzoni
2019-02-06 15:27 ` Sørensen, Stefan
2019-02-06 15:40 ` Thomas Petazzoni [this message]
2018-05-03 14:31 ` [Buildroot] [RFC PATCH 2/2] core: Verify that hardening flags are used Stefan Sørensen
2018-05-03 22:42 ` Arnout Vandecappelle
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=20190206164027.502ae567@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.