Securing a remotely accessible PostgreSQL server

From: Josh <josh(at)saucetel(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Securing a remotely accessible PostgreSQL server
Date: 2010-12-22 16:53:36
Message-ID: 4D122D10.7090805@saucetel.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi All,
I am looking for suggestions on how best to secure a server that is
accessible via the internet. Even account creation for the database is
open to the world. Does anybody have any extra changes they would make
to postgresql.conf or OS changes they would suggest? Perhaps some
default permissions that would be best revoked?

The system setup is currently a Linux box running PostgreSQL 8.4
My pg_hba.conf already limits remote connections to one database and one
particular role.

I have been a bit hesitant to post this in the past as I believed many
would just give the answer of "Don't". Please just humor me and give
suggestions assuming it is the only way. Consider it a fun challenge.

Thanks for your help,
Josh

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Snoop 2010-12-22 19:49:17 Re: PostgreSQL in Shared Disk Failover mode on FreeBSD+CARP+RAIDZ
Previous Message Tom Lane 2010-12-22 15:23:27 Re: Optimizing Update with WHERE x IN (id1,id2,...)