* bug: incorrect ssl directory set on git-scm
@ 2015-12-26 13:35 joe
2015-12-26 18:31 ` Philip Oakley
0 siblings, 1 reply; 2+ messages in thread
From: joe @ 2015-12-26 13:35 UTC (permalink / raw)
To: git
git-scm comes with ca-bundle.trust.crt and cert.pem, it currently (2.6.4)
assumes that they are stored in
<dir name>\mingw32\libexec\ssl\certs
<dir name>\mingw32\libexec\ssl
which is not true, they are in
<dir name>\mingw32\ssl\certs
<dir name>\mingw32\ssl
^ permalink raw reply [flat|nested] 2+ messages in thread
* RE: incorrect ssl directory set on git-scm
2015-12-26 13:35 bug: incorrect ssl directory set on git-scm joe
@ 2015-12-26 18:31 ` Philip Oakley
0 siblings, 0 replies; 2+ messages in thread
From: Philip Oakley @ 2015-12-26 18:31 UTC (permalink / raw)
To: 'joe', git; +Cc: git-for-windows
> From Jo zeve
>
> git-scm comes with ca-bundle.trust.crt and cert.pem, it currently (2.6.4)
> assumes that they are stored in
>
> <dir name>\mingw32\libexec\ssl\certs
> <dir name>\mingw32\libexec\ssl
>
> which is not true, they are in
>
> <dir name>\mingw32\ssl\certs
> <dir name>\mingw32\ssl
>
The location of the CA certs is discussed in
https://github.com/git-for-windows/git/issues/425 among others (do have a
search through the issues for the other discussions).
As I understand it from watching the discussions go by, Windows and *nix
have different perspectives on where they should be stored.
If you can help with a suitable patch / Pull request that would be great.
Especially as it looks like you desire the 32 bitness version.
--
Philip
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-12-26 18:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-12-26 13:35 bug: incorrect ssl directory set on git-scm joe
2015-12-26 18:31 ` Philip Oakley
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).