From: Anibal David Acosta <anibal.acosta@edge.com.py>
To: 'Scott Marlowe' <scott.marlowe@gmail.com>
To: 'Timothy Madden' <terminatorul@gmail.com>
Cc: 'Joe Conway' <mail@joeconway.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Database level encryption
Date: Mon, 5 Apr 2010 17:55:23 -0300
Message-ID: <000b01cad502$52774700$f765d500$@net.py> (raw)
In-Reply-To: <v2ldcc563d11004051334ledfcd2b2gf8db60ca48b43118@mail.gmail.com>
References: <q2y5078d8af1004030635g624bf8f7r580cb3ebe7135b74@mail.gmail.com>
<4BB774D4.3070306@joeconway.com>
<m2r5078d8af1004051330n1874e532u3c88fd1bc31c8697@mail.gmail.com>
<v2ldcc563d11004051334ledfcd2b2gf8db60ca48b43118@mail.gmail.com>
TrueCrypt is a free open source application, can encrypt any drive or create
a virtual encrypted drive.
-----Mensaje original-----
De: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] En nombre de Scott Marlowe
Enviado el: lunes, 05 de abril de 2010 05:35 p.m.
Para: Timothy Madden
CC: Joe Conway; pgsql-admin@postgresql.org
Asunto: Re: [ADMIN] Database level encryption
On Mon, Apr 5, 2010 at 2:30 PM, Timothy Madden <terminatorul@gmail.com>
wrote:
> My scenario is how to protect the database if the machine is stolen
> (it is a mini-laptop), and
> I would like to encrypt the entire database, that is all columns of
> all tables, and if possible
> everything else found in the database.
>
> I would like all searching and sorting functions, just like with a
> normal database (that is,
> transparent encryption for the application level). The password will
> be entered by a human in
> order to start the application. The application exits after three
> unsuccessful attempts, but
> nothing prevents the user to start the application again; the number
> of failures is not counted.
> However if the database could count that I would not mind. I want a
> single password for
> data access to the entire database, there is only one database user
> involved anyway.
>
> I do not see the careful analysis required that you write about, I
> would say I am asking for
> SGBD support for database-level encryption.
Everything you've said so far points to using a mounted encrypted
drive to store the db. Windows and Linux both support this, and I'm
sure Mac does too. The fact that a different tool is needed for each
OS might be an issue. It's dirt simple to setup an encrypted drive on
linux where the user types in the passphrase on each boot. Some
laptops have wonky behaviour bringing up drives on USB at bootup tho
(I'm looking at a Dell that's sitting in the cube next to me that has
issues a BIOS update can't fix.)
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: anibal.acosta@edge.com.py, scott.marlowe@gmail.com, terminatorul@gmail.com, mail@joeconway.com
Subject: Re: Database level encryption
In-Reply-To: <000b01cad502$52774700$f765d500$@net.py>
* 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