Windows SSH Server
Dick Thiot
Bob Rasmussen
Dick, what factors are driving the push to SSH?
> --
> IMPORTANT: T24/Globus posts are no longer accepted on this forum.
>
> To post, send email to jB...@googlegroups.com
> To unsubscribe, send email to jBASE-un...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
>
>
>
>
Regards,
....Bob Rasmussen, President, Rasmussen Software, Inc.
personal e-mail: r...@anzio.com
company e-mail: r...@anzio.com
voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
fax: (US) 503-624-0760
web: http://www.anzio.com
street address: Rasmussen Software, Inc.
10240 SW Nimbus, Suite L9
Portland, OR 97223 USA
Alexander Demin
Tony Gravagno
Dick, I installed Cygwin on the target system and added a SSHD server. So the client does an SSH to this server, which then does port forwarding (tunneling) to the jBASE telnet server. This might seem like cumbersome solution, having a Linux implementation sitting on top of Windows just for one service. But it's actually very easy to install (to my surprise and relief), the overhead is minimal, and over time you may find having Linux functionality in Windows to be quite refreshing - sort of like having Pick commands from the Windows command like with jBase compared to other Pick platforms. (Sorry Jim)
Install Cygwin with OpenSSH, OpenSSL, and inetutils.
Google for these phrases to get info:
ssh port forwarding cygwin
ssh port forwarding linux
ssh tunnel
install cygwin
mobaxterm << this is a pre-packaged "distro" with Cygwin and SSH, look for others
The above method does not require anything special on the client other than switching from telnet to SSH of course. If you're using a telnet client and don't want to change to SSH for some reason, Google:
windows ssh tunnel client
You can install software in Windows which accepts connections on port X and sends them to another server on port Y - with or without encryption. I used this to accept a localhost telnet connection on port 23 from the client, pass the request over SSH to a remote server, and then as above re-route to a telnet server. The result is securing the internet connection while still doing a local insecure telnet.
Frankly it's been a long time since I did this and I'm embarrassed to say I don't have detailed notes on specific software or settings - but over time new software and docs turn up on the web, so you probably wouldn't want my old notes anyway.
HTH
T
Tony Gravagno
Nebula Research and Development
TG@ remove.pleaseNebula-RnD.com
Nebula R&D sells mv.NET and other Pick/MultiValue products
worldwide, and provides related development services
Visit http://PickWiki.com! Contribute!
Kevin Powick
On Monday, 26 November 2012 11:54:47 UTC-5, Dick Thiot wrote:
We currently have a need to implement an SSH server for Windows for a jBASE server. Can others on the list let us know how you have approached SSH servers on Windows for jBASE?
Bob Rasmussen
necessary to connect a client to jBase? Do you have to run an SSH client,
enable port forwarding, and then run a telnet client over that tunnel?
Dan Ell
jBASE is simply a windows program. The SSH server has to run a script that would set the environment variables, but there is nothing else needed.
Dan Ell
Tony Gravagno
the environment vars are set there. How would environment vars set by
the SSHD relate to individual sessions? Especially (note from below)
if the SSHD isn't even on the same system as jBase.
To answer Bob's question, yes, the SSHD accepts a connection on port X
and then transfers that to port Y, but that's not so much "port
forwarding" or tunneling, that's what an SSHD does. Point here is that
no other software required.
Regarding Bitvise - yeah it's great but the Cygwin solution is too,
and it's free, and has more feature, and takes the same amount of time
to setup. When someone thinks Cygwin, they might think "OS emulation"
or "complex" or something similar. Actually I found it dirt-simple to
install and there's even a MSI installer which does all of the initial
setup in the same number of clicks as Bitvise. After that the
configuration is of course different, but no more or less complex than
any commercial offering.
In my testing, I setup a virtual machine with Windows installed as the
guest and with disk updates turned off. This allowed me to try and
repeat the process as many times as necessary to understand it without
doing anything permanent. I then did the Cygwin MSI and setup with
OpenSSH. Then I did a SSH into that virtual which routed the telnet to
another virtual which was actually running jBase. Once I confirmed
everything was working I just repeated the process in the live box.
From there I could SSH or telnet to the live box at any time. Cygwin
starts with windows as does its SSHD service so once it's running it's
completely transparent.
T
Manoj K
Hi,
The best is to install cygwin on both the systems. Cygwin can use as SSH server and client.
Manoj
Kevin Powick
On Wednesday, 28 November 2012 15:16:43 UTC-5, NebulaTonyG wrote:
...the SSHD accepts a connection on port X
and then transfers that to port Y, but that's not so much "port
forwarding" or tunneling, that's what an SSHD does.
Regarding Bitvise - yeah it's great but the Cygwin solution is too,
and it's free
and has more feature
and takes the same amount of time to setup.
I found it dirt-simple to
install and there's even a MSI installer which does all of the initial
setup in the same number of clicks as Bitvise.
Daniel Klein
--Kevin Powick
Tony Gravagno
I'll preface this by saying anything I know about this comes from discussions I had with Kevin in CDP just over a year ago. Based on those discussions and very little pain from experimentation, I was able to get this stuff to work, and for free. That's the whole take-home here. I'm just conveying what I learned back then.
Yeah, awkward phrasing about "what an SSD does". My point was that you don't need SSHD and port-forwarding and tunneling because SSH already does that. Consider this client-side command:
ssh -L <local-port-to-listen>:<remote-host>:<remote-port>
Tunneling is sometimes defined the same as port forwarding but they're not exactly the same. The above command describes the tunneling of a connection from client to server, and subsequently the SSHD does port forwarding to the ultimate destination (the jBase telnetd). So if you're using SSH you don't need separate tunneling or port forwarding software, which seemed to be implied by prior notes. That was my point.
As to many more features and the "such as" - that would be all features available in Cygwin, Linux software running under Windows, XTerm, and any number of command-line utilities like grep, awk, and sed. You don't get any of that with a product dedicated to being nothing more than a SSHD.
As to installing Cygwin, you conveniently left out the sentence following the one you quoted where I said "After that the configuration is of course different, but no more or less complex than any commercial offering.". What I was talking about was the few number of clicks required to click setup, confirm a target directory, maybe confirm a EULA, and then click Finish.
As to: "For laughs, I downloaded the latest version of Cygwin, ran the installer and immediately found myself asking, "now what", as I had to make decisions on choosing which packages to download. " …. " Click on that magic Cygwin icon and I get.. Wait for it. A command prompt."
Speaking of laughs, that sounds just like the jBase installation. DOH!
Look, I'm not going to play this game of fine-tuning words and splitting hairs on the nuances of specific implementations. People have enough information now to get more info. It's time to stop tossing fish and for people to use the fishing poles they have.
Have a nice day.
T
Kevin Powick
On Wednesday, 28 November 2012 20:01:04 UTC-5, NebulaTonyG wrote:
Look, I'm not going to play this game of fine-tuning words and splitting hairs on the nuances of specific implementations.
Simon
Coming a little late into the discussion.
I agree that CygWin is a little OTT and not straightforward for the job described.
A free solution, which is straightforward to install and works with a nice easy to use gui interface is freesshd - www.freesshd.com. I use it on Windows 2003 / jbase 3.4 but it's a generic solution - you create a user name/password combination and point it at your remote.cmd file. It then pretty much works like the jBASE telnet server...
Hope this helps
Simon
George R Smith
