git-credential-manager VS wsl2-ssh-pageant

You can still use HTTPS, just not username/password as authentication. Personally, I think using HTTPS Git Credential Manager is simpler than SSH, as GCM allows you to use GitHub OAuth in your browser to sign in.

Hi, use git Credential Manager https://github.com/git-ecosystem/git-credential-manager been using it with Github and Azure Repo. Make sure that you update your machine global git config to use it.

Download Git for Windows and choose Git Credential Manager (GCM) as credential helper on the installation steps.

This is an application indepentend from git, so best use its channels. A quick search through their Github repo found this issue: https://github.com/GitCredentialManager/git-credential-manager/issues/899

Download the GCM Deb file from here - https://github.com/GitCredentialManager/git-credential-manager/releases/download/v2.0.877/gcm-linux_amd64.2.0.877.deb

When working with external Git repositories it is best practice to use multi-factor HTTPS authentication. It is best to leave the default option by using the built in Git Credential Manager.

(We haven't started using Git Credential Manager Core yet and I haven't done any research into it, so I don't know if it'll throw a wrench in things.)

Hey there! So, I've been using WSL2 with a yubikey for gpg, which is pretty sweet. Basically, this setup uses a Unix socket to Windows gpg-agent and pageant (if you're curious, you can find all the details in this GitHub repo: https://github.com/BlackReloaded/wsl2-ssh-pageant). It's been working great for about a month or so, until I recently installed the Windows Store version for WSLg support on Windows 10. But now, my WSL2 isn't talking to the Win gpg-agent anymore. I've searched GitHub for answers, but no luck yet. Figured I'd post here and see if there are others in the same boat or who might have some tips on this pesky socket issue. Thanks!

You should use the latest wsl2-ssh-peagent, which has a new --gpgConfigBasepath option to allow you to specify the .gnupg directory in Windows.

sshCommand = C:/utils/OpenSSH-Win64/ssh.exe

For GPG, the only things I've done is to use gpg-agent and set up a passthrough for gpg-agent to WSL2 for both OpenSSH and GPG via https://github.com/BlackReloaded/wsl2-ssh-pageant/ since I do development both natively on Windows and via WSL2.

Yeah, I've been using a Yubikey for a bit over a year and I'm already a huge fan of the way it works with SSH/Git. It's a bit more of a pain to set up with WSL2 since you need something like https://github.com/BlackReloaded/wsl2-ssh-pageant but it's absolutely worth the setup time.

I use PuTTY's pageant and https://github.com/BlackReloaded/wsl2-ssh-pageant to share keys between environments but you still need to enter your passphrase at power-on. Window's ssh-agent looks like a better solution. No need to re-enter the passphrase and no need to keep the private key around.