I have an outdated (1.8.X) installation of Git for Windows1 so this might be not up to date, but from what I see in my installation,
ssh.exe (which is a build of OpenSSH) depends on
openssl.exe depends on that library and
msys-ssl-X.Y.Z.dll with these
X.Y.Z parts matching ("0.9.8" in my case). These libraries are located in the same directory as the executable files in question:
AFAIK, when building GfW, the build suite pulls and builds exactly one copy of OpenSSL so both the reslting
ssh.exe are expected to use the same set of libraries provided by OpenSSL. Hence I sense some sort of
%PATH% precedence problem.
What I would check:
type -a openssl
type -a ssh
in your Git Bash prompt, and see if they both return something starting with the "/bin/" prefix as the first (or sole) entry of their respective outputs. If you see something other, like "/c/whatever/other/path/openssl", you have another instance of the
openssl.exe program available earlier than the Git for Windows' copy thanks to your
%PATH%; the same applies to
If yes, fix the contents of
Get a copy of
depends.exe and run it against
openssl.exe from your GfW install to see which libraries they link to, and where those are located. This might give you the clue as to where to look if something appears to be wrong.
1 It's not "msysGit" but "Git for Windows": "msysGit" is a very old name of the project which is used for quite some time to refer to the development environment for Git for Windows while the latter term is used to refer to the end product: the Windows port of Git and a binary installer you've used to install GfW. Please stick to this terminology to not increase the confusion.