Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKv+Gu8sT2CLquxAdneNSQ+YqasbPM96E3h9NMc0JMCR5Wa+bA@mail.gmail.com>
Date: Fri, 10 Feb 2017 14:31:31 +0000
From: Ard Biesheuvel <ard.biesheuvel@...aro.org>
To: Mark Rutland <mark.rutland@....com>
Cc: "linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>, 
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, 
	Leif Lindholm <leif.lindholm@...aro.org>, Catalin Marinas <catalin.marinas@....com>, 
	Russell King <linux@...linux.org.uk>, kernel-hardening@...ts.openwall.com, 
	Laura Abbott <labbott@...oraproject.org>
Subject: Re: [PATCH v2 05/14] arm64: efi: remove forbidden values from the
 PE/COFF header

On 10 February 2017 at 10:13, Mark Rutland <mark.rutland@....com> wrote:
> On Wed, Feb 08, 2017 at 11:55:38AM +0000, Ard Biesheuvel wrote:
>> Bring the PE/COFF header in line with the PE/COFF spec, by setting
>> NumberOfSymbols to 0, and removing the section alignment flags.
>>
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@...aro.org>
>
> I take it that in practice EFI implementations don't care about these?

Not at all. I just spotted it when I was cleaning up the header.

> Assuming so:
>
> Acked-by: Mark Rutland <mark.rutland@....com>
>
> Otherwise, we might want to fix this first, so that we can easily
> backport it.
>

I wouldn't bother

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.