cloudflare / cloudflare/tls-tris
TLS13-WrongOuterRecord test fails
- Dominant language
- Go
- Stars
- 300
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
The TLS13-WrongOuterRecord bogo test expects that clients that receive a handshake content type fail while tris just ignored it.
https://tools.ietf.org/html/draft-ietf-tls-tls13-18#section-5.2 says:
> opaque_type The outer opaque_type field of a TLSCiphertext record is
> always set to the value 23 (application_data) for outward
> compatibility with middleboxes accustomed to parsing previous
> versions of TLS. The actual content type of the record is found
> in TLSInnerPlaintext.type after decryption.
It has no MUST requirement on the receiver, so not sure if we should check it or not.
Contributor guide
Research direction
Start by running the TLS13-WrongOuterRecord bogo test and read the cited TLS 1.3 section 5.2. Determine whether tris should reject or ignore a received handshake content type, then align the implementation and test with the decided receiver behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100