From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | P Kapat <kap4lin(at)gmail(dot)com> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Incomplete online documentation on conecting via ssh tunnels |
Date: | 2008-11-20 08:26:39 |
Message-ID: | 49251F3F.7080300@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
P Kapat wrote:
> The relevant documentations are (replace 8.3 by 8.2 or 8.1 or...):
> http://www.postgresql.org/docs/8.3/static/ssh-tunnels.html
>
> The concerned command is:
> client$ ssh -L 3333:foo.com:5432 joe(at)foo(dot)com
>
>>From the discussion on the novice list, I came to the conclusion that
> the above command works only when listen_addresses = '*' OR
> listen_addresses = 'a.b.c.d'
> (where a.b.c.d is the IP of foo.com; other IPs can be present too) is
> set in postgresql.conf.
>
> But in most cases, for security reason, the server is quarantined
> within localhost by setting: listen_addresses = 'localhost'.
>
> In this case, the ssh tunnel does not work. The correct command is:
> client$ ssh -L 3333:localhost:5432 joe(at)foo(dot)com
> OR
> client$ ssh -L 3333:127.0.0.1:5432 joe(at)foo(dot)com
You are absolutely correct. Someone already pointed this out
independently, and the 8.4devel documentation has much better
information on this:
http://developer.postgresql.org/pgdocs/postgres/ssh-tunnels.html
From | Date | Subject | |
---|---|---|---|
Next Message | P Kapat | 2008-11-21 05:26:39 | Re: Incomplete online documentation on conecting via ssh tunnels |
Previous Message | P Kapat | 2008-11-20 00:31:06 | Incomplete online documentation on conecting via ssh tunnels |