pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Grega Bremec <grega.bremec@noviforum.si>
To: pgsql-admin@postgresql.org
Subject: Re: Database Encryption (now required by law in Italy)
Date: Fri, 5 Mar 2004 16:52:16 +0100
Message-ID: <20040305155216.GA2228@elbereth.noviforum.si> (raw)
In-Reply-To: <20040305143150.GO13042@nemesis.ox.icnet.uk>
References: <20040305092041.GB13042@nemesis.ox.icnet.uk>
	<OAEAKHEHCMLBLIDGAFELIEKOEOAA.matt@ymogen.net>
	<20040305120802.GJ13042@nemesis.ox.icnet.uk>
	<20040305134753.GA1560@elbereth.noviforum.si>
	<20040305143150.GO13042@nemesis.ox.icnet.uk>

...and on Fri, Mar 05, 2004 at 02:31:50PM +0000, Dave Ewart used the keyboard:
> 
> I'm not sure I get your point, Grega - are you suggesting that using
> LoopAES is a good idea and that a system with LoopAES should also boot
> up automatically?
> 
> I don't understand that at all.  If it boots up automatically, then the
> encryption is effectively transparent and pointless.  All data on the
> disk is 'pre-decrypted', very conveniently for whoever has just stolen
> the server/disk.
> 
> If you're using LoopAES, it should *require* manual intervention, i.e.
> passphrase to be entered.  If you want the system to boot up
> automatically, using LoopAES is redundant and so should not be used.

Darn, you made me shorten my hefty post into ten lines. :-(
Just when I I was beginning to like it the way it was... :)

Mind, this is not only in reference to LoopAES.

All I'm saying is that good local security _can_ provide for lack of any
kind of interactive unlock procedure during boot in case the piece of
information required to un(b)lock access to encrypted media can be securely
stored and used by the boot loader in a non-revelatory manner, for example
by pushing the authentication process one step down. One example of that
would be a PSK-protecting boot loader (for boot arguments) and some sort
of key-encrypted boot loader config file.

That way, even if someone can boot the Damn Thing [tm], they can not log
into the system and access the protected data, nor do they have access to
information required to access unencrypted data (passphrases, keys, ...).

Cheers,
-- 
    Grega Bremec
    Senior Administrator
    Noviforum Ltd., Software & Media
    http://www.noviforum.si/

view thread (65+ messages)  latest in thread

Message-ID: <20040305155216.GA2228@elbereth.noviforum.si>
Permalink:  ../20040305155216.GA2228@elbereth.noviforum.si/
Also on:    postgresql.org/message-id/20040305155216.GA2228@elbereth.noviforum.si

 · 

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: grega.bremec@noviforum.si
  Subject: Re: Database Encryption (now required by law in Italy)
  In-Reply-To: <20040305155216.GA2228@elbereth.noviforum.si>
  References: <20040305092041.GB13042@nemesis.ox.icnet.uk> <OAEAKHEHCMLBLIDGAFELIEKOEOAA.matt@ymogen.net> <20040305120802.GJ13042@nemesis.ox.icnet.uk> <20040305134753.GA1560@elbereth.noviforum.si> <20040305143150.GO13042@nemesis.ox.icnet.uk> <20040305155216.GA2228@elbereth.noviforum.si>

* 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