linux-kernel - Re: [RFC PATCH 0/2] Propagating reseed notifications to user space

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:   Mon, 4 Sep 2023 16:54:21 +0200
From:   Babis Chalios <bchalios@...zon.es>
To:     "Jason A. Donenfeld" <Jason@...c4.com>
CC:     Olivia Mackall <olivia@...enic.com>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Theodore Ts'o <tytso@....edu>,
        "Michael S. Tsirkin" <mst@...hat.com>,
        Jason Wang <jasowang@...hat.com>,
        Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
        <linux-crypto@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <virtualization@...ts.linux-foundation.org>, <graf@...zon.de>,
        <xmarcalx@...zon.co.uk>, <aams@...zon.de>, <dwmw@...zon.co.uk>,
        <gregkh@...uxfoundation.org>, <bchalios@...zon.es>
Subject: Re: [RFC PATCH 0/2] Propagating reseed notifications to user space

Hi Jason,

On 4/9/23 16:42, Jason A. Donenfeld wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
>
>
> On Mon, Sep 04, 2023 at 03:44:48PM +0200, Babis Chalios wrote:
>> Hello all,
>>
>> On 23/8/23 11:01, Babis Chalios wrote:
>>> This is an RFC, so that we can discuss whether the proposed ABI works.
>>> Also, I'd like to hear people's opinion on the internal registration
>>> API, 8/24 split etc. If we decide that this approach works, I 'm happy
>>> to add documentation for it, with examples on how user space can make
>>> use of it.
>> Some time has passed since I sent this and I haven't received any
>> comments, so I assume people
> Nope. This still stands:
> https://lore.kernel.org/all/CAHmME9pxc-nO_xa=4+1CnvbnuefbRTJHxM7n817c_TPeoxzu_g@mail.gmail.com/
Could you elaborate on why the proposed RFC is not inline with your 
plan? We need to let user space
know that it needs to reseed its PRNGs. It is not very clear to me, how 
does that interplay with having a
getrandom vDSO.

IOW, say we did have a vDSO getrandom, don't you think we should have 
such an API to notify when it
needs to discard stale state, or do you think this is not the right API?

> And honestly the constant pushing from you has in part been
> demotivating.


Cheers,
Babis