public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Build Linux kernel to have comparable zImages
Date: Thu, 9 Feb 2017 09:46:13 +0100	[thread overview]
Message-ID: <20170209094613.62f602ca@jawa> (raw)
In-Reply-To: <0e866eb6-8080-1c2b-9759-b02b2bd84ed9@au1.ibm.com>

On Thu, 9 Feb 2017 11:25:15 +1100
Andrew Donnellan <andrew.donnellan@au1.ibm.com> wrote:

> On 08/02/17 20:20, Lukasz Majewski wrote:
> > Dear All,
> >
> > Maybe somebody can point me to solution to the following problem:
> >
> > Problem:
> >
> > I do want to be able to compare (with e.g. md5sum, sha1) two linux
> > zImages. The problem is that Linux compiles in current build time
> > into the binary. Hence, even two identical builds will have
> > different hash.
> >
> > Why:
> >
> > I do want to do some considerable Kconfig rework and avoid situation
> > where some option would be left not enabled.
> 
> You might want to look at 
> https://github.com/hardenedlinux/grsecurity-reproducible-build, I'm
> not familiar with it at all but it seems to be somewhat in the
> direction you're after.

Thanks for pointing this out :-).

> 


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de

      reply	other threads:[~2017-02-09  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08  9:20 Build Linux kernel to have comparable zImages Lukasz Majewski
2017-02-09  0:25 ` Andrew Donnellan
2017-02-09  8:46   ` Lukasz Majewski [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=20170209094613.62f602ca@jawa \
    --to=lukma@denx.de \
    --cc=andrew.donnellan@au1.ibm.com \
    --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