Re: Bug with SSH keys loaded into ssh-add

>
> On 2024-11-24 at 16:23:21, Jacob Pfundstein wrote:
> > Hello everyone,
>
> Hi,
>
> > I've recently encountered a bug/issue while using Git for Windows. You
> > can load a passphrase-secured SSH key into the ssh agent using
> > ssh-add. As long as the key is loaded into the ssh agent, you don't
> > have to enter the passphrase when using the key. However, when I do
> > git pull or something similar, Git still prompts me for the
> > passphrase.
>
> This isn't Git prompting you for the passphrase.  Git passes the
> terminal through to OpenSSH, which is prompting you for the passphrase.
> There's really nothing that Git can do, since it doesn't know what
> OpenSSH will do.
>
> I can make a guess about what might be going wrong here so you can try
> to see if that fixes things, and if not, you could try contacting the
> Git for Windows issue tracker at [0].  Please be sure to search first,
> including the closed issues, as the question may already have been asked
> and answered.
>
> My guess as to what's going on is that you're using two different
> versions of OpenSSH, since there are two with Git for Windows.  One is
> shipped with Git for Windows, and one is the one shipped with Windows. I
> think MSYS2 may implement sockets in an unusual way, which means that if
> the agent is from one version and the `ssh` binary is from another
> version, that they may not be able to communicate properly.  In such a
> case, OpenSSH would prompt you again since it can't contact the agent.
> You could try using both from the same version (I think there's an
> install option for that) or try using Git Bash to see if that fixes the
> problem (even if that isn't a good solution for you, it's useful to know
> from a debugging point of view).
>
> As I said, this is just a guess and I don't use Windows, so you'll have
> to try what I mentioned above or open an issue.
>
> [0] https://github.com/git-for-windows/git/issues
> --
> brian m. carlson (they/them or he/him)
> Toronto, Ontario, CA