SSH for Microsoft OS

S

Sieravor

Gawd
Joined
Apr 9, 2005
Messages
943
So, I haven't seen anything on the forums for this yet, so I figured now is as good a time as any to ask.

I'm looking for recommendations for a good SSH daemon for windows based systems. I'm aware of a couple solutions, one being OpenSSH and the other being FortressSSH. Both look good, specifically the one from pragma, but I am hesitant to use anything from a 3rd party without having some personal stories.

OpenSSH is free, I know, and it works, but it's a big hassle to get it running in a windows environment. I need something that installs quickly, with as little hassle as possible, and actually works as advertised. $$$$ isn't really a problem, I just need it to be reliable and when it comes to remote CLI's and the like. There are just too many garbage apps out there to play the trial and error game in a production environment.

so, if anyone has any suggestions as to which route I should go, or if you have input at all I'd love to hear it.

Misc info:

Servers: Fully patched/updated Windows Server 2003
Workstations: Fully patched/updated Windows XP
total computers that need SSH: ~150 (lots of work if I have to use OpenSSH)
 
Are you trying to SSH into the servers or from the Workstations? In other words are you trying to do CLI type things on Windows Servers or are you accessing Linux/Unix based servers via SSH?

I guess I have just never bothered with SSHing into Windows servers before, so I am not sure what all you could do with that.
 
I have alot of CLI management utilities installed on my servers that I'd like to be able to run from anywhere.

So, essentially I need a recommendation for the actual SSH server software.

I'd also like to be able to remotely log into the workstations via SSH. I use linux systems to monitor my windows pc's and I have some webpages that I am building configuration tools for, and I need to be able to issue commands to the remote systems.

Control point --> network monitoring solution --> server/workstation via SSH.

So, I issue commands to my monitoring solution, which then sends the commands to the various systems on the network. It may sound retarded, but there is a good reason.
 
you do realize you are violating the windows xp EULA if you ever ssh in while someone is logged in to the console session? even if its from an automated utility?
 
How is it a violation of the EULA? Having a device connecting to the computer is legal under the EULA, assuming that the purpose for connection is similar to the use of the software that MS provides (remote assistance).

3rd party software is exempt from the session connections rules as long as I am only providing support for the user, which is exactly what I'm doing.

for instance, if I were to use remote assistance to help them locate/delete/modify some aspect of the system, I am within my rights to use SSH instead of the MS provided software, as long as I am performing the same duties and same actions.

::EDIT:: As a clarification, you can have multiple sessions established on a remote system if the intent is to provide assistance to the primary user.
 
vandyke has an ssh program.

you could also use cygwin, but that can be uglyish (maintenance wise especially)
 
Wow, I was going to suggest looking at ssh.com's offering until I saw their pricetag for the server version. :eek:
 
Its been a while since I have done it but OpenSSH is easy to setup and use. Is there a reason why you don't like it?

I set this up for a company whose software developers lived in Belgium. They would SSH into the server and then I would redirect a different port to allow them to get into a Unix box so they could make their code changes.

Alternatively if your Internet equipment has an SSH daemon you can connect to it and then redirect ports via SSH to get to what you need.
 
Bean Dip said:
Its been a while since I have done it but OpenSSH is easy to setup and use. Is there a reason why you don't like it?

I set this up for a company whose software developers lived in Belgium. They would SSH into the server and then I would redirect a different port to allow them to get into a Unix box so they could make their code changes.

Alternatively if your Internet equipment has an SSH daemon you can connect to it and then redirect ports via SSH to get to what you need.
Click to expand...

It's not the most elegant solution.
Updating can be a pain on multiple systems.
I still haven't found a way to kill old sessions (yes you can kill the ssh session with timeouts in sshd config, but it doesn't terminate the shell associated with it).
 
you can only 'share' sessions. When you ssh in you are having two 'users', each with their own session running software. That is not allowed.

Sieravor said:
How is it a violation of the EULA? Having a device connecting to the computer is legal under the EULA, assuming that the purpose for connection is similar to the use of the software that MS provides (remote assistance).

3rd party software is exempt from the session connections rules as long as I am only providing support for the user, which is exactly what I'm doing.

for instance, if I were to use remote assistance to help them locate/delete/modify some aspect of the system, I am within my rights to use SSH instead of the MS provided software, as long as I am performing the same duties and same actions.

::EDIT:: As a clarification, you can have multiple sessions established on a remote system if the intent is to provide assistance to the primary user.
Click to expand...
 
You must log in or register to reply here.
Back
Top