From: Noah Goldstein <goldstein.w.n@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "Jason A. Donenfeld via Libc-alpha" <libc-alpha@sourceware.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: [PATCH v1 1/2] random-bits: Factor out entropy generating function
Date: Mon, 4 Apr 2022 11:51:41 -0500 [thread overview]
Message-ID: <CAFUsyfLYrBLH1MKsD6M4LFjqcdJraEKi-s8RpE87hAbhLpFEsw@mail.gmail.com> (raw)
In-Reply-To: <87a6d06ghc.fsf@oldenburg.str.redhat.com>
On Mon, Apr 4, 2022 at 10:00 AM Florian Weimer via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> * Jason A. Donenfeld via Libc-alpha:
>
> > _However_, based on what people have said in this thread, this all
> > seems highly unnecessary, since you just need some boring
> > statistically uniform randomness without any crypto or security
> > requirements of any kind, and it simply needs to be fast and dumb. If
> > that's the wrong set of requirements for this problem (I still have no
> > idea what the bigger picture here is), please pipe up.
>
> If we can make a cryptographically secure generator fast enough, it
> would relieve programmers of the need to choose between that and another
> generator that just gives some random-looking bits fast. If programmers
> don't have to make a choice, they can't choose incorrectly (introducing
> performance bugs or security bugs).
It sounds like you're talking about creating a user facing API. Since
random_bits
is internal do we really need so much ease of use at the cost of performance?
>
> For example, the system call overhead could be prohibitive for things
> like hash map keys if these hash maps are not used much before they are
> discarded again.
>
> Thanks,
> Florian
>
next prev parent reply other threads:[~2022-04-04 16:51 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
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 [this message]
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=CAFUsyfLYrBLH1MKsD6M4LFjqcdJraEKi-s8RpE87hAbhLpFEsw@mail.gmail.com \
--to=goldstein.w.n@gmail.com \
--cc=Jason@zx2c4.com \
--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).