From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: libc-alpha@sourceware.org, "Alejandro Colomar" <alx@kernel.org>,
"Theo de Raadt" <deraadt@theos.com>,
"Todd C . Miller" <Todd.Miller@sudo.ws>,
"Cristian Rodríguez" <crrodriguez@opensuse.org>,
"Adhemerval Zanella" <adhemerval.zanella@linaro.org>,
"Yann Droneaud" <ydroneaud@opteya.com>,
"Joseph Myers" <joseph@codesourcery.com>
Subject: Re: [PATCH] Give a useful meaning to arc4random_uniform(0);
Date: Sat, 31 Dec 2022 14:39:00 +0100 [thread overview]
Message-ID: <b33694bd-4006-9a65-7df9-262e380ff91c@gmail.com> (raw)
In-Reply-To: <CAHmME9p_2qHXmtZ+nm0bW1Y_4Jityq5cR4SNn161bLm2DhdfyQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 904 bytes --]
Hey Jason!
On 12/31/22 03:57, Jason A. Donenfeld wrote:
> Did you happen to CC me here because you noticed I did exactly the
> same thing in the Linux kernel recently? ;-)
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7f576b2593a978451416424e75f69ad1e3ae4efe
Ahh, I didn't know that. I CCd you because of the lengthy discussion in the
libc-alpha list about the introduction of arc4random(3). I first CCd you in
patch to shadow where I prefered getrandom(2) over arc4random(3) for problems
with libbsd.
However, it's interesting that we came to the same interfaces with completely
independent development. That gives more strength to my feeling that it's a
good interface. I'll detail more in a reply to Theo that I'll write next :)
Cheers,
Alex
P.S.: Thanks for the review in the shadow PR!
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-31 13:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 2:36 Alejandro Colomar
2022-12-31 2:48 ` Alejandro Colomar
2022-12-31 2:57 ` Jason A. Donenfeld
2022-12-31 13:39 ` Alejandro Colomar [this message]
2022-12-31 8:50 ` Theo de Raadt
2022-12-31 8:51 ` Theo de Raadt
2022-12-31 14:56 ` Alejandro Colomar
2022-12-31 15:13 ` Alejandro Colomar
2022-12-31 15:17 ` Alejandro Colomar
2022-12-31 15:59 ` Alejandro Colomar
2022-12-31 16:03 ` Alejandro Colomar
2023-01-01 8:41 ` Theo de Raadt
2022-12-31 23:07 ` Damien Miller
2022-12-31 23:58 ` Alejandro Colomar
2023-01-01 7:48 ` Ariadne Conill
2023-01-01 9:21 ` Otto Moerbeek
2023-01-01 14:05 ` Alejandro Colomar
2023-01-01 8:34 ` Theo de Raadt
2023-01-01 21:37 ` Arsen Arsenović
2023-01-01 23:50 ` Alejandro Colomar
2023-01-02 0:02 ` Arsen Arsenović
2023-01-02 11:24 ` Alejandro Colomar
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=b33694bd-4006-9a65-7df9-262e380ff91c@gmail.com \
--to=alx.manpages@gmail.com \
--cc=Jason@zx2c4.com \
--cc=Todd.Miller@sudo.ws \
--cc=adhemerval.zanella@linaro.org \
--cc=alx@kernel.org \
--cc=crrodriguez@opensuse.org \
--cc=deraadt@theos.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=ydroneaud@opteya.com \
/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).