Re: help running pgAdmin in debian -lenny

From: Erwin Brandstetter <brsaweda(at)gmail(dot)com>
To: pgadmin-support(at)postgresql(dot)org
Subject: Re: help running pgAdmin in debian -lenny
Date: 2011-02-24 14:57:29
Message-ID: 371f8b74-ec1b-454b-ace9-9a366b095278@n11g2000vbm.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Feb 20, 11:51 pm, guilla(dot)(dot)(dot)(at)lelarge(dot)info (Guillaume Lelarge) wrote:
(...)
> If you are on the same network, just allow your computer to access the
> database server with the pg_hba.conf file.
>
> Otherwise, you can use an SSH tunnel.

Details to the above suggestion for internet connections (also for
future reference):
Under Linux you can just use ssh on the command line. Something like:
ssh my_server_ip_here -Nf -L5433:my_server_ip_here:5432
For help try
man ssh

Under Windows, one good way is to use puTTY:
http://www.chiark.greenend.org.uk/~sgtatham/putty/
Example on how to open an SSH tunnel using port forwarding with puTTY:
http://www.cs.uu.nl/technical/services/ssh/putty/puttyfw.html

As an alternative to an SSH tunnel you can allow access from the
internet on your DB server. You should know your way around security,
though! If in doubt consult:
http://www.postgresql.org/docs/9.0/interactive/runtime-config-connection.html

For this, you need to allow connections from the internet in
postgresql.conf:
listen_addresses = '*'

I would advise to restrict internet connections to SSL. Also i would
only enable known IP adress(es) of the client(s). So you would add a
line like this to your pg_hba.conf:
# Access for John Doe from home
hostssl all myuser insert_client_ip_here/32 md5

Be sure not to allow unwanted connections from the internet.

Regards
Erwin

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Basil Bourque 2011-02-25 01:38:15 Re: Bug - Rows in Query Output pane fail to grow in height when font size preference size is larger
Previous Message Guillaume Lelarge 2011-02-23 23:02:24 Re: "Invalid byte sequence" message