From: Rasmus Villemoes <ravi@prevas.dk>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
Tom Rini <trini@konsulko.com>,
hugo.cornelis@essensium.com, Simon Glass <sjg@chromium.org>,
paulerwan.rio@gmail.com, al.kochet@gmail.com, ada@thorsis.com,
Philippe Reynes <philippe.reynes@softathome.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/1] tools: use cryptographically safe RNG
Date: Fri, 15 Nov 2024 11:41:25 +0100 [thread overview]
Message-ID: <87ldxkn5ii.fsf@prevas.dk> (raw)
In-Reply-To: <CAM=mAOkaHf-TZ1Xw0W6kcYV7G+9wCJk14svaiCtdt6V1KpVQ4A@mail.gmail.com> (Heinrich Schuchardt's message of "Fri, 15 Nov 2024 09:34:54 +0100")
On Fri, Nov 15 2024, Heinrich Schuchardt <heinrich.schuchardt@canonical.com> wrote:
>> >
>> > Linking against libbsd might be an alternative on older systems.
>>
>> 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.
>>
>> Rasmus
>>
>
>
> /dev/urandom is not available in containers.
What container runtime doesn't provide such basic nodes to containers?
Is /dev/null also not available in those containers? Strange.
And how, in that case, would the C library (or libbsd, or whatever
implements arc4random) then actually obtain random bytes to hand out or
seed its internal state? Using arc4random() or rand48() or xkcd221()
doesn't fix lack of access to proper random numbers, it may just hide
the problem and silence some static checker that knows "random() is
bad!", but doesn't know that arc4random() might be just as bad if used
in a crippled environment.
Rasmus
next prev parent reply other threads:[~2024-11-15 10:41 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 [this message]
2024-11-15 11:19 ` Torsten Duwe
2024-11-15 14:32 ` Mark Kettenis
2024-11-15 19:21 ` Rasmus Villemoes
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=87ldxkn5ii.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.