From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Silvana Di Martino <silvanadimartino@tin.it>
Cc: Alex Page <alex.page@cancer.org.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: Database Encryption (now required by law in Italy)
Date: Fri, 5 Mar 2004 12:14:27 -0800 (PST)
Message-ID: <20040305120845.H92233@megazone.bigpanda.com> (raw)
In-Reply-To: <200403052024.38291.silvanadimartino@tin.it>
References: <200403050951.33230.silvanadimartino@tin.it>
<40488640.1040409@spacemonkeylabs.com>
<20040305151154.GC11311@halcyon.ox.icnet.uk>
<200403052024.38291.silvanadimartino@tin.it>
On Fri, 5 Mar 2004, Silvana Di Martino wrote:
> Alle 15:11, venerdì 5 marzo 2004, Alex Page ha scritto:
> > 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.
>
> Unfortunately, the new Italian law forces us to take seriously into account
> this catastrophic scenario and another one that is almost as worring: an
> unfaithful SysAdmin that copies your data and sells them to KGB. So, database
> encryption (and not disk encryption) is the _only_ answer.
But since your sysadmin (if not trusted) could go behind your back and
replace the database, any applications that are using the data, etc, I'm
not sure that's even sufficient.
> > 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 ;)
>
> The server should listen to the (encrypted/digitally signed) "Heartbeat" of a
> password server through the net to prevent this kind of attack.
That'll help prevent this sort of attack (although doesn't entirely unless
you can guarantee that the password server cannot be taken at the same
time) but also gives you a remote point of failure.
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: sszabo@megazone.bigpanda.com, silvanadimartino@tin.it, alex.page@cancer.org.uk
Subject: Re: Database Encryption (now required by law in Italy)
In-Reply-To: <20040305120845.H92233@megazone.bigpanda.com>
References: <200403050951.33230.silvanadimartino@tin.it> <40488640.1040409@spacemonkeylabs.com> <20040305151154.GC11311@halcyon.ox.icnet.uk> <200403052024.38291.silvanadimartino@tin.it> <20040305120845.H92233@megazone.bigpanda.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