pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Page <alex.page@cancer.org.uk>
To: Mitch Pirtle <mitchy@spacemonkeylabs.com>
Subject: Re: Database Encryption (now required by law in Italy)
Date: Fri, 5 Mar 2004 15:11:54 +0000
Message-ID: <20040305151154.GC11311@halcyon.ox.icnet.uk> (raw)
In-Reply-To: <40488640.1040409@spacemonkeylabs.com>
References: <200403050951.33230.silvanadimartino@tin.it>
	<40484403.70001@aldratech.com>
	<200403051245.10681.silvanadimartino@tin.it>
	<20040305121254.GK13042@nemesis.ox.icnet.uk>
	<40488640.1040409@spacemonkeylabs.com>

On Fri, Mar 05, 2004 at 08:53:04AM -0500, Mitch Pirtle wrote:

> I understand (and demand) requiring SSL connections for database 
> clients, and MD5 hashing of passwords before storing in the database, 
> but implementing two-way encryption of database data just doesn't make 
> sense to me.

It all comes down to what you're trying to protect your data *from*. If
you're trying to protect it from people sniffing network traffic between
clients and the server, then SSL is sensible. If you're trying to
protect against somebody reading passwords out of a database and using
them to impersonate other users, use MD5 (or SHA) hashing.

If you're trying to protect against somebody taking down your server
room door with a sledgehammer, lifting your server out of the rack,
driving it away and booting off an alternative medium to avoid needing
to know your root password, then a loopback encrypted partition (or data
encrypted in GPG where the decryption key is not stored on the database
server) is a sensible precaution.

I expect that for most database users, it comes down to meeting the
standards defined by law rather than realistic expectations of an attack
- I expect that most of the situations we attempt to prevent are
unlikely in the extreme, but we have various contractual and legal
obligations which mean we have to defend against them anyway.

Of course, this loopback encryption with a boot-time passphrase may fail
if they take the rackmount UPS as *well*, and keep the machine powered
at all times ;)

Alex
-- 
Mail: Alex Page <alex.page@cancer.org.uk>
Real: Systems/Network Assistant, Epidemiology Unit, Oxford
Tel:  01865 302 223 (external) / 223 (internal)
PGP:  8868 21D7 3D35 DD77 9D06  BF0A 0746 2DE6 55EA 367E



view thread (65+ messages)  latest in thread

Message-ID: <20040305151154.GC11311@halcyon.ox.icnet.uk>
Permalink:  ../20040305151154.GC11311@halcyon.ox.icnet.uk/
Also on:    postgresql.org/message-id/20040305151154.GC11311@halcyon.ox.icnet.uk

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: alex.page@cancer.org.uk, mitchy@spacemonkeylabs.com
  Subject: Re: Database Encryption (now required by law in Italy)
  In-Reply-To: <20040305151154.GC11311@halcyon.ox.icnet.uk>
  References: <200403050951.33230.silvanadimartino@tin.it> <40484403.70001@aldratech.com> <200403051245.10681.silvanadimartino@tin.it> <20040305121254.GK13042@nemesis.ox.icnet.uk> <40488640.1040409@spacemonkeylabs.com> <20040305151154.GC11311@halcyon.ox.icnet.uk>

* 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