You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Oliver Schmidt <sp...@googlemail.com> on 2013/07/17 01:08:36 UTC

Is the CouchDB users database secure?

While reading the Kan.so docs ( 
http://kan.so/docs/The_users_database ) I saw 
that the users database, which includes 
username and password, is publicly accessible 
for everyone. Couldn't an attacker use this to 
create a list of all username-password pairs? 
Wouldn't it be more secure to use a server side 
function which validates the password without 
giving the users db directly to everyone? Or am I 
just too paranoid?

Regards

Re: Is the CouchDB users database secure?

Posted by Robert Newson <rn...@apache.org>.
Yes.

On 17 July 2013 00:35, Oliver Schmidt <sp...@googlemail.com> wrote:
> Am Mittwoch, 17. Juli 2013, 00:09:23 schrieb
> Robert Newson:
>> The _users database is not so open since
> our 1.2.0 release. A user can
>> only see their own document.
> And how does logging in work? Is there a
> server side component which checks
> whether the incoming password equals the
> hash in the database or not?

Re: Is the CouchDB users database secure?

Posted by Oliver Schmidt <sp...@googlemail.com>.
Am Mittwoch, 17. Juli 2013, 00:09:23 schrieb 
Robert Newson:
> The _users database is not so open since 
our 1.2.0 release. A user can
> only see their own document. 
And how does logging in work? Is there a 
server side component which checks 
whether the incoming password equals the 
hash in the database or not?

Re: Is the CouchDB users database secure?

Posted by Robert Newson <rn...@apache.org>.
The _users database is not so open since our 1.2.0 release. A user can
only see their own document. Even before this you could only see
password hashes, but we agreed even this was too much to show.

B.


On 17 July 2013 00:08, Oliver Schmidt <sp...@googlemail.com> wrote:
> While reading the Kan.so docs (
> http://kan.so/docs/The_users_database ) I saw
> that the users database, which includes
> username and password, is publicly accessible
> for everyone. Couldn't an attacker use this to
> create a list of all username-password pairs?
> Wouldn't it be more secure to use a server side
> function which validates the password without
> giving the users db directly to everyone? Or am I
> just too paranoid?
>
> Regards