Bug with bash and OpenSSL usage on Windows

  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 ``` however, openssl just hung (on Windows). Cmd can execute this command, but bash cannot.

What did you expect to happen? (Expected behavior)

openssl to generate messages about key generation to stdout

What happened instead? (Actual behavior)

openssl just hung

What's different between what you expected and what actually happened?

openssl just hung, rendering it unusable within bash Windows

Anything else you want to add:

This is an issue specifically with Windows x64.

Please review the rest of the bug report below. You can delete any lines you don't wish to share.

[System Info] git version: git version 2.45.2.windows.1 cpu: x86_64 built from commit: 91d03cb2e4fbf6ad961ace739b8a646868cb154d sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 19044 compiler info: gnuc: 14.1 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe

[Enabled Hooks] not run from a git repository - no hooks to show