From: Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>
To: Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
Cc: Henrique de Moraes Holschuh
<hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>,
Linux Kernel Developers List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux API <linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH -v5] random: introduce getrandom(2) system call
Date: Fri, 25 Jul 2014 09:22:25 -0400 [thread overview]
Message-ID: <20140725132225.GQ1865@thunk.org> (raw)
In-Reply-To: <CALCETrVgKMVnBuzE+bCXaUPRrqhVxwv4AXmJrUJSYws5rZxhJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Jul 24, 2014 at 04:27:36PM -0700, Andy Lutomirski wrote:
>
> I think that people might do:
>
> try getrandom(GRND_RANDOM)
> fall back to /dev/random
> fall back to something intensely stupid
>
> We want them to at least attempt the fallback from GRND_RANDOM to !GRND_RANDOM.
We can't legislate against stupidity. Seriously, the best way to do
this is to write a good userspace library and encourage application
writers to use it.
Regards,
- Ted
next prev parent reply other threads:[~2014-07-25 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 14:31 [PATCH -v5] random: introduce getrandom(2) system call Theodore Ts'o
2014-07-24 15:18 ` Henrique de Moraes Holschuh
2014-07-24 15:21 ` Andy Lutomirski
2014-07-24 19:02 ` Theodore Ts'o
2014-07-24 20:30 ` Henrique de Moraes Holschuh
2014-07-24 20:54 ` Andy Lutomirski
2014-07-24 23:27 ` H. Peter Anvin
2014-07-24 23:24 ` Theodore Ts'o
2014-07-24 23:27 ` Andy Lutomirski
[not found] ` <CALCETrVgKMVnBuzE+bCXaUPRrqhVxwv4AXmJrUJSYws5rZxhJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-25 13:22 ` Theodore Ts'o [this message]
[not found] ` <20140724232434.GN6673-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2014-07-25 12:46 ` Henrique de Moraes Holschuh
[not found] ` <1406212287-9855-1-git-send-email-tytso-3s7WtUTddSA@public.gmane.org>
2014-07-30 14:34 ` Rolf Eike Beer
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=20140725132225.GQ1865@thunk.org \
--to=tytso-3s7wtutddsa@public.gmane.org \
--cc=hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.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 NNTP newsgroup(s).