Re: secure ODBC connection

Your starting it at the wrong place.  You start the connection from the
machine you are connectiong from - not the database server.  Otherwise you
are setting up a secure tunnel withing the machine, instead of accross the
network!

Run the SSH command on the Windows client machine.

Regards,
Mathew

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org]On Behalf Of Mister ics
> Sent: Sunday, 16 September 2001 9:36 AM
> To: renfro@tntech.edu
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] secure ODBC connection
>
>
> 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@myserver.myorg.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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html