| 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
| ||
|
Date: Sat, 23 Jul 2022 15:04:36 -0400
From: Cristian RodrÃguez <crrodriguez@...nsuse.org>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: libc-alpha@...rceware.org, linux-crypto@...r.kernel.org,
Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>,
Florian Weimer <fweimer@...hat.com>,
Yann Droneaud <ydroneaud@...eya.com>, jann@...jh.net,
Michael@...ronix.com
Subject: Re: arc4random - are you sure we want these?
On Sat, Jul 23, 2022 at 12:25 PM Jason A. Donenfeld via Libc-alpha
<libc-alpha@...rceware.org> wrote:
> For that reason, past discussion of having some random number generation
> in userspace libcs has geared toward doing this in the vDSO, somehow,
> where the kernel can be part and parcel of that effort.
On linux just making this interface call "something" from the VDSO that
- does not block.
- cannot ever fail or if it does indeed need to bail out it kills the
calling thread as last resort.
(if neither of those can be provided, we are back to square one)
Will be beyond awesome because it could be usable everywhere,
including the dynamic linker, malloc or whatever else
question is..is there any at least experimental patch with a hope of
beign accepted available ?
Powered by blists - more mailing lists