Setting ssl ciphers config does not work
- Dominant language
- Erlang
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 9
Description
## Description
If you uncomment ciphers or tls_versions for example in local.ini, starting couchdb fails. This could be something on my end, but I've been toying with this for a couple days with no luck. We have ssl working just fine, but are trying to restrict the ciphers to be used now.
## Steps to Reproduce
Uncomment the default ciphers config in local.ini. The http server will fail to start when starting couchdb. If you tweak from the default at all, you'll likely get an error that mochi had an issue parsing
## Expected Behaviour
[NOTE]: # ( Tell us what you expected to happen. )
## Your Environment
* CouchDB version used: 3.1.1
* Browser name and version:
* Operating system and version: CentOs7
tried several different erlang versions 20, 21, and 22 major versions
## Additional Context
[TIP]: # ( Add any other context about the problem here. )
Contributor guide
Research direction
Start with the ciphers and tls_versions settings in local.ini and reproduce the HTTP server startup failure on CouchDB 3.1.1 with the reported Erlang and CentOS 7 environment. Compare the default and modified values, including the Mochi parsing error, and consider the issue done when CouchDB starts while the configured TLS restrictions are accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- centos, erlang
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100