Date: Wed, 31 Aug 2016 17:41:40 -0400 From: Ed Maste <emaste@freebsd.org> To: freebsd-security@freebsd.org Subject: Re: Unexplained update to /boot/boot1.efi and 2 others by freebsd-update Message-ID: <CAPyFy2DrzZcEF9yc5TA0Bt=eE7sOhq6apagRfZpXezy1ANBoFQ@mail.gmail.com> In-Reply-To: <20160823002821.GJ1069@FreeBSD.org> References: <201608221415.u7MEFl8d009158@higson.cam.lispworks.com> <20160823002821.GJ1069@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22 August 2016 at 20:28, Gleb Smirnoff <glebius@freebsd.org> wrote: > > The freebsd-update build code attempts to extract and ignore timestamps in order > to determine whether files are 'really' changing between builds; unfortunately these > particular files contain a build artifact which the freebsd-update code was not > able to handle, thus resulting in them being incorrectly identified as needing to be > distributed. The issue with PE/COFF timestamps in the UEFI bootloader components is fixed as of SVN r305160 in HEAD and will make it back to stable/11 in due course. The timestamps will now be set to a consistent, known value.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2DrzZcEF9yc5TA0Bt=eE7sOhq6apagRfZpXezy1ANBoFQ>