mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #159] CA installation in Windows git-bash (curl there, etc) #102
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#102
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rfay on GitHub (Apr 24, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/159
It would be wonderful if in addition to all the wonderful places the CA is already installed it could be installed in the git-bash ecosystem (for curl in windows git bash).
Thanks for mkcert! it's is an amazing breakthrough. I'm integrating it into ddev a local web development environment which runs on most platforms. And it's now able to trust local certs for the very first time. Thanks!
@FiloSottile commented on GitHub (Jun 1, 2019):
Can you provide some more info on that ecosystem? I don't use Windows, so I wouldn't know where to start to find its root store.
@rfay commented on GitHub (Jun 3, 2019):
Thanks, I haven't found a solution yet, but poking around on the web:
git config --global http.sslBackend schannel... but that seems to be specific to git (as expected, since it uses git config)I haven't tried the first with the curl that ships in the git-for-windows world; maybe it would work. The second (git config) approach definitely didn't work for me.
@rfay commented on GitHub (Jun 3, 2019):
It looks to me like
does the job from within git-bash context.
Outside git-bash context, I believe the directory is typically
C:\Program Files\Git\mingw64\ssl\certs@closedstack commented on GitHub (Oct 7, 2020):
In Most corporate settings it is best to set it to use Windows Trusted CA Store, since that will be managed by your IT (like if they inspect outbound HTTPS traffic) using
git config --global http.sslBackend schannelas suggested by @rfay
@mkontani commented on GitHub (Oct 12, 2020):
Typically, windows has no certificates dir, but stores in win registory.
If you want to import into the registory with using cli, It seems that
certutilcommand can be used.See: https://superuser.com/questions/1506440/import-certificates-using-command-line-on-windows
@jkugler commented on GitHub (Dec 9, 2020):
@rfay From where did you acquire mkcert? It does not seem to be in my default git bash install.
Edit: I might not need it. Just cat and append to the ca-bundle.crt file.
Edit 2: solution not working for me...so, may be a problem somewhere else.
@rfay commented on GitHub (Dec 9, 2020):
@jkugler - download the windows binary from the releases page, https://github.com/FiloSottile/mkcert/releases
@MarlonMrN commented on GitHub (Jun 11, 2021):
but how to make that config for the entire git-bash? For example, I cannot perform any curls to https endpoints in my bash... (and all of my package managers suffer from the same issue... it's a pain to add the certificates for each of them, as they expire...)
Any ideas how to do that?