Openssh should have been a game changer but they made a classic openssh porting bug (not reading all bytes from the channel on close) and have now been sat on the fix in “prerelease” for years. I prodded the VP over the group about the issue and they repeatedly made excuses about how the team is too small and getting updates over to the windows team is too hard. That was multiple windows releases ago. Over on GitHub if you look up git receive pack errors being frequent clone problems for windows users you’ll find constant reports ever since the git distribution stopped using its own ssh. I know a bunch of good people at Microsoft, but this leadership is incapable of operating in a user centric manner and shouldn’t be trusted with embedded OSS forks.

I'm a simple man, if I open the shell and `ssh [email protected]` doesn't work, I don't use that computer. Idk if Windows has fixed that yet or why it's so hard for them. Also couldn't even find the shell on a Chromebook.

putty is longer necessary? That would be a wild upgrade in usability for the work laptop, shall go try it

openssh has been an optional windows component for... almost a decade now? including the server, so you can ssh into powershell as easily as into any unix-like. (last time I set it up there was some fiddling with file permissions required for key auth to work, but it does work.)

OpenSSH on Windows is great for the odd connection and SFTP session, but I still feel strongly that any serious usage should just stick with PuTTY and WinSCP. The GUI capabilities these provide are what Windows users are used to. The only benefit of built-in SSH is if you're working with some minimal image stuff, like Windows Server Core or Tiny11. IMHO.

imo the interesting part in opensssh into Windows.

IIRC (it's been a while) I used the server with vscode remote ssh extension.

I feel old but its only 6 years not a decade :P

I guess 'before covid' and 'decade ago' is the same in my mind ;) I might have been using a preview build back then, too

I dislike using putty, I use the ssh client from WSL. Just feels .. better. And bash/fish history helps.

On the other hand sometimes the GUI on WSL decides to break and you have to restart the whole thing.

Aged like fine milk