From: Josh <josh@saucetel.com>
To: pgsql-admin@postgresql.org
Subject: Securing a remotely accessible PostgreSQL server
Date: Wed, 22 Dec 2010 11:53:36 -0500
Message-ID: <4D122D10.7090805@saucetel.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: josh@saucetel.com
Subject: Re: Securing a remotely accessible PostgreSQL server
In-Reply-To: <4D122D10.7090805@saucetel.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox