pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Silvana Di Martino <silvanadimartino@tin.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: Article on DB encryption
Date: Mon, 8 Mar 2004 14:19:23 -0500 (EST)
Message-ID: <200403081919.i28JJNn18271@candle.pha.pa.us> (raw)
In-Reply-To: <200403081020.21312.silvanadimartino@tin.it>

Silvana Di Martino wrote:
> And this one shows a feasible solution for PostgreSQL (using pgcrypto):
> 
> "Oracle has one of the best solutions for in-database encryption-decryption 
> keys. It stores the keys, encrypted, in a table. For users with access 
> rights, it decrypts the keys, which in turn decrypt the desired data. The 
> downside, of course, is that you have unencrypted data on the network, but 
> the benefit is making access to encrypted data secure. Not even the database 
> administrator can see the unencrypted data--even the keys to get at the data 
> are encrypted. This solution can be implemented in any of the major 
> databases, and Oracle provides a secure key generator as well as other tools 
> to get you started."

Interesting.  I can see how the client decrypts the stored password, but
I don't see how the server works with that decrypted password.  

I can see how the client could use it to decrypt data on their end, or
send the password as part of the query as an argument to a pg_crypto
function.

The user could decrypt it and store it in a temporary table, and join to
that table in queries, and pass that decrypted password column to
pg_crypto functions, but do we guarantee that that temp table would not
be on the disk if the server crashes and is then stolen?  Seems
server-side variables would be a natural, secure use for this that temp
tables don't supply.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (3+ messages)  latest in thread

Message-ID: <200403081919.i28JJNn18271@candle.pha.pa.us>
Permalink:  ../200403081919.i28JJNn18271@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200403081919.i28JJNn18271@candle.pha.pa.us

 · 

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: pgman@candle.pha.pa.us, silvanadimartino@tin.it
  Subject: Re: Article on DB encryption
  In-Reply-To: <200403081919.i28JJNn18271@candle.pha.pa.us>
  References: <200403081020.21312.silvanadimartino@tin.it> <200403081919.i28JJNn18271@candle.pha.pa.us>

* 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