strict KEX
Nobody has claimed this yet.
- Dominant language
- D
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
strict KEX (the Terrapin mitigation from CVE-2023-48795) is primarily relevant when chacha20-poly1305@openssh.com or the *-etm@openssh.com CBC modes are negotiated. Since we don't currently support those ciphers, the practical exposure is limited and this isn't blocking. Still worth implementing eventually for defense in depth and forward compatibility with peers that require it.
Contributor guide
No contributing guide indexed for this repository
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
The issue concerns strict KEX as a Terrapin mitigation for the SSH protocol and references CVE-2023-48795. Start by locating the repository's SSH key-exchange negotiation entry point and reviewing the relevant protocol guidance. Done means strict KEX is implemented for forward compatibility without requiring the currently unsupported cipher modes.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100