Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 66096 invoked from network); 17 Aug 2009 23:37:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Aug 2009 23:37:29 -0000 Received: (qmail 17861 invoked by uid 500); 17 Aug 2009 23:37:47 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 17783 invoked by uid 500); 17 Aug 2009 23:37:47 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 17773 invoked by uid 99); 17 Aug 2009 23:37:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2009 23:37:47 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [76.96.27.212] (HELO QMTA14.emeryville.ca.mail.comcast.net) (76.96.27.212) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2009 23:37:37 +0000 Received: from OMTA05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by QMTA14.emeryville.ca.mail.comcast.net with comcast id VZBf1c00E0vp7WLAEbdH5X; Mon, 17 Aug 2009 23:37:17 +0000 Received: from [192.168.10.100] ([98.198.233.112]) by OMTA05.emeryville.ca.mail.comcast.net with comcast id VbdA1c0012SADaS8RbdCXk; Mon, 17 Aug 2009 23:37:14 +0000 Message-Id: <0C366699-9810-4738-BC93-EEF12C5C6674@apache.org> From: Curt Arnold To: dev@couchdb.apache.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Cryptography in CouchDB Date: Mon, 17 Aug 2009 18:37:08 -0500 X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org I don't know if it predates the recent OAuth patch, but I believe the CouchDB now requires an export notice to be filed. The export notification should have been filed before crypto related code was committed. I do not know if there is a procedure to follow when the export notice is not filed beforehand. See http://www.apache.org/dev/crypto.html and http://www.apache.org/licenses/exports/ It should have dawned on me earlier, but I stumbled upon it when I built Erlang R13B01 from source without previously installing libssl- dev. Erlang and CouchDB would build successfully, but CouchDB would fail on start up. Surprised me that CouchDB requires ssl to launch.