Personally I would recommend anyone on Windows to use WSL (which supports ssh and scp out of the box) but it's nice to see this is available for people who don't want to use WSL.
Personally I would recommend anyone on Windows to use WSL (which supports ssh and scp out of the box) but it's nice to see this is available for people who don't want to use WSL.
Do you have something you can share publicly to demonstrate to the uninitiated how painful this has been?
Putty's dedication to the Windows registry has caused me tremendous grief.
Helping end users (Windows developers) configure Putty is the bane of my "discount" remote access strategy (SSH port forwarding).
It gets even worse too because in some of my courses (like my Let's Encrypt course) I request people to securely transfer files to their DO server.
So now they have to set up WinSCP or a comparable tool, which has its own set of lengthly instructions.
And for comparison on MacOS, Linux or WSL it's just:
Create SSH key: ssh-keygen -t rsa (hit enter a couple of times)
SSH into a server: ssh user@host
SCP a file to a server: scp foo.conf user@host:/tmp