pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Silvana Di Martino <silvanadimartino@tin.it>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
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 21:39:49 +0000
Message-ID: <200403052137.51384.silvanadimartino@tin.it> (raw)
In-Reply-To: <20040305120845.H92233@megazone.bigpanda.com>
References: <200403050951.33230.silvanadimartino@tin.it>
	<200403052024.38291.silvanadimartino@tin.it>
	<20040305120845.H92233@megazone.bigpanda.com>

Alle 20:14, venerdì 5 marzo 2004, Stephan Szabo ha scritto:
> > 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.

Replacing the RDBMS engine and/or the "client" application, would be useless: 
the "cracker" still need the password to access the encrypted data.

> > > 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.

Right.

See you

-----------------------------------------
Alessandro Bottoni and Silvana Di Martino
alessandrobottoni@interfree.it
silvanadimartino@tin.it



view thread (65+ messages)  latest in thread

Message-ID: <200403052137.51384.silvanadimartino@tin.it>
Permalink:  ../200403052137.51384.silvanadimartino@tin.it/
Also on:    postgresql.org/message-id/200403052137.51384.silvanadimartino@tin.it

 · 

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: silvanadimartino@tin.it, sszabo@megazone.bigpanda.com, alex.page@cancer.org.uk
  Subject: Re: Database Encryption (now required by law in Italy)
  In-Reply-To: <200403052137.51384.silvanadimartino@tin.it>
  References: <200403050951.33230.silvanadimartino@tin.it> <200403052024.38291.silvanadimartino@tin.it> <20040305120845.H92233@megazone.bigpanda.com> <200403052137.51384.silvanadimartino@tin.it>

* 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