linux-kernel - Re: [PATCH tip v8] x86/setup: Use rng seeds from setup

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 10 Jul 2022 13:11:16 +0200
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     "H. Peter Anvin" <hpa@...or.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, X86 ML <x86@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH tip v8] x86/setup: Use rng seeds from setup_data

On 7/10/22, Borislav Petkov <bp@...en8.de> wrote:
> On Sat, Jul 09, 2022 at 03:41:19PM -0700, H. Peter Anvin wrote:
>> In ABI/API terms, that symbol has the semantic of connecting the API
>> version
>> to the underlying ABI version; a piece of code that sees an enumeration
>> type
>> > SETUP_ENUM_MAX must by definition treat it as an opaque blob. In the
>> future, should it become warranted, we may add flags that indicate how
>> unaware code should handle them, but I don't think we can engineer that
>> right now.
>
> Ok, let's hope it doesn't come to that and userspace behaves... <eyeroll>
>
> So, I'm going to send the below to Linus now so that 5.19 releases fixed
> and then queue Jason's patch next week.

Do you want me to rebase mine on top of the 5.19 fixup? Or is that
trivial enough that you'll just do it when applying?

Jason