Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 8EFDF6350BD for ; Wed, 7 Apr 2010 09:09:58 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 95212-05-5 for ; Wed, 7 Apr 2010 12:09:38 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mail.postgresql.org (Postfix) with ESMTP id 60226635257 for ; Wed, 7 Apr 2010 09:05:36 -0300 (ADT) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NzU0h-0002P7-B9 for pgsql-admin@postgresql.org; Wed, 07 Apr 2010 14:05:31 +0200 Received: from g224125059.adsl.alicedsl.de ([92.224.125.59]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Apr 2010 14:05:31 +0200 Received: from tim by g224125059.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Apr 2010 14:05:31 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: pgsql-admin@postgresql.org To: pgsql-admin@postgresql.org From: Tim Landscheidt Subject: Re: Database level encryption Date: Wed, 07 Apr 2010 12:05:13 +0000 Organization: Lines: 14 Message-ID: References: <4BB774D4.3070306@joeconway.com> <4BBA05E80200002500030493@gw.wicourts.gov> <4BBA6924.5050305@joeconway.com> <4BBB009102000025000304D3@gw.wicourts.gov> <4BBB6A49020000250003052B@gw.wicourts.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: g224125059.adsl.alicedsl.de Mail-Copies-To: never User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:NwP9vmgx9thp8i+KZ7TyQ8KCLiA= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.715 tagged_above=-10 required=5 tests=AWL=-0.716, BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 201004/63 X-Sequence-Number: 34157 Timothy Madden wrote: > [...] > User authentication should be unrelated to encrypting the database > owned by that user. You can think of it as if only the owner can ever > connect to such a database, and his/her password is the encryption > key, or as if any user that wishes to connect should provide the > encryption key first, and then the user name and password. As you seem not to need any of PostgreSQL's features, why not use SQLite? It seems perfect for your application as far as you stated it. Tim