You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Javier Candeira (JIRA)" <ji...@apache.org> on 2014/10/26 23:43:34 UTC
[jira] [Updated] (COUCHDB-2362) Have dev/run put the same cookie
secret and hashed admin password in all three nodes of dev cluster
[ https://issues.apache.org/jira/browse/COUCHDB-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Javier Candeira updated COUCHDB-2362:
-------------------------------------
Summary: Have dev/run put the same cookie secret and hashed admin password in all three nodes of dev cluster (was: Have dev/run put the correct user:password in the [admin] section of all three nodes in dev cluster)
> Have dev/run put the same cookie secret and hashed admin password in all three nodes of dev cluster
> ---------------------------------------------------------------------------------------------------
>
> Key: COUCHDB-2362
> URL: https://issues.apache.org/jira/browse/COUCHDB-2362
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: BigCouch
> Reporter: Javier Candeira
>
> When starting a dev cluster with the --admin option:
> `dev/run -a candeira:candeira`
> the local.ini scripts get rebuilt with an extra [admin] section and the plaintext user = password line. This means that couchdb adds the hashed password instead of replacing it.
> in addition, the admin party fix only sets the user = password line in one of the cluster's nodes, which may create problem.
> The forthcoming patch will initialise all three nodes with the same hashed password, as per rnewson:
> 00:27 <+rnewson> so you need to ensure that the admin is the same on all nodes after hashing
> 00:28 <+rnewson> otherwise cookies won't work if you hop between nodes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)