[
https://issues.apache.org/jira/browse/COUCHDB-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902735#comment-13902735
]
Robert Newson commented on COUCHDB-2066:
----------------------------------------
We can and should upgrade _user records on next authentication (when we have
the password) and not wait until the user changes their password. Upconverting
from the old scheme to the new one is a novel (and therefore almost certainly
broken) security algorithm, very much -1 on that.
As a further enhancement, we could allow a server config setting that refuses
users that only have password_sha on disk, and force them to change their
password.
> Don't allow stupid storage of passwords
> ---------------------------------------
>
> Key: COUCHDB-2066
> URL: https://issues.apache.org/jira/browse/COUCHDB-2066
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Isaac Z. Schlueter
>
> If a password_sha/salt combination is PUT into the _users db, wrap that up in
> PBKDF2.
> Discussion:
> https://twitter.com/janl/status/434818855626502144
> https://twitter.com/izs/status/434835388213899264
> https://twitter.com/janl/status/434835614790586368
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
