3 ms·

first thought- MS didn't support SSH?

by glxc 11y ago

acomjean 11y ago
I don't think so. Thus everyone looking for a free client. The PuTTY client being popular. The offical is at a ~sgtatham/putty/ web address which seems very old school. Though recently some not official versions had malware installed if I'm remembering. I'm wondering if this is a response to that.
- wlesieutre 11y ago
  Old school and served over HTTP, making it not that hard for someone to MITM you and give you a backdoored client when you download it. Don't worry though, the page has checksums you can validate your download against! Except those are also served over HTTP.
  - sfk 11y ago
    Yes, sgtatham should move to a secure location like GitHub. Homakov is perhaps willing to guide the transition.
    - JoeAltmaier 11y ago
      Maybe somebody could automate the process, provide a service?!
- bad_user 11y ago
  An SSH client is also included with Git for Windows, since it includes MSYS, plus Git needs to connect through SSH. There's also Cygwin, which comes with the OpenSSH server in addition to the client. For a preconfigured Cygwin when I needed it, found Babun to be useful: https://babun.github.io/ https://babun.github.io/
  - Encosia 11y ago
    Yes. Coupled with cmder for a nice terminal interface, msysgit's ssh is what I've been using for about the past year and a half. Works great.
dredmorbius 11y ago
There's no default included SSH client. SSH server support is also limited, though possible under, say, Cygwin. SSHing into a Windows box with file shares open to other hosts is ... interesting. You're outside the normal user authentication scope, and CIFS/SMB fileshare is (pardon extremely imprecise descriptions) authenticated and contextualized via the desktop login. CALS accounting too, and I've run into exceptionally annoying concurrency limits as a result. Contrast with, say, NFS or iSCSI where filesystem mounts are managed at the system level, possibly with automounter support for apparently seamless behavior. My read of this is that this is largely geared at 1) providing additional support for OpenSSH development (a Good Thing), and 2) (finally) delivering an SSH client on the default install. Really, about fucking time, that.
nailer 11y ago
You had to pay for http://www.powershellserver.com/ http://www.powershellserver.com/ before, or use a Cygwin-type setup. There was nothing native and free.

first thought- MS didn't support SSH?

by glxc 11y ago

first thought- MS didn't support SSH?

I don't think so. Thus everyone looking for a free client. The PuTTY client being popular. The offical is at a ~sgtatham/putty/ web address which seems very old school. Though recently some not official versions had malware installed if I'm remembering. I'm wondering if this is a response to that.

wlesieutre 11y ago
Old school and served over HTTP, making it not that hard for someone to MITM you and give you a backdoored client when you download it. Don't worry though, the page has checksums you can validate your download against! Except those are also served over HTTP.
- sfk 11y ago
  Yes, sgtatham should move to a secure location like GitHub. Homakov is perhaps willing to guide the transition.
  - JoeAltmaier 11y ago
    Maybe somebody could automate the process, provide a service?!
bad_user 11y ago
An SSH client is also included with Git for Windows, since it includes MSYS, plus Git needs to connect through SSH. There's also Cygwin, which comes with the OpenSSH server in addition to the client. For a preconfigured Cygwin when I needed it, found Babun to be useful: https://babun.github.io/ https://babun.github.io/
- Encosia 11y ago
  Yes. Coupled with cmder for a nice terminal interface, msysgit's ssh is what I've been using for about the past year and a half. Works great.

dredmorbius 11y ago

There's no default included SSH client. SSH server support is also limited, though possible under, say, Cygwin. SSHing into a Windows box with file shares open to other hosts is ... interesting. You're outside the normal user authentication scope, and CIFS/SMB fileshare is (pardon extremely imprecise descriptions) authenticated and contextualized via the desktop login. CALS accounting too, and I've run into exceptionally annoying concurrency limits as a result. Contrast with, say, NFS or iSCSI where filesystem mounts are managed at the system level, possibly with automounter support for apparently seamless behavior. My read of this is that this is largely geared at 1) providing additional support for OpenSSH development (a Good Thing), and 2) (finally) delivering an SSH client on the default install. Really, about fucking time, that.

nailer 11y ago

You had to pay for http://www.powershellserver.com/ http://www.powershellserver.com/ before, or use a Cygwin-type setup. There was nothing native and free.