From: Rasmus Villemoes <ravi@prevas.dk>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: trini@konsulko.com, heinrich.schuchardt@canonical.com,
hugo.cornelis@essensium.com, sjg@chromium.org,
paulerwan.rio@gmail.com, al.kochet@gmail.com, ada@thorsis.com,
philippe.reynes@softathome.com, u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] tools: use cryptographically safe RNG
Date: Fri, 15 Nov 2024 20:21:41 +0100 [thread overview]
Message-ID: <87bjygmhfe.fsf@prevas.dk> (raw)
In-Reply-To: <87o72g1sbd.fsf@bloch.sibelius.xs4all.nl> (Mark Kettenis's message of "Fri, 15 Nov 2024 15:32:06 +0100")
On Fri, Nov 15 2024, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>>
>> Or use getrandom(), which according to the man page has been exposed via
>> glibc since glibc 2.25. Or just read from /dev/urandom which should work
>> everywhere.
>
> $ man getrandom
> man: No entry for getrandom in the manual.
I assume this is intended to inform me that getrandom() doesn't exist on
*BSD?
As I said, reading from /dev/urandom is probably better as that also
works on BSDs automatically. If somebody tries to do crypto stuff in an
environment where they've removed such a basic device node, they get to
keep both pieces (i.e. the code should just fail)
Rasmus
next prev parent reply other threads:[~2024-11-15 19:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 16:32 [PATCH 1/1] tools: use cryptographically safe RNG Heinrich Schuchardt
2024-11-14 17:26 ` Tom Rini
2024-11-14 17:35 ` Heinrich Schuchardt
2024-11-14 17:39 ` Tom Rini
2024-11-15 0:21 ` Mark Kettenis
2024-11-15 7:18 ` Rasmus Villemoes
2024-11-15 8:34 ` Heinrich Schuchardt
2024-11-15 10:41 ` Rasmus Villemoes
2024-11-15 11:19 ` Torsten Duwe
2024-11-15 14:32 ` Mark Kettenis
2024-11-15 19:21 ` Rasmus Villemoes [this message]
2024-11-15 22:48 ` Mark Kettenis
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=87bjygmhfe.fsf@prevas.dk \
--to=ravi@prevas.dk \
--cc=ada@thorsis.com \
--cc=al.kochet@gmail.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=hugo.cornelis@essensium.com \
--cc=mark.kettenis@xs4all.nl \
--cc=paulerwan.rio@gmail.com \
--cc=philippe.reynes@softathome.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.