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 4CB47D1CC78 for ; Fri, 5 Mar 2004 19:28:26 +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 41422-06 for ; Fri, 5 Mar 2004 15:28:24 -0400 (AST) Received: from vsmtp3.tin.it (vsmtp3alice.tin.it [212.216.176.143]) by svr1.postgresql.org (Postfix) with ESMTP id EEB2DD1B906 for ; Fri, 5 Mar 2004 15:28:22 -0400 (AST) Received: from host91-33.pool8248.interbusiness.it (82.48.33.91) by vsmtp3.tin.it (7.0.019) (authenticated as silvanadimartino) id 402CD18F0041E6F5; Fri, 5 Mar 2004 20:28:21 +0100 From: Silvana Di Martino To: Radu-Adrian Popescu , pgsql-admin@postgresql.org Subject: Re: Database Encryption (now required by law in Italy) Date: Fri, 5 Mar 2004 19:27:11 +0000 User-Agent: KMail/1.5 References: <404864DD.6000207@aldratech.com> In-Reply-To: <404864DD.6000207@aldratech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200403051927.11026.silvanadimartino@tin.it> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/57 X-Sequence-Number: 12627 Alle 11:30, venerd=EC 5 marzo 2004, Radu-Adrian Popescu ha scritto: > We're basically doing it this way: generate a pair of private/public > keys and save these. > Then we get sensitive data in from some outside source, use it in the > processing part, > then we encrypt it using the public key (obviously) and store it in > the database. They > public key lives itself inside the database, because it presents no > security risk if exposed. > The private key lives on a separate machine in another physical > location. So no-one can > decrypt the data even if gaining access to the server machines. > Obviously this assumes > that we do not decrypt the data after using it... Which is something > rather hard to enforce, > depending on the application. > > If we do need to decrypt the data, we take the encrypted data to a > safe location, get the private key > securely and then decrypt and use the data. That is quite complicated. It looks like what we actually need is a system= =20 like Kerberos (devoted to data encryption "on the fly" instead of user=20 authentication). The logical schema of Kerberos fits well our model: a=20 third-party system authenticate and authorize whoever (process or human) th= at=20 have to access the data. Just the third party stores the private keys and u= se=20 them. All other parties just uses public keys. Unfortunately, just a community of crypto-specialists can implement such a= =20 mechanism. See you. ----------------------------------------- Alessandro Bottoni and Silvana Di Martino alessandrobottoni@interfree.it silvanadimartino@tin.it