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 BD1D7D509 for ; Tue, 3 Jul 2012 15:54:09 +0000 (UTC) Received: (qmail 15573 invoked by uid 500); 3 Jul 2012 15:54:08 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 15541 invoked by uid 500); 3 Jul 2012 15:54:08 -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 15531 invoked by uid 99); 3 Jul 2012 15:54:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2012 15:54:08 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of albin.stigo@gmail.com designates 209.85.213.52 as permitted sender) Received: from [209.85.213.52] (HELO mail-yw0-f52.google.com) (209.85.213.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2012 15:54:00 +0000 Received: by yhpp61 with SMTP id p61so6763529yhp.11 for ; Tue, 03 Jul 2012 08:53:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=BKHRBrah+ReHKAI2DDsxqlzDNsrdpPIEzdnTUCUF2BU=; b=qRrFi9j/8+OOdZDycQRg9icKUL5nhb6T6fFDUPki8McRHxDpeGZ7q3Bahfph4yL6te 4tTTwMDotuX+Y2ocpbo1K06uwp0otQN+d3mTgJh7ebq+r0gUIL3lXIkRbwNbmRTo8gGL PzAH/zOVZEFREfKpY2Ov5P9dONPDS8QZ1VdFyr6aFazB3eUYy8NBrybg/JH3It3Y2lTK Jkl8Q02IIgNAyKSyJ7Z9JFFA6OidcIWKx65wVIoD94rMl8d6G08dSauIhXdF1GYL4eA+ d07tHd2Eg2j0gybWsp97k4bxq5bE/NdSAdW1uyznOJ9nmc91VWzkvdh+Q4HEubFIiCLq suCQ== MIME-Version: 1.0 Received: by 10.236.201.195 with SMTP id b43mr1411313yho.27.1341330819771; Tue, 03 Jul 2012 08:53:39 -0700 (PDT) Received: by 10.236.216.40 with HTTP; Tue, 3 Jul 2012 08:53:39 -0700 (PDT) Date: Tue, 3 Jul 2012 17:53:39 +0200 Message-ID: Subject: Cryptograhically signed docs... From: =?ISO-8859-1?Q?Albin_Stig=F6?= To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, Did anyone experiment with cryptographically signing docs as a method of "authentication"..? I was thinking something along these lines: Instead of using name/password login all posted docs must be signed with a private key. The server has a list of the public keys that are allowed to post. If the signature is not correct the validation function rejects the new/updated doc. I think this scheme could have many interesting use cases... It might also be a way of maintaining "ownership" across replication. Did anyone try this? --Albin