Update to OpenSSL 3.0 for TLS 1.3 support
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Chef server currently still relies on the rather ancient OpenSSL version 1.0.2 which is EOL, and lacks TLS 1.3 support and a bunch of new ciphers/algos.
There was an initiative in the past which was closed due to FIPS concerns #2348 but its 4 years later now, and the situation is unchanged.
The chef-infra-client is already on OpenSSL 3.0 but unfortunately the server isn't, and is serving old protocols, weak ciphers and doesn't support HTTP/2.
Related issues:
#3679
#2349
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the prior FIPS-related initiative in #2348 and the related issues #3679 and #2349 to understand the unresolved constraints. The work is complete when Chef Server no longer depends on OpenSSL 1.0.2 and supports TLS 1.3, newer ciphers and algorithms, and HTTP/2 without regressing FIPS requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100