Making the DB secure - Mailing list pgsql-general

From Együd Csaba
Subject Making the DB secure
Date
Msg-id 0II800CK2BLUJL@mail.vnet.hu
Whole thread Raw
Responses Re: Making the DB secure  (Sean Davis <sdavis2@mail.nih.gov>)
Re: Making the DB secure  (Douglas McNaught <doug@mcnaught.org>)
Re: Making the DB secure  (Geoffrey <esoteric@3times25.net>)
Re: Making the DB secure  ("Karl O. Pinc" <kop@meme.com>)
Re: Making the DB secure  (hubert depesz lubaczewski <depesz@gmail.com>)
List pgsql-general
Hi,
we plan to make available our database from the internet (direct tcp/ip
based connections). We want to make it as secure as possible. There are a
few users who could access the database, but we want to block any other
users to access.

Our plans are:
  - using encripted (ssl) connections - since sensitive (medical) personal
information are stored.
    (How to setup this? What do we need on server side, and what on client
side?)
  - using pg_hba.conf to configure authentication method and IP filters
  - forcing our users to change their passwords frequently
  - applying strong password policy (long pw, containing upper/lowercase
characters and numbers)

Could anybody suggest us something more valuable features in postgres to
improve the security?
Regarding SSL, I'd like to know how to use it correctly. What we have to do
on the server to accept ssl connections, and what kind of client softwares
are required.

Many thanks,

-- Csaba Együd


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.7.7/20 - Release Date: 2005.06.16.




--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.7.7/20 - Release Date: 2005.06.16.


pgsql-general by date:

Previous
From: Jacob Atzen
Date:
Subject: Re: Backing up multiple databases
Next
From: Christopher Browne
Date:
Subject: Re: Backing up multiple databases