Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of kxepal@gmail.com designates
 74.125.82.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAN-3CBJ7b_32Apx7Hk_GJgFTz49mc1LDN_i6TXTDEgnS=scM1g@mail.gmail.com>
References: 
 <CAN-3CBJ7b_32Apx7Hk_GJgFTz49mc1LDN_i6TXTDEgnS=scM1g@mail.gmail.com>
Date: Mon, 25 Mar 2013 08:14:21 +0400
Message-ID: 
 <CAHdjipKeLgtGVuQCXEYThiUq4SL8bUn-z+Jjo6Y1Jr9vcmFbuw@mail.gmail.com>
Subject: Re: Input validation and limits
From: Alexander Shorin <kxepal@gmail.com>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi Jason!

On Mon, Mar 25, 2013 at 7:22 AM, Jason Smith <jhs@apache.org> wrote:
> ## reCAPTCHA support
> ...
> ## Rate limiting

Wouldn't these things break bulk updates and replications? Both of
them triggers vdu much and let them fail on half way just because they
hit update rate wouldn't be nice.

P.S. Currently, these questions could be solved via nginx in front of
CouchDB + fail2ban. May be better to integrate with existed tools? For
example, providing auth.log with authentication successful and failure
attempts - fail2ban will be happy for this. Currently you have to live
with verbose logs (or configure per-module logging, thanks to Jan!)
which looks a bit overhead if you're interested only in auth problems.

--
,,,^..^,,,