On Jun 1, 2013 6:37 AM, "Jason Smith" wrote:
>
> Both methods have their own restrictions.
>
> When editing an .ini file, you *can* trivially set a password cyphertext
> (just paste it in), but you cannot set a password to literally
> "-pbkdf2-...". (You could calculate the hash yourself and then
On Sat, Jun 1, 2013 at 9:14 AM, Randall Leeds wrote:
> On Fri, May 31, 2013 at 4:30 PM, Jason Smith wrote:
> > Hi, Benoit.
> >
> > I did not put this in a branch since it was a single commit. I think I
> > missed that IRC meeting and did not realize the policy.
> >
> > My original implementation
On Fri, May 31, 2013 at 4:30 PM, Jason Smith wrote:
> Hi, Benoit.
>
> I did not put this in a branch since it was a single commit. I think I
> missed that IRC meeting and did not realize the policy.
>
> My original implementation assumed a "raw" update if the password had a
> "-pbkdf2-" prefix. Ye
Hi, Benoit.
I did not put this in a branch since it was a single commit. I think I
missed that IRC meeting and did not realize the policy.
My original implementation assumed a "raw" update if the password had a
"-pbkdf2-" prefix. Yes, that means people can no longer have a password of
literally "
So to be clear I don't understand why this patch landed in master
after the discussion we had on irc about it. Discussion was supposed
to continue on the ml...
Anyway I will repeat my argument against this ugly "raw" parameter. We
don't need it.
Actually we are checking if the password match an h
Why isn't it in a branch ? :/
On Fri, May 31, 2013 at 8:06 PM, wrote:
> Updated Branches:
> refs/heads/master f15f54d56 -> c98ba5612
>
>
> Allow storing a pre-hashed admin password
>
> When duplicating a couch, it is difficult to copy the _config/admins/*
> values. Storing the encoded value do
