Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 4964E2E3EC7 for ; Thu, 20 Dec 2007 16:52:35 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 87595-10 for ; Thu, 20 Dec 2007 16:52:32 -0400 (AST) Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id ABCCC2E3E7F for ; Thu, 20 Dec 2007 16:52:32 -0400 (AST) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=crankycanuck.ca) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1J5SNb-0001ms-RX for pgsql-performance@postgresql.org; Thu, 20 Dec 2007 15:52:31 -0500 Received: by crankycanuck.ca (Postfix, from userid 1000) id 7F5BD500AA; Thu, 20 Dec 2007 15:52:14 -0500 (EST) Date: Thu, 20 Dec 2007 15:52:14 -0500 From: Andrew Sullivan To: pgsql-performance@postgresql.org Subject: Re: viewing source code Message-ID: <20071220205214.GW4924@crankycanuck.ca> Mail-Followup-To: Andrew Sullivan , pgsql-performance@postgresql.org References: <1A6E6D554222284AB25ABE3229A92762112A33@nrtexcus702.int.asurion.com> <476A9ADF.5030101@commandprompt.com> <90bce5730712201047m4dd0fe05k6b1fccc57897326f@mail.gmail.com> <20071220114011.64a650d7@commandprompt.com> <20071220200739.GC11586@alvh.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/323 X-Sequence-Number: 28139 On Thu, Dec 20, 2007 at 03:35:42PM -0500, Merlin Moncure wrote: > > Key management is an issue but easily solved. Uber simple solution is > to create a designated table holding the key(s) and use classic > permissions to guard it. Any security expert worth the title would point and laugh at that suggestion. If the idea is that the contents have to be encrypted to protect them, then it is just not acceptable to have the encryption keys online. That's the sort of "security" that inevitably causes programs to get a reputation for ill-thought-out protections. A