From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: "'Git List'" <git@vger.kernel.org>,
"'brian m. carlson'" <sandals@crustytoothpaste.net>
Subject: RE: Problems with CSPRNG in wrapper.c
Date: Mon, 27 Feb 2023 18:23:36 -0500 [thread overview]
Message-ID: <003e01d94b02$877c2c20$96748460$@nexbridge.com> (raw)
In-Reply-To: <xmqqv8jmr98f.fsf@gitster.g>
On Monday, February 27, 2023 6:15 PM, Junio C Hamano wrote:
><rsbecker@nexbridge.com> writes:
>
>> First, I was not aware that csprng was a git dependency ...
>
>You can choose from implementations that depend on common external
libraries
>and system functions, but we have a fallback internal implementation that
only
>requires /dev/urandom.
>
>See description for CSPRNG_METHOD in Makefile and 05cd988d (wrapper:
>add a helper to generate numbers from a CSPRNG, 2022-01-17) for additional
>background.
I have already been down that path, but not successfully. /dev/urandom is
not available on the platform - never has, never will to my knowledge. This
does appear to work if PRNGD is correctly running, but I can't seem to get
that to work on this site. The config.mak.uname for NonStop does specify:
CSPRNG_METHOD = openssl
which should use OPENSSL_random(), shouldn't it? OpenSSL 3.0 uses the
_rdrand() builtin so should ever go to PRNGD, but it seems like this is
anyway. Debugging isn't possible as this is not on my own systems - and
things work here. Is there any kind of tracing I can do?
next prev parent reply other threads:[~2023-02-27 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 23:06 Problems with CSPRNG in wrapper.c rsbecker
2023-02-27 23:15 ` Junio C Hamano
2023-02-27 23:23 ` rsbecker [this message]
2023-02-28 0:11 ` brian m. carlson
2023-02-28 0:51 ` rsbecker
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='003e01d94b02$877c2c20$96748460$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/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).