Windows support

[radix]

I'd love to be able to use Kryptonite, but I use Windows on my Desktop machine, and use native Windows tools.

I saw that there are people working to get kr working on Windows Subsystem for Linux (#54, #71), but it's not clear if that will work with my native Windows tools. For example, I'd love it if when I run git in a PowerShell or from vscode/atom/whatever IDE, if it could connect to the kr ssh agent for authentication.

[kcking]

This is a definite goal for us, perhaps in the next few weeks. In the meantime we should have WSL working tonight, but I realize that won't help you with Atom/vscode/etc.

Do you currently use puTTY on windows?

[alien2003]

Babun?

[radix]

@kcking I don't use puTTY. Most of my ssh usage is via SourceTree, or git directly from PowerShell, but also occasionally OpenSSH directly from PowerShell.

[kcking]

Ok great, I'll look into integrations for these

[clarkd]

Would be great to get this - We currently use Putty/Pageant on Windows.

[kbzowski]

Putty/Pageant +1

[steveklabnik]

Another Putty user here.

[orclev]

One vote for plain git and git bash here. Pretty sure that version is based in mingw.

[xIGBClutchIx]

Any updates on this support? @kcking

[kcking]

A contributor is working on this behind the scenes! A bare-bones pageant replacement may be available in the next couple of weeks -- stay tuned! 😄

[sebgrohn]

Any update on this issue? :) I, too, would love to use this on Windows!

[kcking]

We are now working on the next teams product, and as a result have pushed support for windows to next year. Please stay subscribed to this issue for any updates regarding windows.

[tiernano]

now with Microsoft including OpenSSH in Windows 10 (1709), would love to see this working!

[kcking]

Exciting! I just tried out the ssh client and unfortunately it currently lacks support for RSA host keys as well as ProxyCommand (which has been scoped out of their initial release). Kryptonite uses ProxyCommand to verify the signature of the host you are connecting to. I'll be following this issue PowerShell/Win32-OpenSSH#355 to see when ProxyCommand support is added, but we'll also be considering our previous alternatives if this takes too long.