On Wednesday 12 December 2007 10:04:54 pm A. Kretschmer wrote:
> am Wed, dem 12.12.2007, um 10:11:21 -0800 mailte johnf folgendes:
> > > I would suggest a ssh-tunnel.
> > >
> > >
> > > Andreas
> >
> > I guess I don't know enough about ssh because I thought it allowed users
> > to run apps on my server?
>
> This is also possible.
>
> > How would I get a remote app that needs a connection
> > to the postgres server to use the ssh connection?
>
> 2 ways:
> - remote login and run the application remote (like psql)
> - Portforwarding, i explain:
> ssh <remote> -L:5432:<ip pg-server>:5432
>
> Read more:
> http://www.ssh.com/support/documentation/online/ssh/adminguide/32/Port_Forw
>arding.html
>
>
> Now the TCP-Port 5432 on your local System is forwarded to the
> PG-Server. You can use arbitrary application on your local host, it
> seems the database is running local on your host.
>
> The connection to the pg-server are encapsulated and encrypted through
> the ssh-connection. You don't need an open port on the remote side,
> except SSH. And your server can be in a LAN behind the gateway with
> a private address.
>
>
>
> Other solution, as Tom suggested, SSL.
>
>
> Andreas
Thanks this also looks like a possible solution. But what does the postgres
server see as an IP coming from the client (is it 127.0.0.1). IOW what/how
do I setup the pg_hba.conf to allow this connection?
--
John Fabiani