From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Zack Weinberg" <zack@owlfolio.org>,
"Cristian Rodríguez" <cristian@rodriguez.im>,
"Florian Weimer" <fweimer@redhat.com>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
GNU libc development <libc-alpha@sourceware.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: [PATCH 2/2] Add single-threaded fast path to rand()
Date: Fri, 22 Mar 2024 11:46:18 -0300 [thread overview]
Message-ID: <17ac36a5-d5c0-4f71-8cf3-5eaf014194d6@linaro.org> (raw)
In-Reply-To: <f6582f73-e7fc-4d8b-87ac-fd232dd2930c@app.fastmail.com>
On 22/03/24 11:27, Zack Weinberg wrote:
> On Thu, Mar 21, 2024, at 11:53 AM, Adhemerval Zanella Netto wrote:
>> And even if arc4random is explicit a non CPRNG, there were some worries that
>> users might misuse the interface and thus add some security issues.
>
> No opinion about anything else in this thread, but if we add arc4random at all
> it MUST be a CSPRNG. That's a documented guarantee on all the systems that
> do have it, and applications rely on it.
Yeah, this is another point of contention where one might consider that a
userland CPRNG that has no feedback from kernel to where/how to properly
reseed might not be considered a CPRNG.
next prev parent reply other threads:[~2024-03-22 14:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 15:20 [PATCH 2/2] Add single-threaded fast path to rand() Wilco Dijkstra
2024-03-18 19:24 ` Cristian Rodríguez
2024-03-19 15:44 ` Wilco Dijkstra
2024-03-20 12:31 ` Adhemerval Zanella Netto
2024-03-20 14:18 ` Cristian Rodríguez
2024-03-20 14:27 ` Adhemerval Zanella Netto
2024-03-21 7:39 ` Florian Weimer
2024-03-21 13:33 ` Cristian Rodríguez
2024-03-21 14:35 ` Mathieu Desnoyers
2024-03-21 15:07 ` Szabolcs Nagy
2024-03-21 15:18 ` Wilco Dijkstra
2024-03-21 15:53 ` Adhemerval Zanella Netto
2024-03-22 14:27 ` Zack Weinberg
2024-03-22 14:46 ` Adhemerval Zanella Netto [this message]
2024-03-22 15:30 ` Zack Weinberg
2024-03-22 18:05 ` Adhemerval Zanella Netto
2024-03-22 19:47 ` Mathieu Desnoyers
2024-03-22 22:54 ` Cristian Rodríguez
2024-03-23 14:01 ` Zack Weinberg
2024-03-23 15:23 ` Mathieu Desnoyers
2024-03-25 14:09 ` Mathieu Desnoyers
2024-03-25 17:52 ` Adhemerval Zanella Netto
2024-03-24 0:59 ` Cristian Rodríguez
2024-03-25 6:44 ` Florian Weimer
2024-03-20 14:28 ` Wilco Dijkstra
2024-03-20 14:40 ` Xi Ruoyao
-- strict thread matches above, loose matches on Subject: below --
2023-11-28 17:37 Wilco Dijkstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17ac36a5-d5c0-4f71-8cf3-5eaf014194d6@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Jason@zx2c4.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=cristian@rodriguez.im \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=zack@owlfolio.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).