pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Michael Fuhr <mike@fuhr.org>
Cc: Olivier Boissard <olivier.boissard@cerene.fr>
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: database encryption
Date: Thu, 8 Feb 2007 09:30:44 -0500 (EST)
Message-ID: <200702081430.l18EUis26889@momjian.us> (raw)
In-Reply-To: <20070208115221.GA76441@winnie.fuhr.org>

Michael Fuhr wrote:
> On Thu, Feb 08, 2007 at 09:13:48AM +0100, Olivier Boissard wrote:
> > I was thinking about a system in which only the php programs will be 
> > able to manage stored informations. In case of  theft or unexpected 
> > access to servers nobody could be able to retrieve the stored data 
> > without the authorized key.
> 
> What about theft or compromise of the server running the PHP code?
> In general it's a good idea to encrypt and decrypt as close to where
> the cleartext is needed to limit exposure, but you should also
> consider the vulnerability of the system that holds the key.  For
> some applications it might make sense to use public-key encryption
> with the exposed (e.g., Internet-facing) server having only the
> public (encryption) key and a more protected backend server having
> the corresponding private (decryption) key.
> 
> Without knowing the requirements and the threat model it's impossible
> to suggest a suitable solution.  Can you be more specific about what
> you're trying to do?

We do have an encryption section in our documentation:

	http://www.postgresql.org/docs/8.2/static/encryption-options.html


-- 
  Bruce Momjian  <bruce@momjian.us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +



view thread (10+ messages)  latest in thread

Message-ID: <200702081430.l18EUis26889@momjian.us>
Permalink:  ../200702081430.l18EUis26889@momjian.us/
Also on:    postgresql.org/message-id/200702081430.l18EUis26889@momjian.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: bruce@momjian.us, mike@fuhr.org, olivier.boissard@cerene.fr, ajs@crankycanuck.ca
  Subject: Re: database encryption
  In-Reply-To: <200702081430.l18EUis26889@momjian.us>
  References: <20070208115221.GA76441@winnie.fuhr.org> <200702081430.l18EUis26889@momjian.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