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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110527094047.GJ21386@elte.hu>
Date:	Fri, 27 May 2011 11:40:47 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Dave Jones <davej@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Dan Rosenberg <drosenberg@...curity.com>,
	Tony Luck <tony.luck@...il.com>, linux-kernel@...r.kernel.org,
	kees.cook@...onical.com, davem@...emloft.net, eranian@...gle.com,
	torvalds@...ux-foundation.org, adobriyan@...il.com,
	penberg@...nel.org, Arjan van de Ven <arjan@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Valdis.Kletnieks@...edu, pageexec@...email.hu
Subject: Re: [RFC][PATCH] Randomize kernel base address on boot


* Dave Jones <davej@...hat.com> wrote:

> On Thu, May 26, 2011 at 03:32:13PM -0700, H. Peter Anvin wrote:
>  > On 05/26/2011 03:18 PM, Rafael J. Wysocki wrote:
>  > > 
>  > > Well, as far as I can tell, this feature is going to break hibernation on
>  > > both x86_32 and x86_64 at the moment, unless you can guarantee that the
>  > > randomized kernel location will be the same for both the boot and the target
>  > > kernels.
>  > > 
>  > 
>  > Obviously we can't and we don't.  I'm a bit surprised at that
>  > constraint... how can that constraint not break things like kernels of
>  > slightly different size?
> 
> In Fedora at least, we make sure the kernel you thaw from is the 
> same one you booted by diddling with grub to force the right kernel 
> to be booted.

Btw., the hibernation code should save a signature and make sure that 
the two kernels match! It's really broken if the code allows blind 
thawing ...

Thanks,

	Ingo
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ