Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: SmileUpps Features (Was: How do CouchApps fit into the CouchDB
 story? (Was: CouchDB Articles, Pills and Tutorials Ideas))
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: <5DF7EB60-B0DD-4CC6-8582-A0991A0AB5B5@b2w.com>
Date: Wed, 6 May 2015 11:51:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC124038-46D4-4FFC-B82F-EA520AF3819F@apache.org>
References: 
 <CAPMhwa5R6CdeQP-m_FHfqYsJ4NDwLYiePuwrsi2bRfzifncRpw@mail.gmail.com>
 <CAHw0XrtCxKWzM5x9Q2XjqxV3HOPLKCyOuTVOpMOeJKobJCzs5g@mail.gmail.com>
 <CAPMhwa7KTf4QTYm5HKyG2TxAzYPJ4a5CxAg90v8A26gY=W7poQ@mail.gmail.com>
 <CAHw0Xrt=1zvX9ud_Dezmks6jP10kPWMp08qXqO2ohO9yWCi2pw@mail.gmail.com>
 <CAPMhwa4XzFmPEdWRTdrtQW4x4thXcsCMe-OrJyA81OfL8DMTEQ@mail.gmail.com>
 <CAHw0XrtWiqQbQdaYoGGrjK2kGthJHeqTKg6K-EzzqfOe0rVycg@mail.gmail.com>
 <33BD4D82-787C-48D5-B963-FEEA4C0913CB@apache.org>
 <CADA9kr_7X6ha_hK3qb7N4FLDKeXCUQ7kDnYxN86Vzs_mRLKeCg@mail.gmail.com>
 <4209351E-F51E-4DB5-8A5F-8AB53DA21877@apache.org>
 <CAPMhwa4SeOJyj7618u_MvG1CredCm2J3a5p8pL9Lo7nCRjk3dQ@mail.gmail.com>
 <47CA7E1D-AC9D-42C3-9188-778265347F10@apache.org>
 <CAPMhwa7gjAXhGqY1S-snes7O_dMMWwoo0HiG-22qpbUus=zn_w@mail.gmail.com>
 <D328F540-26C0-468C-AE43-1489818B414A@apache.org>
 <CAPMhwa5LVA4X1yV+vOGDitnmBe4Nn+ErK5KpZBCqZhY=Qm41QA@mail.gmail.com>
 <5D665CF6-8E41-477F-BBE1-6EC7CDC534AA@apache.org>
 <CAPMhwa6BhY8a+UOxe1PCWxew3_2vVM8oU7uGQSDpCWT6
  Yusaqg@mail.gmail.com> <D2CB63FE-0457-4BC6-AC11-E2D42AFA325F@apache.org>
 <CAPMhwa7trQHvgYoxVP9S=ixpvkxwZxCm+-cYM4RO7FCm7tNbCw@mail.gmail.com>
 <5F87782C-54D0-4999-ADFD-2C07C71C24E7@apache.org>
 <CAPMhwa7B7TWY-aZ5t-fhqwca6CKeNxUBsgX51OgpxPdJGAS2RA@mail.gmail.com>
 <4E6DAC78-5234-4306-9F99-8AE3593E33C9@apache.org>
 <5DF7EB60-B0DD-4CC6-8582-A0991A0AB5B5@b2w.com>
To: marketing@couchdb.apache.org


> On 06 May 2015, at 07:49, Johs Ensby <johs@b2w.com> wrote:
>=20
> Jan and Giovanni,
> I am afraid I am dumbing down the discussion here (Giovanni, sorry for =
not studying your docs in detail yet), but isn=E2=80=99t this very =
basic?
> a vhost point all requests directly to the _rewrite that is used to =
manage security
> the _rewrite decides what to forward to the databases (with or without =
preset parameters in the rewrite rule)

When I send a request without a Host: header, then the vhost mechanism =
doesn=E2=80=99t kick in and I can access the full CouchDB server. There =
is no =E2=80=9Cdefault vhost=E2=80=9D setting in CouchDB.

Cloudant uses a different vhost system that I=E2=80=99m not familiar =
with.

Best
Jan
--


>=20
> I have used Cloudant for hosting, so my experience is based on the =
following setup procedure
> define vhost, point this to a _rewrite of a selected ddoc
> define access to each db based on where the traffic comes from, =
differentiate access levels by using more than one vhost, e.g. =
editor.mydomain.com <http://editor.domain.com/> and www.mydomain.com
> use one _rewrite as your API, strap it down as much as you want or
> use one _rewrite per access level (vhost)
> open up for rewrite to ../../../etc if you need to reach multiple dbs =
from same _rewrite
> create views for commonly requested subsets of data
> do the fine grade filtering in lists
>=20
> As for access control in the list (row by row) we have a =
req.userCtx.roles object with info coming from authenication via =
LlinkedIn to filter out data.
> There is a huge performance penalty for having to filter views in the =
list, of course, but the combination of views and filtering in a list =
serves a lot of purposes well as long as you think of your vhosts and =
_rewrites as your CouchApp API.
>=20
>=20
> Johs
>=20
>> On 05 May 2015, at 19:08, Jan Lehnardt <jan@apache.org> wrote:
>>=20
>>> I still haven't heard of a single path for exploit, but ok...
>>=20
>> I make a GET request to =
http://<ip-address>:<port>/database/_all_docs?include_docs=3Dtrue =
authenticated as one of your users, with your couchapp in it. In CouchDB =
parlance, I get all docs if I have access to the db. There is no way of =
making CouchDB only return =E2=80=9Cmy=E2=80=9D documents and not =
documents from other users. There is also no way of forcing me another =
route. What happens on your system?
>=20

--=20
Professional Support for Apache CouchDB:
http://www.neighbourhood.ie/couchdb-support/