public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
	 "Jason A. Donenfeld via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v1 1/2] random-bits: Factor out entropy generating function
Date: Mon, 4 Apr 2022 20:32:22 +0200	[thread overview]
Message-ID: <CAHmME9rwPDehwCG6j4LKUoKEHkSzcJXDwL8iMYc2P+nqj7Miqw@mail.gmail.com> (raw)
In-Reply-To: <CAFUsyfLYrBLH1MKsD6M4LFjqcdJraEKi-s8RpE87hAbhLpFEsw@mail.gmail.com>

Hi Noah,

On Mon, Apr 4, 2022 at 6:51 PM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
>
> 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?

Right, my thoughts exactly. If you just need some statistically
uniform bytes for whatever it is whomever told me above something
about threading something about no security something about really
doesn't matter, then I fail to see why https://א.cc/xrAIhCvy/c is
insufficient, and I also don't know why this thread is chasing its
tail about rdtsc.

I'd appreciate it if somebody in a leadership position could let me
know what is asked of me here, since somebody CC'd me into this
thread. I've already made two RNGs here for various spitballed
objectives. I'd like to refrain from spending time on a third until
there's some clarity on what it is you all want. Probably it makes
sense for me to leave this thread alone for a bit while you guys work
that out.

Jason

  parent reply	other threads:[~2022-04-04 18:32 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
2022-04-04 17:22                       ` Adhemerval Zanella
2022-04-04 18:32                       ` Jason A. Donenfeld [this message]
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=CAHmME9rwPDehwCG6j4LKUoKEHkSzcJXDwL8iMYc2P+nqj7Miqw@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=fweimer@redhat.com \
    --cc=goldstein.w.n@gmail.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).