From user-return-18623-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Mon Oct 31 22:52:24 2011 Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 29A8E9B83 for ; Mon, 31 Oct 2011 22:52:24 +0000 (UTC) Received: (qmail 17024 invoked by uid 500); 31 Oct 2011 22:52:22 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 16985 invoked by uid 500); 31 Oct 2011 22:52:22 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 16977 invoked by uid 99); 31 Oct 2011 22:52:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Oct 2011 22:52:22 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jens@couchbase.com designates 206.225.164.29 as permitted sender) Received: from [206.225.164.29] (HELO EXHUB020-2.exch020.serverdata.net) (206.225.164.29) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Oct 2011 22:52:15 +0000 Received: from EXVMBX020-1.exch020.serverdata.net ([169.254.4.141]) by EXHUB020-2.exch020.serverdata.net ([206.225.164.29]) with mapi; Mon, 31 Oct 2011 15:51:52 -0700 From: Jens Alfke To: "user@couchdb.apache.org" Date: Mon, 31 Oct 2011 15:51:52 -0700 Subject: Re: Health care software utilizing CouchDB Thread-Topic: Health care software utilizing CouchDB Thread-Index: AcyYH66EjzTlAoYdSm6OLyGZ6Rvi5g== Message-ID: References: <4EAEF01F.6070902@thewordnerd.info> In-Reply-To: <4EAEF01F.6070902@thewordnerd.info> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_FA78B6613F8546E4B0DDE60321C6DCFBcouchbasecom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_FA78B6613F8546E4B0DDE60321C6DCFBcouchbasecom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable On Oct 31, 2011, at 11:59 AM, Nolan Darilek wrote: How do you handle data encryption? Or are you not US-based? You can encrypt the sensitive data, base64-encode the resulting blob and th= en put that into a property of a document. The disadvantage, of course, is that you can=92t index or filter based on t= his data because view functions can=92t read it. The only alternative I can think of is to encrypt the entire database file,= which would probably involve splicing into CouchDB at a low level to inser= t a block cipher into the file I/O code. =97Jens --_000_FA78B6613F8546E4B0DDE60321C6DCFBcouchbasecom_--