[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151109211341.GA29829@srcf.ucam.org>
Date: Mon, 9 Nov 2015 21:13:41 +0000
From: Matthew Garrett <mjg59@...f.ucam.org>
To: kernel-hardening@...ts.openwall.com
Cc: Theodore Tso <tytso@...gle.com>, Emese Revfy <re.emese@...il.com>,
Kees Cook <keescook@...omium.org>, PaX Team <pageexec@...email.hu>,
Brad Spengler <spender@...ecurity.net>,
Greg KH <gregkh@...uxfoundation.org>,
Josh Triplett <josh@...htriplett.org>
Subject: Re: Re: Proposal for kernel self protection
features
On Mon, Nov 09, 2015 at 09:09:22PM +0000, Jason Cooper wrote:
> Well, That's why I referred to reading from /boot or from a flash
> partition. Existing bootloaders in the field already have that
> capability. That's how they load the kernel.
This doesn't really handle cases like network booting. Most SoCs have
some kind of RNG, recent x86 has hardware RNG, older x86 frequently has
an RNG in a TPM. Pulling an entropy seed from the filesystem is a
reasonable fallback, but we should definitely be thinking of it as a
fallback - someone with physical access to your system while it's turned
off may be able to infer the ASLR state for your next boot, for
instance.
--
Matthew Garrett | mjg59@...f.ucam.org
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.
