From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Cristian Rodríguez" <crrodriguez@opensuse.org>
Cc: Jonny Grant <jg@jguk.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>,
GNU C Library <libc-alpha@sourceware.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] Add example to rand.3
Date: Wed, 28 Dec 2022 22:18:52 +0100 [thread overview]
Message-ID: <07f63ec3-8b0b-4720-daa7-d46a0dd36860@gmail.com> (raw)
In-Reply-To: <CAPBLoAdEbaH8yi_T=_BNAcgwE7=Pq+7QybwfHXNB92QFdx0XPQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 997 bytes --]
On 12/28/22 22:04, Cristian Rodríguez wrote:
> On Wed, Dec 28, 2022 at 5:57 PM Alejandro Colomar via Libc-alpha
> <libc-alpha@sourceware.org> wrote:
>
>> Ahh, I didn't connect the dots the other day! We don't need to wait for glibc.
>> libbsd already provides arc4random on GNU/Linux systems, so I can already
>> recommend using arc4random to seed srand(3).
>>
>> I'll prepare a patch...
>>
>
> I would suggest avoiding that, as it suffers from all the problems
> previously discussed on this list , on the relevant arc4random thread
>
> tl;dr , it can't be safe without kernel support, as you need to know
> when to drop the buffer. (on fork, on resume plus on $deity knows
> condition for which there is no kernel notification about)
Maybe I'd remove the SEE ALSO reference to arc4random(3bsd) then, so that I
don't "recommend" using it. I'll add arc4random(3) to SEE ALSO when we have a
manual page for the function.
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-12-28 21:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 21:50 [PATCH] Add example to rand.3 Jonny Grant
2022-12-26 22:29 ` Alejandro Colomar
2022-12-27 13:07 ` Cristian Rodríguez
2022-12-27 23:33 ` Alejandro Colomar
2022-12-28 0:00 ` G. Branden Robinson
2022-12-28 0:41 ` Alejandro Colomar
2022-12-28 12:21 ` Cristian Rodríguez
2022-12-30 18:15 ` Joseph Myers
2022-12-30 18:20 ` Alejandro Colomar
2022-12-30 18:50 ` Joseph Myers
2022-12-30 18:58 ` Alejandro Colomar
2022-12-30 19:11 ` Cristian Rodríguez
2022-12-30 21:08 ` Joseph Myers
2022-12-30 21:15 ` Internal organization of "the implementation" (was: [PATCH] Add example to rand.3) Alejandro Colomar
2022-12-30 21:50 ` Joseph Myers
2022-12-27 21:37 ` [PATCH] Add example to rand.3 Jonny Grant
2022-12-27 23:11 ` Alejandro Colomar
2022-12-28 20:51 ` Jonny Grant
2022-12-28 20:56 ` Alejandro Colomar
2022-12-28 21:03 ` Alejandro Colomar
2022-12-28 21:04 ` Alejandro Colomar
2022-12-28 21:25 ` Jonny Grant
2022-12-28 21:32 ` Alejandro Colomar
2022-12-28 21:04 ` Cristian Rodríguez
2022-12-28 21:11 ` Alejandro Colomar
2022-12-28 21:19 ` Jonny Grant
2022-12-28 21:18 ` Alejandro Colomar [this message]
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=07f63ec3-8b0b-4720-daa7-d46a0dd36860@gmail.com \
--to=alx.manpages@gmail.com \
--cc=crrodriguez@opensuse.org \
--cc=fweimer@redhat.com \
--cc=jg@jguk.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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