Simple way of doing this with almost anything, is to use SSH
- Install SSH on the DB machine
- Install an SSH client on Windows (lots of GUI versions, but there is a
command line one that comes with Cywin.)
- Using the SSH client, log onto the db machine, and forward the db port to
a port on localhost.
Using ssh.exe from cygwin like this:
C:\>ssh -L 80:192.168.0.254:80 -l root -T 192.168.0.254
stdin: is not a tty
'dumb': unknown terminal type.
Waiting for forwarded connections to terminate...
The following connections are open:
#0 listen port 80 for 192.168.0.254 port 80, connect from 127.0.0.1 port
(t4 r1 i1/0 o16/0 fd 4/4)
The above example forwards port 80 to localhost port 80, and specifies that
no actual terminal session be started on the server you've logged onto
(forward port only)
- Setup you programs on the windows machine to connect to localhost via ODBC
ps - I use Win2k, and have not found an SSH client by default
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org]On Behalf Of Mister ics
> Sent: Thursday, 13 September 2001 1:39 PM
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] secure ODBC connection
> <<Sorry for partially O.T. >>
> is there a way to tunnel a win'98 ODBC connection into a ssh connection ?
> Tunnelling a TCP/IP connection in a ssh stream is a good and
> simple way to
> obtain acceptable levels of security in client-server applications.
> Unfortunately i've not found a way to do it on Win'95-98 boxes.
> I heared ssh tunnelling is supported at o.s.-level in win2000.
In response to
pgsql-odbc by date
|Next:||From: hero||Date: 2001-09-14 04:27:29|
|Subject: pgAdmin II /odbc connect errors|
|Previous:||From: Mister ics||Date: 2001-09-13 22:37:26|
|Subject: Re: secure ODBC connection|