From: Noah Goldstein <goldstein.w.n@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: "Cristian Rodríguez" <crrodriguez@opensuse.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"GNU C Library" <libc-alpha@sourceware.org>,
"Florian Weimer" <fweimer@redhat.com>
Subject: Re: [PATCH v1 1/2] random-bits: Factor out entropy generating function
Date: Mon, 4 Apr 2022 13:23:45 -0500 [thread overview]
Message-ID: <CAFUsyf+zbXFVRV9G1GQfRP3D+VoHVrWrGDNAhJgUuR80uvYoQw@mail.gmail.com> (raw)
In-Reply-To: <939bcfbb-516e-ab97-f6bf-858c4956c38e@linaro.org>
On Mon, Apr 4, 2022 at 12:42 PM Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
>
>
>
> On 01/04/2022 15:01, Cristian Rodríguez wrote:
> > On Thu, Mar 31, 2022 at 8:05 PM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> >
> >> AFAIK our goal is entropy more so than security. For example
> >> if this is used to generate jiffies to stagger threads its not a security
> >> issue in any sense, it's just not ideal for performance.
> >
> > In any case this should be more than fast enough for the other use
> > cases of random_bits() .. maybe one new random_bits_fast() function
> > foe edge cases where even this is too slow?
>
> I think we are bike-shedding in the same issue OpenBSD guys stumbled
> and which they have solved 10 years ago [1]. Essentially, we need to
> come up with a internal PRNG interface that can be used internally and
> externally, instead of reinventing cleaver ways to use the timer as
> entropy source.
>
> The issue is not really the cypher used, ideally it could be replace if
> we find out that it does not fit. The main issue is to glue together
> all the requirements to have a concise internal interface, taking in
> consideration the glibc constrains to work with multiple kernel version
> and environments (where we can't assume we have access to a source or
> reliable entropy like getrandom syscall).
>
> My plan to rehearse Florian arc4random proposal to have some simpler
> to where we might improve upon (a simpler fork detection for kernels
> without MADV_WIPEONFORK that just issue a atfork handle, maybe using
> ChaCha20 as virtually all other systems do, no per-thread state).
Why no per-thread / per-cpu? It seems otherwise there will need to be
some explicit synchronization on the stream.
Regarding this patch, do we want to skip it and just wait on arc4random
interface in kernel/glibc or should I go forward with it and some arch
specific entropy functions in the mean-time?
>
> [1] https://www.youtube.com/watch?v=gp_90-3R0pE
next prev parent reply other threads:[~2022-04-04 18:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 22:09 Noah Goldstein
2022-03-28 22:09 ` [PATCH v1 2/2] x86: Use rdtsc for generating entropy for random_bits Noah Goldstein
2022-03-29 19:51 ` [PATCH v1 1/2] random-bits: Factor out entropy generating function Adhemerval Zanella
2022-03-29 19:56 ` Noah Goldstein
2022-03-29 20:04 ` Noah Goldstein
2022-03-29 20:14 ` H.J. Lu
2022-03-29 20:44 ` Adhemerval Zanella
2022-03-29 20:52 ` Noah Goldstein
2022-03-29 20:37 ` Adhemerval Zanella
2022-03-29 20:44 ` Noah Goldstein
2022-03-30 15:37 ` Adhemerval Zanella
2022-03-30 16:30 ` Noah Goldstein
2022-03-30 19:38 ` Cristian Rodríguez
2022-03-31 4:45 ` Jason A. Donenfeld
2022-03-31 10:08 ` Cristian Rodríguez
2022-03-31 11:17 ` Adhemerval Zanella
2022-03-31 11:25 ` Cristian Rodríguez
2022-03-31 11:48 ` Adhemerval Zanella
2022-03-31 12:14 ` Cristian Rodríguez
2022-03-31 13:12 ` Yann Droneaud
2022-03-31 15:31 ` Jason A. Donenfeld
2022-03-31 18:16 ` Noah Goldstein
2022-03-31 21:57 ` Cristian Rodríguez
2022-03-31 22:33 ` Noah Goldstein
2022-03-31 22:51 ` Jason A. Donenfeld
2022-03-31 23:05 ` Noah Goldstein
2022-03-31 23:25 ` Jason A. Donenfeld
2022-04-01 18:01 ` Cristian Rodríguez
2022-04-04 17:42 ` Adhemerval Zanella
2022-04-04 18:23 ` Noah Goldstein [this message]
2022-04-04 18:38 ` Adhemerval Zanella
2022-04-04 18:52 ` Noah Goldstein
2022-04-04 19:20 ` Adhemerval Zanella
2022-04-04 19:48 ` Noah Goldstein
2022-04-04 19:57 ` Adhemerval Zanella
2022-04-04 14:51 ` Florian Weimer
2022-04-04 14:54 ` Jason A. Donenfeld
2022-04-04 15:00 ` Florian Weimer
2022-04-04 16:51 ` Noah Goldstein
2022-04-04 17:22 ` Adhemerval Zanella
2022-04-04 18:32 ` Jason A. Donenfeld
2022-04-04 19:16 ` Noah Goldstein
2022-04-05 0:10 ` Cristian Rodríguez
2022-04-05 0:18 ` Jason A. Donenfeld
2022-04-05 13:45 ` Cristian Rodríguez
2022-04-05 9:22 ` Florian Weimer
2022-04-04 18:28 ` Jason A. Donenfeld
2022-04-05 9:20 ` Florian Weimer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFUsyf+zbXFVRV9G1GQfRP3D+VoHVrWrGDNAhJgUuR80uvYoQw@mail.gmail.com \
--to=goldstein.w.n@gmail.com \
--cc=Jason@zx2c4.com \
--cc=adhemerval.zanella@linaro.org \
--cc=crrodriguez@opensuse.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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).