From: md@Linux.IT (Marco d'Itri)
To: Lucas De Marchi <lucas.de.marchi@gmail.com>, 820010@bugs.debian.org
Cc: Ben Hutchings <ben@decadent.org.uk>,
linux-modules <linux-modules@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: Bug#820010: [PATCH v2] libkmod: Add support for detached module signatures
Date: Sat, 21 May 2016 20:40:04 +0200 [thread overview]
Message-ID: <20160521184004.GA32133@bongo.bofh.it> (raw)
In-Reply-To: <CAKi4VAKQecNsdVUXV0dR8_0GTKBirZq8NR7b32xMY+ar3Dn4Uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
On May 21, Lucas De Marchi <lucas.de.marchi@gmail.com> wrote:
> And how is this signature prepared? Since it needs the compiled
> module it would be a matter of changing the compiler, even minor
> version, to invalidate the argument of reproducible build. It seems
> very fragile to me.
But this is the whole point of reproducible builds: knowing that if you
start from the same sources and build enviroment, and distributions do,
then you will get the same results.
Building gcc is reproducibile as well...
Reproducibility with a different compiler has never been a goal.
--
ciao,
Marco
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 648 bytes --]
next prev parent reply other threads:[~2016-05-21 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 0:16 [PATCH] libkmod: Add support for detached module signatures Ben Hutchings
2016-04-05 0:32 ` [PATCH v2] " Ben Hutchings
2016-04-13 4:05 ` Lucas De Marchi
2016-04-13 10:00 ` Ben Hutchings
2016-05-17 12:51 ` Ben Hutchings
2016-05-21 18:31 ` Lucas De Marchi
2016-05-21 18:40 ` Marco d'Itri [this message]
2016-05-21 19:01 ` Ben Hutchings
2016-05-29 12:48 ` Ben Hutchings
2016-06-04 14:13 ` Lucas De Marchi
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=20160521184004.GA32133@bongo.bofh.it \
--to=md@linux.it \
--cc=820010@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=rusty@rustcorp.com.au \
/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.