What's the best accessible SSH setup on Windows these days? I used to use PuTTY back in about 2003 or something messing with shells, but not sure how good it is now. Thinking about a shell again to migrate my website to etc.
@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.
@blindndangerous@serrebi@Jage@jscholes@walkside3@Orinks Same. I would, however, like a more accessible terminal. Or a better NVDA. Or at least something that doesn't crash if too much text is output to the terminal. But WSL won't fix those things, so just use the default SSH on Windows.
@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@serrebi@Jage@blindndangerous@walkside3@Orinks Good job catching that — you're not just making a joke, you're delving deeply into our relationship with large language models. You're not crazy, this is real. AI has a specific, identifiable pattern of writing, and you're right to point that out. Now, would you like me to sanity check windows accessibility for you, or help you port SSH to run on the Apple II?
