Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CA+4wGE7iYVYa6hu0=WQ6OmZ--iWBwgs-8YXF+HOThgTnJN4v9g@mail.gmail.com>
References: 
 <CA+4wGE53FS065CNJrGsYFqtVu6g0EGPYN5A8OoCKv0DFEOCPAg@mail.gmail.com>
 <CAAL6JQh05ABk6iR5PT1uCvE3FSM_eZNvxfm7g3viDG_ZrXUdXg@mail.gmail.com>
 <CA+4wGE7c4EMvnzx2GPoeDz9twccKtheB21Hq7BucY3f7egS6Ew@mail.gmail.com>
 <CAN-3CB+MZFDnqy-VTJThqu0D5bv5GvQ=OT=xPTp467gZycj2Uw@mail.gmail.com>
 <CA+4wGE7iYVYa6hu0=WQ6OmZ--iWBwgs-8YXF+HOThgTnJN4v9g@mail.gmail.com>
From: Jason Smith <jhs@iriscouch.com>
Date: Tue, 15 Nov 2011 07:57:49 +0000
Message-ID: 
 <CAN-3CBJf=ZfERLxBZoVVaX5kF9-Ro5qYO26jVhkS=CpM=yXhPg@mail.gmail.com>
Subject: Re: Why MD5 is used for hashes, also about non-deterministic IDs.
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

On Tue, Nov 15, 2011 at 7:34 AM, Alex Besogonov
<alex.besogonov@gmail.com> wrote:
>>> Now I make a change to 'Doc' at machine A. This creates a new revid
>>> with new md5 hash.
>>> A malicious software somehow learns about this update and creates
>>> another document
>>> on machine B, contriving it so to make the resulting hash to be the
>>> same as on machine A.
>> Before going any further, you must show why we care about the contents
>> of machine B.
>> Why would I log in to machine B if I do not trust B's owner? Why would
>> I clone your Git repository if I do not know you?
> The problem is, MD5 hash depends on _untrusted_ data that external
> processes might put into the database.
>
> For example, imagine that machines A and B use CouchDB to store
> certificates.

I ask again.

-- 
Iris Couch