cloudflare / cloudflare/tls-tris
Wrong trace, when handshake fails on client side
Open
- Dominant language
- Go
- Stars
- 300
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
On client side, when ``doTLS13Handshake`` fails because of server sending wrongly formatted key I get following error
```
handshake failed: local error: tls: bad record MAC
```
Message isn't correct
Contributor guide
Research direction
Start at the client-side doTLS13Handshake path and reproduce the failure with a server sending a wrongly formatted key. Trace where the bad record MAC error is selected, then make the reported error identify the handshake problem and verify it with a focused regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100