From: <rsbecker@nexbridge.com>
To: "'Git List'" <git@vger.kernel.org>
Subject: Problems with CSPRNG in wrapper.c
Date: Mon, 27 Feb 2023 18:06:07 -0500 [thread overview]
Message-ID: <003d01d94b00$16abc7a0$440356e0$@nexbridge.com> (raw)
I've hit an issue with git that has me stumped at a customer site - so I
have limited visibility on what is actually wrong. This is pretty urgent
that I resolve this.
In git/wrapper (lines 477 from :
if (csprng_bytes(&v, sizeof(v)) < 0)
return error_errno("unable to get random bytes for temporary file");
First, I was not aware that csprng was a git dependency - not sure why
because we depend on OpenSSL_random that should return random bytes. Does
this still mean that there is a dependency on PRNGD, or is there another
dependency I am missing.
Should I get them to revert back to an older git version (which one)? Is a
patch needed?
Thanks,
Randall
--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.
next reply other threads:[~2023-02-27 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 23:06 rsbecker [this message]
2023-02-27 23:15 ` Problems with CSPRNG in wrapper.c Junio C Hamano
2023-02-27 23:23 ` rsbecker
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='003d01d94b00$16abc7a0$440356e0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
/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.