unexpected close of connection with compressed certificate
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
When a compressed certificate is used we send the following compressed certificate message:
struct {
CertificateCompressionAlgorithm algorithm;
uint24 uncompressed_length;
opaque compressed_certificate_message<1..2^24-1>;
} CompressedCertificate;
When we have a very big compressed_certificate_message (>1,000,000 bytes) OpenSSL closes the connection unexpectedly rather than sending a bad_certificate alert.
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 reproducing the compressed-certificate case with a compressed_certificate_message larger than 1,000,000 bytes, then trace OpenSSL's TLS certificate handling to find where the connection is closed. Done means the peer receives a bad_certificate alert instead of an unexpected connection close.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100