From: Silvana Di Martino <silvanadimartino@tin.it>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pgcrypto and database encryption
Date: Mon, 8 Mar 2004 08:10:44 +0000
Message-ID: <200403080810.44226.silvanadimartino@tin.it> (raw)
In-Reply-To: <20040307091719.P46697@megazone.bigpanda.com>
References: <200403071613.03397.silvanadimartino@tin.it>
<20040307091719.P46697@megazone.bigpanda.com>
Alle 17:40, domenica 7 marzo 2004, Stephan Szabo ha scritto:
> Who has access to the unencrypted versions of the data? Are there people
> who will have access to the database who might have access to some of the
> encrypted data but not all or someone who has access to the database but
> none of the encrypted data? If so, then you presumably need a system
> where the decryption will only work for the appropriate people and that
> needs to be built in.
Yes: each "authorized operator" must be able to access data belonging to him,
only, even if the database contains data belonging to many different
operators. Moreover, SysAdmin (that are not "authorized operator") must not
be able to access any data, even if they are able to access the database (as
a whole) for maintenance. So, decryption must work for authorized operator
only.
> Also, what manipulation do you want to do with these values in the
> database? Are you going to need to subtract two encrypted dates or
> determine that one is greater than the other?
Yes: we will need to perform basic operations on encrypted dates, times and so
on. Of course, it would be great to be able to delegate the on-the-fly
decryption/encryption work to the encryption system.
> What about substring or
> ordering for encrypted strings? Does this have to be automatic or is
> explicit description of the fact that you want to decrypt them and then do
> something sufficient?
Same as above: we would need to perform substring-wise operations and ordering
on encrypted strings. The encryption/decryption mechanism should be
automatic.
>
> Finally, there are some questions about reliability of the system as a
> whole. In a system like the -pw above, where do those passwords come from,
> is it from a human typing at a console? If so, you need to consider
> downtime and recovery time issues based on who has access to the
> passwords. This doesn't so much affect the law in question but it may
> affect contracts that you have if they have downtime requirements.
The password should come from a human typing at the console (not our choice:
law imposes it). Downtime will be affected: this is out of our control and
must be accepted by our customers.
Thanks for your comments.
-----------------------------------------
Alessandro Bottoni and Silvana Di Martino
alessandrobottoni@interfree.it
silvanadimartino@tin.it
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
Subject: Re: pgcrypto and database encryption
In-Reply-To: <200403080810.44226.silvanadimartino@tin.it>
References: <200403071613.03397.silvanadimartino@tin.it> <20040307091719.P46697@megazone.bigpanda.com> <200403080810.44226.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