Skip site navigation (1) Skip section navigation (2)

Re: secure ODBC connection

From: "Mister ics" <mister_ics(at)hotmail(dot)com>
To: renfro(at)tntech(dot)edu
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: secure ODBC connection
Date: 2001-09-16 09:36:02
Message-ID: F18pxGgcxHBQ634K01Q0000b063@hotmail.com (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi Mike,

I understand now... but i still have a problem on server side :-)

When i start the tunnel on back-end side:

ssh -N -L 3333:myserver.myorg.com:5432 relay(at)myserver(dot)myorg(dot)com

it starts to listen on port 3333 of the 127.0.0.1 host (lo). If i try to 
connect to myserver.myorg:3333 from the outside, the connection is refufed 
because the tunnel does not work on the network interface's address (es. 
192.168.0.1), but only on the lo interface.
How can i "export" that tunnel to the outside.

Thaks in advance,

Regards,
Silvio
>Doesn't matter. The whole point of ssh tunneling is to provide crypto
>for programs that wouldn't otherwise have it (certain pop, imap, http,
>whatever programs).
>
>As Matthew Frank pointed out, make an ssh tunnel from
>localhost:odbcport to odbchost:odpcport and point your ODBC client to
>localhost instead of odbchost.
>
>To try a simpler example, I've used putty's terminal app to tunnel
>localhost:9673 to a remote host's port 9673 (not for ODBC, but for web
>work). Pointed my web browser at localhost:9673 and up popped the
>remote web site. Secure as SSL, but without the cost.
>


_________________________________________________________________
Scarica GRATUITAMENTE MSN Explorer all'indirizzo 
http://explorer.msn.it/intl.asp


Responses

pgsql-odbc by date

Next:From: Mathew FrankDate: 2001-09-16 10:59:00
Subject: Re: secure ODBC connection
Previous:From: Dave PageDate: 2001-09-15 11:32:07
Subject: Re:

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group