Date: Tue, 13 Jul 2004 15:18:38 +0200
From: Daniel Struck <struck.d@retrovirology.lu>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Sarah Tanembaum <sarahtanembaum@yahoo.com>,
	pgsql-php@postgresql.org, pgsql-admin@postgresql.org,
	pgsql-hackers-win32@postgresql.org, pgadmin-support@postgresql.org,
	pgsql-sql@postgresql.org
Subject: Re: [PHP] Secure DB Systems - How to
Message-Id: <20040713151838.0004cb8e@localhost>
In-Reply-To: <20040713123817.GB3710@wolff.to>
References: <ccjra4$pgl$1@sea.gmane.org> <20040709152722.GA20935@wolff.to>
	<20040713113557.31e9d6dc@localhost>
	<20040713123817.GB3710@wolff.to>
Organization: gwia.inf.chl.lu
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

> If you decrypt the data on the database, the sysadmin can see it.

Hm, you are right. If one does decrypt the data on the database you have to=
 sent the password to postgresql and so a administrator of the database cou=
ld easily grasb the password.

So the only way to go, would be to perform en/decryption on the client side?


> If you are willing to take that chance (e.g. if you primary concern is
> some third party getting a snapshot of the DB), then you can do lots of
> things.

I wonder now; if somebody could achieve to get a snapshot of the database, =
they could also be able to get the log-file of postgresql.
So one would also have to make attention that the information like sql stat=
ements don't leak that way.
Are there other places where this kind of information could leak?


Greetings,

Daniel Struck

--=20
Retrovirology Laboratory Luxembourg
Centre Hospitalier de Luxembourg
4, rue E. Barbl=E9
L-1210 Luxembourg

phone: +352-44116105
fax:   +352-44116113
web: http://www.retrovirology.lu
e-mail: struck.d@retrovirology.lu