[<prev] [next>] [day] [month] [year] [list]
Message-ID: <9a5b63ce-aeaa-77cf-0e36-53ee472a1656@zytor.com>
Date: Tue, 17 Jan 2023 15:50:41 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: David Keisar Schm <david.keisarschm@...l.huji.ac.il>
Cc: linux-kernel@...r.kernel.org,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, Jason@...c4.com, keescook@...omium.org,
aksecurity@...il.com, ilay.bahat1@...il.com
Subject: Re: [PATCH v4 3/3] x86 mm, x86 architecture (32-bit and 64-bit):
arch/x86/mm/kaslr.c: Adds 64bits version of prandom_seed_state
On 1/17/23 13:16, David Keisar Schm wrote:
>
> Because (the way we understand this), Kees Cook prefers to keep the
> original API, so that a fixed seed can be injected at will (for
> debugging). Seehttps://lkml.org/lkml/2023/1/6/772
> <https://lkml.org/lkml/2023/1/6/772>
>
This bothers me, because with FG-KASLR is *exactly* when a bad PRNG will
shine through.
-hpa
Powered by blists - more mailing lists