X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C484BD1CA50 for ; Mon, 8 Mar 2004 21:46:13 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 28958-03 for ; Mon, 8 Mar 2004 17:46:02 -0400 (AST) Received: from vsmtp1.tin.it (vsmtp1alice.tin.it [212.216.176.141]) by svr1.postgresql.org (Postfix) with ESMTP id 7C686D1C95E for ; Mon, 8 Mar 2004 17:46:00 -0400 (AST) Received: from host20-33.pool8248.interbusiness.it (82.48.33.20) by vsmtp1.tin.it (7.0.019) (authenticated as silvanadimartino) id 4034BCBF0037CA63; Mon, 8 Mar 2004 22:45:49 +0100 From: Silvana Di Martino To: Joe Conway Subject: Re: Database Encryption (now required by law in Italy) Date: Mon, 8 Mar 2004 22:43:37 +0000 User-Agent: KMail/1.5 Cc: Peter Galbavy , pgsql-admin@postgresql.org References: <0A5B2E3C3A64CA4AB14F76DBCA76DDA44E2DA6@seifur.hnit.is> <200403081226.10550.silvanadimartino@tin.it> <404CAD5D.6010503@joeconway.com> In-Reply-To: <404CAD5D.6010503@joeconway.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200403082219.06167.silvanadimartino@tin.it> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/136 X-Sequence-Number: 12705 Alle 17:29, luned=EC 8 marzo 2004, Joe Conway ha scritto: > Silvana Di Martino wrote: > > Oracle has a built-in feature for encrypting/decrypting this password's > > password. > > Right, and this master password is only protected because Oracle is > closed source. It is not possible to do the same thing with Postgres > because you could find the master key (or the algorithm to produce it) > in the source code. > > However this amounts to "security by obscurity", and anyone serious > about encryption will tell you it is insufficient. There is no way to > have cryptographically sound protection of your data using a key > embedded in the software like that. Right. I completely agree. The only way to implement such a mechanism in a= =20 open source product is to keep the password away from the RDBMS host. See m= y=20 previous messages for a plausible scenario. See you ----------------------------------------- Alessandro Bottoni and Silvana Di Martino alessandrobottoni@interfree.it silvanadimartino@tin.it