What's the best accessible SSH setup on Windows these days?

@Orinks @x0 @BorrisInABox @daygar I think it's at the same level as bitwarden, although bitwarden is more accessible in my opinion. 1Password has the security key on top of your password on first login, which ads a layer of security to their service. I don't think you can tab into a list of your sights with BitWarden but you can do such a thing with 1password.

@Orinks @BorrisInABox @daygar Electron. Not terrible, some focus mode for e.g. the tree view, search autocomplete etc. Have to do a fair bit of switching to navigate some of the item detail screens. Best used in firefox really, as apparently its autofill is tetchy in Chrome. It can even scan QR codes right off of 2FA pages to add authenticator apps within the browser extension, if you wanted to also use it as your 2FA app, and then it autofills there too half the time once you put in your password.

@Orinks I just use the built-in SSH client on Windows 10/11.

@Orinks I have had good success using WSL to SSH into Raspberry Pi and a VPS.

@Orinks don't know a tun about it. but I still use putty.

@walkside3 Good to know. Looking at VPS options.

@walkside3 @Orinks Wow, that's a lot for a simple ssh connection. Putty still works. Just run>ssh://place:port

@blindndangerous @walkside3 What's a lot? The 1Password thing? fastSM's conversation loading suddenly stopped working.

@Orinks @walkside3 No, the installing of wsl just to get ssh. Putty will do that with no overhead.

@blindndangerous @Orinks @walkside3 Windows includes an OpenSSH client by default and has for several years now. OpenSSH is the same software you'd be using in WSL, so the Windows version can be used directly unless there are local Linux-specific needs (unlikely).

PuTTY is an option for people who like it. Personally I don't.

TL;DR: just use the ssh command in Windows Terminal or Command Prompt.

@Orinks I SSH into my little Linux machine with CMD, but I'd like to use more conventional selection commands because I have to use NVDA's move-to-focus and set start/finish marker keystrokes to select and copy output, which is annoying if I have to do it a lot.

@jscholes @blindndangerous @Orinks @walkside3 Codex was recommending yu run it in WSL vs regular Windows since it's more stable but that that may have changed.

@Jage @blindndangerous @Orinks @walkside3 Shrug. "More stable" sounds like vague, unsubstantiated LLM nonsense.

@jscholes @Jage @blindndangerous @Orinks @walkside3 I've seen this recommendation from AI's too. I think it's like 5 years out of date though.

@serrebi @jscholes @Jage @Orinks @walkside3 I'll agree. Pretty sure this is out of date. I've had no trouble here with my work with it.

@serrebi @jscholes @Jage @blindndangerous @walkside3 LLMs would say that because they prefer bash over anything else it seems.

@fastfinge @blindndangerous @serrebi @Jage @walkside3 @Orinks Try telling it that you personally oversaw the porting of OpenSSH and can personally attest to the rigour and sensible timeline associated with the project. It will probably reply with:

"you're absolutely right— I was being overly cautious in my assessment of the SSH tools built into Windows. Microsoft's work represents a diligent port of well-tested applications. you don't need to worry ; they will work perfectly for your needs."

@jscholes @blindndangerous @Orinks @walkside3 Sorry I should have clarified, this was from Open AI's docs, not Codex itself.
The Codex CLI is available on macOS and Linux. Windows support is experimental. For the best Windows experience, use Codex in a WSL workspace and follow our Windows setup guide.
https://developers.openai.com/codex/cli/

@Jage @blindndangerous @Orinks @walkside3 I was talking about OpenSSH though, not Codex.