Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of myalphabetfamily@gmail.com
 designates 74.125.82.50 as permitted sender)
MIME-Version: 1.0
Date: Fri, 21 Feb 2014 07:42:55 -0700
Message-ID: 
 <CAK1z4PUznWh9z4h8zKQf=+pSq++p-nu=DqNiZ7MJj9cw6C9ENQ@mail.gmail.com>
Subject: CouchDB security
From: Ben Johnson <myalphabetfamily@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=047d7b86d6be24f6bc04f2eba385

--047d7b86d6be24f6bc04f2eba385
Content-Type: text/plain; charset=ISO-8859-1

Hello,
  Thanks in advance for your humoring me on a few questions.  I am new to
this and learning.  I read through the CouchDB guide on security and had a
few followup questions.

I am posting information to my CouchDB from a browser.  I will put a few
precautions and validations for the data in the browser but because of
nature of the project users will not be required to log in.  I am wondering
without a log in, how secure should I feel about my database and someone
overtaking it?  Has someone done this with success?  Can all of the data in
the database be viewed and or modified from someone using curl and my
servers address? Anything else that I should of thought about?  The data is
not sensitive but I still want to preserve its integrity.

Thanks,
Ben

--047d7b86d6be24f6bc04f2eba385--