[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121108194522.GC27586@redhat.com>
Date: Thu, 8 Nov 2012 14:45:22 -0500
From: Vivek Goyal <vgoyal@...hat.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Matthew Garrett <mjg@...hat.com>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Khalid Aziz <khalid@...ehiking.org>, kexec@...ts.infradead.org,
horms@...ge.net.au, Dave Young <dyoung@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
linux kernel mailing list <linux-kernel@...r.kernel.org>,
Dmitry Kasatkin <dmitry.kasatkin@...el.com>,
Roberto Sassu <roberto.sassu@...ito.it>,
Kees Cook <keescook@...omium.org>,
Peter Jones <pjones@...hat.com>
Subject: Re: Kdump with signed images
On Thu, Nov 08, 2012 at 02:40:50PM -0500, Vivek Goyal wrote:
> On Tue, Nov 06, 2012 at 03:51:59PM -0800, Eric W. Biederman wrote:
>
> [..]
>
> Thnking more about executable signature verification, I have another question.
>
> While verifyign the signature, we will have to read the whole executable
> in memory. That sounds bad as we are in kernel mode and will not be killed
> and if sombody is trying to execute a malformed exceptionally large
> executable, system will start killing other processess. We can potentially
> lock all the memory in kernel just by trying to execute a signed huge
> executable. Not good.
>
Also, even if we try to read in whole executable, can't an hacker modify
pages in swap disk and then they will be faulted back in and bingo hacker
is running its unsigned code. (assuming root has been compromised otherwise
why do we have to do all this exercise).
Thanks
Vivek
--
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/
Powered by blists - more mailing lists