Skip to content

Bug with git bash and OpenSSL usage on Windows - that affects Self-Signed-Certificates-Generator #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
TAbdiukov opened this issue Jul 28, 2024 · 3 comments

Comments

@TAbdiukov
Copy link

Git Bash for Widows with default installation settings cannot utilize OpenSSL properly. Hence a workaround is needed.

More info: git-for-windows/git#5079

@TAbdiukov
Copy link
Author

TAbdiukov commented Jul 28, 2024

It seems that, so use this script on Windows, this setting must be changed as follows:
image

Current solution is to reinstall entire Git with the setting set as shown above.

@Vinalti
Copy link
Owner

Vinalti commented Jul 28, 2024

Ah yes that's possible, what about using the WSL (Windows Subsystem for Linux) ?

@TAbdiukov
Copy link
Author

Here is my experience with WSL (I may be doing it incorrectly),

PS C:\Projects\Self-Signed-Certificates-Generator> wsl -e sh generate_certificate.sh
: not foundrtificate.sh: 7:
: not foundrtificate.sh: 14:
generate_certificate.sh: 16: Syntax error: "(" unexpected
PS C:\Projects\Self-Signed-Certificates-Generator> wsl -e bash generate_certificate.sh
generate_certificate.sh: line 7: $'\r': command not found
generate_certificate.sh: line 14: $'\r': command not found
generate_certificate.sh: line 16: syntax error near unexpected token `$'{\r''
'enerate_certificate.sh: line 16: `function short_usage(){
PS C:\Projects\Self-Signed-Certificates-Generator>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants