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 6B19CD1B9AF for ; Mon, 8 Mar 2004 11:09:16 +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 62440-05 for ; Mon, 8 Mar 2004 07:09:16 -0400 (AST) Received: from vsmtp3.tin.it (vsmtp3alice.tin.it [212.216.176.143]) by svr1.postgresql.org (Postfix) with ESMTP id 6A867D1B979 for ; Mon, 8 Mar 2004 07:09:13 -0400 (AST) Received: from host191-33.pool8248.interbusiness.it (82.48.33.191) by vsmtp3.tin.it (7.0.019) (authenticated as silvanadimartino) id 402CD18F00473B0D for pgsql-admin@postgresql.org; Mon, 8 Mar 2004 12:09:13 +0100 From: Silvana Di Martino To: pgsql-admin@postgresql.org Subject: Article on DB encryption Date: Mon, 8 Mar 2004 12:07:52 +0000 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200403081020.21312.silvanadimartino@tin.it> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/119 X-Sequence-Number: 12688 For the (very few?) people interested in this topic: "Time is Right for Database Encryption" Dec 9, 2003 | By Don MacVittie Published on NetworkComputing (www.nwc.com) http://www.nwc.com/shared/article/printFullArticle.jhtml;jsessionid=REGYCTEZ5MNJQQSNDBGCKHY?articleID=16401578 This paragraph, in particular, deals with a most-argued topic: "This is why client applications should decrypt the data after they receive it from the database. That's the most secure place to handle encryption and decryption. But changing all your client applications usually isn't realistic. If you find that modifying your apps is not an option, look for a solution that allows for decryption on the database and protection of your data while on the network. Using SSL to communicate with your database will protect your data while it traverses the LAN. It's simple to implement, especially since you probably already use it for transmitting sensitive information over the Internet." 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." Have a nice reading. ----------------------------------------- Alessandro Bottoni and Silvana Di Martino alessandrobottoni@interfree.it silvanadimartino@tin.it