Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 67138 invoked from network); 23 May 2010 10:11:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 May 2010 10:11:06 -0000 Received: (qmail 1531 invoked by uid 500); 23 May 2010 10:11:05 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 1299 invoked by uid 500); 23 May 2010 10:11:04 -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 1291 invoked by uid 99); 23 May 2010 10:11:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 May 2010 10:11:04 +0000 X-ASF-Spam-Status: No, hits=3.6 required=10.0 tests=FREEMAIL_FROM,FS_REPLICA,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tom.sante@gmail.com designates 74.125.82.180 as permitted sender) Received: from [74.125.82.180] (HELO mail-wy0-f180.google.com) (74.125.82.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 May 2010 10:10:55 +0000 Received: by wyi11 with SMTP id 11so1732167wyi.11 for ; Sun, 23 May 2010 03:10:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=bYYBWIpjQjmehECbEScHL7p6nh0YTrV9U3HY8cW7KG0=; b=bgLJ4U2KYe0q4H0r/CYFZ8WFRd9Jh2gMHV3CYSDU/Ki+0/QJZEwgiK0JBMVXnu/c5/ QE5YXU8H/i+w/E8N93oj5+pcMNTCGpbizV+9yIBafCeZv63nI8uCqJk4OE8JJsMIMI6b ft3I2kzWU8kP6iSvrZif8Gm1ZST2m7wG0Wg0M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=HbvdonrC89CbIXc1YNizWL8+OHdIq5CJpnAu/hJaPZr8x7pMmxdr52+33aDB4VoJiN iGC4xi+Cyj/8Mc7L5Mj7k5YPPPItiUlp6cgOY/5GO2wqUgldm6B/Xx+q64mVnYyBWp3K itYCQAi/w8FgoetWGw8GZijJBDRKT362rhgtw= Received: by 10.216.158.65 with SMTP id p43mr2199686wek.50.1274609378019; Sun, 23 May 2010 03:09:38 -0700 (PDT) Received: from pb.local ([91.182.47.84]) by mx.google.com with ESMTPS id x6sm7458262gvf.27.2010.05.23.03.09.36 (version=SSLv3 cipher=RC4-MD5); Sun, 23 May 2010 03:09:36 -0700 (PDT) Message-ID: <4BF8FEDD.3000002@gmail.com> Date: Sun, 23 May 2010 12:09:33 +0200 From: Tom Sante User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.2.4) Gecko/20100519 Lanikai/3.1pre MIME-Version: 1.0 To: user@couchdb.apache.org Subject: Re: Replication Security References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 19/05/10 14:43, Norberto Fernandes FCS wrote: > Hi All, > > > Does anyone know the protocol or security layer used by couchDB to replicate data? > Is data being published from one database to the other over a security layer? or is it a simple http post? > > Thanks, > Norberto Replication is with HTTP, like almost everything else in couchDB. To do a secure replication between 2 servers I use a local port that tunnels all HTTP requests via ssh to the remote couchDB server.