SSLKEYLOGFILE support for ECH
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
After testing curl with OpenSSL's new ECH support I found that OpenSSL doesn't write out the ECH_CONFIG and ECH_SECRET values needed for tools like Wireshark.
It would obviously be nice if OpenSSL supported this so enabling ECH doesn't come at the cost of being able to inspect the traffic. :)
The ietf-tls-keylogfile document has been updated as of rev 3. to document the values needed: https://datatracker.ietf.org/doc/draft-ietf-tls-keylogfile/
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 reading the referenced ietf-tls-keylogfile draft revision 3 and tracing OpenSSL's existing SSLKEYLOGFILE handling for ECH. Done means OpenSSL emits the ECH_CONFIG and ECH_SECRET values required by tools such as Wireshark when ECH is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100