From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Tim Abdiukov <tabdiukov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug with bash and OpenSSL usage on Windows
Date: Sat, 27 Jul 2024 14:36:00 +0000 [thread overview]
Message-ID: <ZqUF0ANz9qX-wWEN@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CAD+08a87xxVRxO1eiWiam-7xvq=AyKUB-MzqG-r=rM_SYbquBQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Hey,
On 2024-07-26 at 19:40:48, Tim Abdiukov wrote:
> What did you do before the bug happened? (Steps to reproduce your issue)
> Tried to generate a self-signed certificate using git bash.
>
> Using git bash, I ran
> ```
> openssl genrsa -aes256 (private key location) 4096
> ```
The Git project doesn't ship OpenSSL, or, for that matter, any binaries
at all. All we ship is source versions of Git which various
distributors compile, sometimes with other binaries.
It looks like you're probably using Git for Windows, which _does_ ship
OpenSSL, and so you probably want to contact them using their issue
tracker[0] once you've verified that it hasn't already been reported.
[0] https://github.com/git-for-windows/git
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2024-07-27 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 19:40 Bug with bash and OpenSSL usage on Windows Tim Abdiukov
2024-07-26 19:48 ` Tim Abdiukov
2024-07-27 14:36 ` brian m. carlson [this message]
2024-07-27 15:53 ` Junio C Hamano
2024-07-27 15:58 ` Junio C Hamano
2024-07-27 16:05 ` Eric Sunshine
2024-07-27 21:20 ` brian m. carlson
2024-07-27 22:01 ` Jeff King
2024-08-13 13:06 ` Johannes Schindelin
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=ZqUF0ANz9qX-wWEN@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=tabdiukov@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