Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 May 2017 08:47:17 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Daniel Gruss <daniel.gruss@...k.tugraz.at>
Cc: kernel list <linux-kernel@...r.kernel.org>,
	kernel-hardening@...ts.openwall.com,
	"clementine.maurice@...k.tugraz.at" <clementine.maurice@...k.tugraz.at>,
	"moritz.lipp@...k.tugraz.at" <moritz.lipp@...k.tugraz.at>,
	Michael Schwarz <michael.schwarz@...k.tugraz.at>,
	Richard Fellner <richard.fellner@...dent.tugraz.at>,
	kirill.shutemov@...ux.intel.com, Ingo Molnar <mingo@...nel.org>,
	"anders.fogh@...ta-adan.de" <anders.fogh@...ta-adan.de>
Subject: Re: [RFC, PATCH] x86_64: KAISER - do not map kernel in user mode

On Thu, May 04, 2017 at 12:02:47PM +0200, Daniel Gruss wrote:
> After several recent works [1,2,3] KASLR on x86_64 was basically considered
> dead by many researchers. We have been working on an efficient but effective
> fix for this problem and found that not mapping the kernel space when
> running in user mode is the solution to this problem [4] (the corresponding
> paper [5] will be presented at ESSoS17).

I'll try to read the paper.  In the meantime: how different is your
approach from then one here?

	https://lwn.net/Articles/39283/

and how different is the performance impact?

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.