grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan McCune <jonmccune@google.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Deterministic grub-mkimage
Date: Mon, 29 Dec 2014 11:01:20 -0800	[thread overview]
Message-ID: <CADtfRCU2R7aG7zs3iH6g=znDEHKK860XN_E6tVRH-_0JBw-_wg@mail.gmail.com> (raw)
In-Reply-To: <CAAXZBWJTjoh7iQD-7AgNAxSMxLbzeMhposW9A5Dup2nZKy1nQw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]

On Mon, Dec 29, 2014 at 3:08 AM, Andrew Clausen <andrew.p.clausen@gmail.com>
wrote:

> Hi Jonathan,
>
> On 29 December 2014 at 06:29, Jonathan McCune <jonmccune@google.com>
> wrote:
> >> One solution would be to:
> >>  * build deterministically by default by using a constant timestamp, and
> >
> > I think doing this by default would be a poor choice, as most of the time
> > during development it is very useful to easily identify which version /
> > build / experiment / etc is in use.
>
> I agree that during development, timestamps might be useful.  Although
> I've never found them particularly helpful myself -- they aren't as
> easy as, say, having a text file sitting in the same directory saying
> which git commit it is.  In fact, including the git commit somewhere
> in the binary would be both more helpful and deterministic.  (I am
> happy to supply a patch for this.)  Have you ever used time stamps?
>
> >>  * add a --with-timestamps option (disabled by default), which would
> >> enable honest timestamps.
> >>
> >> What do you think?  Are you accepting patches?
> >
> > The availability of a flag to explicitly set a specific timestamp for the
> > purpose of reproducing a build, seems sane to me. I don't think I would
> > enable it by default.
>
> Sorry to be stubborn on this point, but I think it's quite important.
> If most people are using deterministic builds, then it becomes much
> easier for people to audit against each other's computers.  At the
> moment, when I do audits with Grub, I have to ask my
> colleagues/friends to zero out the timestamp.  It makes the
> conversation longer, which makes me feel reluctant to inconvenience
> them.  So I end up doing a less thorough audit.  This kind of audit
> scenario arises frequently (or at least, it ought to) in work with
> NGOs, journalists, law firms, etc.
>
> Bottom line: I think there is an important social benefit to dropping
> timestamps by default.  I'm not convinced timestamps are used much by
> developers, and there are better alternatives such as git-commits.
>

No objection from me, though I'm not a maintainer.

-Jon

[-- Attachment #2: Type: text/html, Size: 2781 bytes --]

  reply	other threads:[~2014-12-29 19:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-28 11:24 Deterministic grub-mkimage Andrew Clausen
2014-12-29  6:29 ` Jonathan McCune
2014-12-29 11:08   ` Andrew Clausen
2014-12-29 19:01     ` Jonathan McCune [this message]
2015-01-22 20:08     ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-03-22 19:33       ` [PATCH] use stock embedded timestamp 2015-01-01T0000+0000 Daniel Kahn Gillmor
2015-03-27 12:27         ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-03-28 16:04           ` Daniel Kahn Gillmor

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='CADtfRCU2R7aG7zs3iH6g=znDEHKK860XN_E6tVRH-_0JBw-_wg@mail.gmail.com' \
    --to=jonmccune@google.com \
    --cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).