Yep,
It's GUI. This makes me happy because it takes me 5 minutes to explain to someone how to use it, most of which is spent reviewing SSH authentication
.
As opposed to standard SCP, which is painful, WinSCP2 allows me to instruct our site people quickly on how to update web sites, without using evil unencrypted and bandwidth hogging FTP.
OpenSSH for Windows runs as a service, and also allows you to ssh right into the box, running multiple interactive command line sessions along with your VNC sessions.
By the time I am done with a Windows box, chances are it's got the following anyway:
1. OpenSSH for Windows, which is also a Cygwin port.
2. PuTTY ssh client, because it's nice.
3. Tunnelier SSH tunneling tool.
4. A Linux or OpenBSD box as a firewall
.
5. NAT, to make tunneling over a bitch that you need Tunnelier for.
6. A completely hacked registry.
7. ACL's like mad.
8. Most of IIS completely disabled, except for ASP and Perl scripting. This is how I avoided Code Red and Nimda, because we disabled most of IIS and don't do anything more than ASP with it.
Windows = one bitch and a half to set up, but remarkably stable if you take the time to lock it down and don't use unsigned video drivers.
It takes me about 4-5x the time it takes me to set up a Linux box to set up a Windows one, since Microsoft turns on EVERYTHING by default.
Mitch