linux-kernel - Re: [PATCH 1/1] kexec: Verify the signature of signed PE bzImage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20140724150730.7827985aa003a236e2140a6b@linux-foundation.org>
Date:	Thu, 24 Jul 2014 15:07:30 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	ebiederm@...ssion.com, hpa@...or.com, mjg59@...f.ucam.org,
	bp@...en8.de, dhowells@...hat.com, linux-kernel@...r.kernel.org,
	kexec@...ts.infradead.org
Subject: Re: [PATCH 1/1] kexec: Verify the signature of signed PE bzImage

On Thu, 24 Jul 2014 10:16:42 -0400 Vivek Goyal <vgoyal@...hat.com> wrote:

> I am wondering how this final kexec patch should be routed. Issue here is that
> this patch depends on David Howells's PKCS7 and PEFILE patches. Which are now
> sitting in security tree. (security/next).
> 
> http://git.kernel.org/cgit/linux/kernel/git/jmorris/linux-security.git/log/?h=next
> 
> Not sure how to handle this dependency issue.

I have all these patches staged after linux-next so it fitted
straight in.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/