All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	"Bernhard M.Wiedemann" <bwiedemann@suse.de>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH] x86/efi: Do not insert timestamps in efi files
Date: Thu, 25 Oct 2018 15:00:56 +0100	[thread overview]
Message-ID: <d9db83e2-3f03-78ff-b92c-85ca680b7924@citrix.com> (raw)
In-Reply-To: <5BD1B8AA02000078001F4A44@prv1-mh.provo.novell.com>

On 25/10/18 13:35, Jan Beulich wrote:
>>>> On 24.10.18 at 15:45, <bwiedemann@suse.de> wrote:
>> in order to make builds reproducible.
>> See https://reproducible-builds.org/ for why this is good.
> But is this something everyone wants, unconditionally? I'm
> generally happy to have this basic indication of when a certain
> image was built; I regret that ELF images have no such
> indication.

What practical purpose does having a time stamp serve?  If you really
need to see, what is wrong with the mtime in your build tree?

For shipped binaries to customers, exactly when it was built is
irrelevant, whereas peoples ability to independently verify the
integrity of the binary is important.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-10-25 14:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  8:03 [PATCH] x86/efi: Do not insert timestamps in efi files Bernhard M. Wiedemann
2018-10-24  8:16 ` Andrew Cooper
2018-10-24 12:49   ` Bernhard M. Wiedemann
2018-10-24 13:04     ` Wei Liu
2018-10-24 13:45     ` Bernhard M. Wiedemann
2018-10-25  8:02       ` Wei Liu
     [not found]       ` <108D0A7C020000E4CA4B4E14@prv1-mh.provo.novell.com>
     [not found]         ` <74F2501302000079CA4B4E14@prv1-mh.provo.novell.com>
2018-10-25 12:35           ` Jan Beulich
2018-10-25 14:00             ` Andrew Cooper [this message]
2018-10-25 14:08               ` Jan Beulich
2018-10-26 11:11                 ` Bernhard M. Wiedemann

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=d9db83e2-3f03-78ff-b92c-85ca680b7924@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=bwiedemann@suse.de \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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 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.