[GitHub] couchdb-couch-epi pull request #20: Update README.md
GitHub user DeadZen opened a pull request: https://github.com/apache/couchdb-couch-epi/pull/20 Update README.md Fix a few typos and such You can merge this pull request into a Git repository by running: $ git pull https://github.com/DeadZen/couchdb-couch-epi patch-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-couch-epi/pull/20.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #20 commit 8f0c826d3e16967f5f442dd67223ebf803a9152c Author: Pedram NimreeziDate: 2016-08-30T05:50:09Z Update README.md Fix a few typos and such --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2299) admin users are unable to login after upgrading to 1.6.0 when older password hashes are used
[ https://issues.apache.org/jira/browse/COUCHDB-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446983#comment-15446983 ] ASF subversion and git services commented on COUCHDB-2299: -- Commit 5bfd43dd0e3681bdb39dbbe47b6e56105a599cef in couchdb-documentation's branch refs/heads/1.6.1 from [~dch] [ https://git-wip-us.apache.org/repos/asf?p=couchdb-documentation.git;h=5bfd43d ] docs: include release notes for improved handling of admin password hashing - closes COUCHDB-2298 - closes COUCHDB-2299 > admin users are unable to login after upgrading to 1.6.0 when older password > hashes are used > > > Key: COUCHDB-2299 > URL: https://issues.apache.org/jira/browse/COUCHDB-2299 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Affects Versions: 1.6.0 >Reporter: Dave Cottlehuber >Assignee: Dave Cottlehuber >Priority: Blocker > Fix For: 1.6.1 > > > # issue > When a couch is upgraded to 1.6.0, and the config files contain an [admins] > section with non-PBKDF2 hashed passwords (old-style < 1.3.1) then couchdb > will not let those admin users login. > # reproduce > - install 1.2.1 through 1.5.1 (tested those + 1.3.1 + 1.6.1-rc.3) > - create a new admin user via futon > - remove old binaries etc `rm -rf bin share lib` > - only dbs and .ini files remain (apart from log uri etc) > - install 1.6.0 (or 1-rc.3 with the fix for the raw/unhashed password fix) > - try to log in using admin via futon > {code} > 2> [debug] [<0.146.0>] 'POST' /_session {1,1} from "94.136.7.161" > Headers: [{'Accept',"application/json"}, > {'Accept-Encoding',"gzip,deflate"}, > {'Accept-Language',"en-US,en;q=0.8,de;q=0.6"}, > {'Connection',"keep-alive"}, > {'Content-Length',"25"}, > {'Content-Type',"application/x-www-form-urlencoded; charset=UTF-8"}, > {'Cookie',"AuthSession="}, > {"Dnt","1"}, > {'Host',"130.211.98.121:5984"}, > {"Origin","http://130.211.98.121:5984"}, > {'Referer',"http://130.211.98.121:5984/_utils/"}, > {'User-Agent',"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2129.0 Safari/537.36"}, > {"X-Requested-With","XMLHttpRequest"}] > [debug] [<0.146.0>] OAuth Params: [] > [debug] [<0.146.0>] Attempt Login: admin > [debug] [<0.117.0>] DDocProc found for DDocKey: {<<"_design/_auth">>, > > <<"2-7837bd4a550c1a65ac96c258e83d8b8c">>} > [debug] [<0.171.0>] OS Process #Port<0.3041> Input :: > ["reset",{"reduce_limit":true,"timeout":5000}] > [debug] [<0.171.0>] OS Process #Port<0.3041> Output :: true > [debug] [<0.171.0>] OS Process #Port<0.3041> Input :: > ["ddoc","_design/_auth", > ["validate_doc_update"], > [{"_id":"", > "password_scheme":"pbkdf2", > "iterations":10,"roles":["_admin"], > "salt":"a755d787383cdc147808a3ce2326479e", > "password_scheme":"simple", > "derived_key":"77bc076166db06fd940540ea7dc9d181e7e44741", > "_revisions":{"start":0,"ids":[]}}, > null, > {"db":"_users","name":null,"roles":["_admin"]},{}]] > [debug] [<0.171.0>] OS Process #Port<0.3041> Output :: {"forbidden":"doc.type > must be user"} > [debug] [<0.146.0>] Minor error in HTTP request: {forbidden, > <<"doc.type must be user">>} > [debug] [<0.146.0>] Stacktrace: [{couch_db,update_doc,4, > [{file,"couch_db.erl"},{line,432}]}, > {couch_httpd_auth, > '-maybe_upgrade_password_hash/3-fun-0-', > 4, > [{file,"couch_httpd_auth.erl"}, > {line,355}]}, > {couch_util,with_db,2, > [{file,"couch_util.erl"},{line,443}]}, > {couch_httpd_auth,handle_session_req,1, > [{file,"couch_httpd_auth.erl"}, > {line,275}]}, > {couch_httpd,handle_request_int,5, > [{file,"couch_httpd.erl"},{line,318}]}, > {mochiweb_http,headers,5, > [{file,"mochiweb_http.erl"},{line,94}]}, > {proc_lib,init_p_do_apply,3, > [{file,"proc_lib.erl"},{line,227}]}] > [info] [<0.146.0>] 94.136.7.161 - - POST /_session 403 > {code} -- This message was sent by
[jira] [Commented] (COUCHDB-2298) 1.6.0 crashes on startup if plain (non-hashed) admins are present in .ini / config files
[ https://issues.apache.org/jira/browse/COUCHDB-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446982#comment-15446982 ] ASF subversion and git services commented on COUCHDB-2298: -- Commit 5bfd43dd0e3681bdb39dbbe47b6e56105a599cef in couchdb-documentation's branch refs/heads/1.6.1 from [~dch] [ https://git-wip-us.apache.org/repos/asf?p=couchdb-documentation.git;h=5bfd43d ] docs: include release notes for improved handling of admin password hashing - closes COUCHDB-2298 - closes COUCHDB-2299 > 1.6.0 crashes on startup if plain (non-hashed) admins are present in .ini / > config files > > > Key: COUCHDB-2298 > URL: https://issues.apache.org/jira/browse/COUCHDB-2298 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Database Core >Reporter: Dave Cottlehuber >Assignee: Dave Cottlehuber > Fix For: 1.6.1 > > > If a couchdb install is managed via e.g. chef or similar, and the admin > passwords are pushed as plaintext, couchdb will crash on startup. > {code} > 1> Apache CouchDB 1.6.0 (LogLevel=info) is starting. > {"init terminating in do_boot",{{badmatch,{error,{bad_return, > {{couch_app,start,[normal,["/ramdisk/couch/etc/couchdb/default.ini","/ramdisk/couch/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1,[{file,"couch_server_sup.erl"},{line,98}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,274}]}]}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}} > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2298) 1.6.0 crashes on startup if plain (non-hashed) admins are present in .ini / config files
[ https://issues.apache.org/jira/browse/COUCHDB-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446985#comment-15446985 ] ASF subversion and git services commented on COUCHDB-2298: -- Commit 5bfd43dd0e3681bdb39dbbe47b6e56105a599cef in couchdb-documentation's branch refs/heads/1.6.x from [~dch] [ https://git-wip-us.apache.org/repos/asf?p=couchdb-documentation.git;h=5bfd43d ] docs: include release notes for improved handling of admin password hashing - closes COUCHDB-2298 - closes COUCHDB-2299 > 1.6.0 crashes on startup if plain (non-hashed) admins are present in .ini / > config files > > > Key: COUCHDB-2298 > URL: https://issues.apache.org/jira/browse/COUCHDB-2298 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Database Core >Reporter: Dave Cottlehuber >Assignee: Dave Cottlehuber > Fix For: 1.6.1 > > > If a couchdb install is managed via e.g. chef or similar, and the admin > passwords are pushed as plaintext, couchdb will crash on startup. > {code} > 1> Apache CouchDB 1.6.0 (LogLevel=info) is starting. > {"init terminating in do_boot",{{badmatch,{error,{bad_return, > {{couch_app,start,[normal,["/ramdisk/couch/etc/couchdb/default.ini","/ramdisk/couch/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1,[{file,"couch_server_sup.erl"},{line,98}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,274}]}]}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}} > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2299) admin users are unable to login after upgrading to 1.6.0 when older password hashes are used
[ https://issues.apache.org/jira/browse/COUCHDB-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446986#comment-15446986 ] ASF subversion and git services commented on COUCHDB-2299: -- Commit 5bfd43dd0e3681bdb39dbbe47b6e56105a599cef in couchdb-documentation's branch refs/heads/1.6.x from [~dch] [ https://git-wip-us.apache.org/repos/asf?p=couchdb-documentation.git;h=5bfd43d ] docs: include release notes for improved handling of admin password hashing - closes COUCHDB-2298 - closes COUCHDB-2299 > admin users are unable to login after upgrading to 1.6.0 when older password > hashes are used > > > Key: COUCHDB-2299 > URL: https://issues.apache.org/jira/browse/COUCHDB-2299 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Affects Versions: 1.6.0 >Reporter: Dave Cottlehuber >Assignee: Dave Cottlehuber >Priority: Blocker > Fix For: 1.6.1 > > > # issue > When a couch is upgraded to 1.6.0, and the config files contain an [admins] > section with non-PBKDF2 hashed passwords (old-style < 1.3.1) then couchdb > will not let those admin users login. > # reproduce > - install 1.2.1 through 1.5.1 (tested those + 1.3.1 + 1.6.1-rc.3) > - create a new admin user via futon > - remove old binaries etc `rm -rf bin share lib` > - only dbs and .ini files remain (apart from log uri etc) > - install 1.6.0 (or 1-rc.3 with the fix for the raw/unhashed password fix) > - try to log in using admin via futon > {code} > 2> [debug] [<0.146.0>] 'POST' /_session {1,1} from "94.136.7.161" > Headers: [{'Accept',"application/json"}, > {'Accept-Encoding',"gzip,deflate"}, > {'Accept-Language',"en-US,en;q=0.8,de;q=0.6"}, > {'Connection',"keep-alive"}, > {'Content-Length',"25"}, > {'Content-Type',"application/x-www-form-urlencoded; charset=UTF-8"}, > {'Cookie',"AuthSession="}, > {"Dnt","1"}, > {'Host',"130.211.98.121:5984"}, > {"Origin","http://130.211.98.121:5984"}, > {'Referer',"http://130.211.98.121:5984/_utils/"}, > {'User-Agent',"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2129.0 Safari/537.36"}, > {"X-Requested-With","XMLHttpRequest"}] > [debug] [<0.146.0>] OAuth Params: [] > [debug] [<0.146.0>] Attempt Login: admin > [debug] [<0.117.0>] DDocProc found for DDocKey: {<<"_design/_auth">>, > > <<"2-7837bd4a550c1a65ac96c258e83d8b8c">>} > [debug] [<0.171.0>] OS Process #Port<0.3041> Input :: > ["reset",{"reduce_limit":true,"timeout":5000}] > [debug] [<0.171.0>] OS Process #Port<0.3041> Output :: true > [debug] [<0.171.0>] OS Process #Port<0.3041> Input :: > ["ddoc","_design/_auth", > ["validate_doc_update"], > [{"_id":"", > "password_scheme":"pbkdf2", > "iterations":10,"roles":["_admin"], > "salt":"a755d787383cdc147808a3ce2326479e", > "password_scheme":"simple", > "derived_key":"77bc076166db06fd940540ea7dc9d181e7e44741", > "_revisions":{"start":0,"ids":[]}}, > null, > {"db":"_users","name":null,"roles":["_admin"]},{}]] > [debug] [<0.171.0>] OS Process #Port<0.3041> Output :: {"forbidden":"doc.type > must be user"} > [debug] [<0.146.0>] Minor error in HTTP request: {forbidden, > <<"doc.type must be user">>} > [debug] [<0.146.0>] Stacktrace: [{couch_db,update_doc,4, > [{file,"couch_db.erl"},{line,432}]}, > {couch_httpd_auth, > '-maybe_upgrade_password_hash/3-fun-0-', > 4, > [{file,"couch_httpd_auth.erl"}, > {line,355}]}, > {couch_util,with_db,2, > [{file,"couch_util.erl"},{line,443}]}, > {couch_httpd_auth,handle_session_req,1, > [{file,"couch_httpd_auth.erl"}, > {line,275}]}, > {couch_httpd,handle_request_int,5, > [{file,"couch_httpd.erl"},{line,318}]}, > {mochiweb_http,headers,5, > [{file,"mochiweb_http.erl"},{line,94}]}, > {proc_lib,init_p_do_apply,3, > [{file,"proc_lib.erl"},{line,227}]}] > [info] [<0.146.0>] 94.136.7.161 - - POST /_session 403 > {code} -- This message was sent by
[jira] [Commented] (COUCHDB-3111) Default replicator change feed timeout too short
[ https://issues.apache.org/jira/browse/COUCHDB-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446957#comment-15446957 ] Nick Vatamaniuc commented on COUCHDB-3111: -- For reference here is an example of a change feed request : {code} GET /rdyno_001/_changes?filter=rdyno_filterdoc%2Frdyno_filtername=continuous=all_docs=%22334-g1IieJyV0MENgjAUgOGnmKAnR9AJjG2RlpPcHENbHg0SxJNn3UQ30U10EyzUBAkhgTRpk7b_d3gZAEwTB2GenzEmIaF8tTaLZOZhLEEtiqJIE0e6J3PhKqEiLfz2905CLc2utj8FKoUTuqGaIswuOcb6mMfY3Ydlv2_0WiqfR9ivP5T9tdFLznxNvF59PjE73MxhiHttIGFCoxhgPKzxrA0aKCLQH2C8rPH-nwX1Auw3S2t8rFHOQwGMdhXDNPOQYztMv-12jrg%22=1 {code} > Default replicator change feed timeout too short > > > Key: COUCHDB-3111 > URL: https://issues.apache.org/jira/browse/COUCHDB-3111 > Project: CouchDB > Issue Type: Improvement >Reporter: Nick Vatamaniuc > > Current replicator change feeds are set up to timeout based on default > connection_timeout parameter divided by 3. Default connection timeout is > 3 (msec). So replicator change feeds are torn down and established again > every 10 seconds. > That doesn't seem bad on a smaller scale but if there are 1000 replications > jobs on a server it would means tearing down change feed connections every 10 > msec. It seems like it might not be optimal so wanted to discuss it. > Looking at the commit which introduced 'div 3' behavior wondering if there is > anything to improve here: > https://github.com/apache/couchdb-couch-replicator/commit/ed447f8c01880c7f99f5829a8ef485fd8d399376 > Maybe keep div 3 but increase default connection timeout to 60 seconds? Or > maybe apply div 2 - 5 seconds, or have a minimum of 30 seconds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-3111) Default replicator change feed timeout too short
Nick Vatamaniuc created COUCHDB-3111: Summary: Default replicator change feed timeout too short Key: COUCHDB-3111 URL: https://issues.apache.org/jira/browse/COUCHDB-3111 Project: CouchDB Issue Type: Improvement Reporter: Nick Vatamaniuc Current replicator change feeds are set up to timeout based on default connection_timeout parameter divided by 3. Default connection timeout is 3 (msec). So replicator change feeds are torn down and established again every 10 seconds. That doesn't seem bad on a smaller scale but if there are 1000 replications jobs on a server it would means tearing down change feed connections every 10 msec. It seems like it might not be optimal so wanted to discuss it. Looking at the commit which introduced 'div 3' behavior wondering if there is anything to improve here: https://github.com/apache/couchdb-couch-replicator/commit/ed447f8c01880c7f99f5829a8ef485fd8d399376 Maybe keep div 3 but increase default connection timeout to 60 seconds? Or maybe apply div 2 - 5 seconds, or have a minimum of 30 seconds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-fauxton pull request #766: fix: typos and dash-style
GitHub user janl opened a pull request: https://github.com/apache/couchdb-fauxton/pull/766 fix: typos and dash-style You can merge this pull request into a Git repository by running: $ git pull https://github.com/janl/couchdb-fauxton typos Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/766.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #766 commit 700557539dc752b5fa6384b67b44cac256a0104c Author: Jan LehnardtDate: 2016-08-29T19:55:15Z fix: typos and dash-style --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (COUCHDB-3110) Fauxton: Update Visual Guide with new logo
Jan Lehnardt created COUCHDB-3110: - Summary: Fauxton: Update Visual Guide with new logo Key: COUCHDB-3110 URL: https://issues.apache.org/jira/browse/COUCHDB-3110 Project: CouchDB Issue Type: Bug Components: Fauxton Reporter: Jan Lehnardt https://couchdb.apache.org/fauxton-visual-guide/index.html shows the old logo -- This message was sent by Atlassian JIRA (v6.3.4#6332)