Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proposal: crypto/tls: RFC 7685 support (ClientHello "padding(21)") #39271

Open
MarkOtzen opened this issue May 27, 2020 · 1 comment
Open

proposal: crypto/tls: RFC 7685 support (ClientHello "padding(21)") #39271

MarkOtzen opened this issue May 27, 2020 · 1 comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Proposal Proposal-Crypto Proposal related to crypto packages or other security issues
Milestone

Comments

@MarkOtzen
Copy link

MarkOtzen commented May 27, 2020

Unfortunately, there are TLS servers that refuse (and hang upon) ClientHello messages of sizes in the range 256-512 bytes, causing TLS handshake timeouts. RFC 7685 lets clients mitigate this by adding padding bytes to the ClientHello messages, so clients can adjust the ClientHello sizes at will as a workaround.

https://tools.ietf.org/html/rfc7685#section-1 reads:

Successive TLS [RFC5246] versions have added support for more cipher
suites and, over time, more TLS extensions have been defined. This
has caused the size of the TLS ClientHello to grow, and the
additional size has caused some implementation bugs to come to light.
At least one of these implementation bugs can be ameliorated by
making the ClientHello even larger. This is desirable given that
fully comprehensive patching of affected implementations is difficult
to achieve.
This memo describes a TLS extension that can be used to pad a
ClientHello to a desired size in order to avoid implementation bugs
caused by certain ClientHello sizes.

And here's a description of a buggy server implementation:
https://mailarchive.ietf.org/arch/msg/tls/8wXwhM1d5WSmROHFSgrTyFmWN2o/

Adding support for this extension would let users workaround these buggy server implementations.

@andybons andybons changed the title crypto/tls: RFC 7685 support (ClientHello "padding(21)") proposal: crypto/tls: RFC 7685 support (ClientHello "padding(21)") May 27, 2020
@gopherbot gopherbot added this to the Proposal milestone May 27, 2020
@andybons andybons added Proposal-Crypto Proposal related to crypto packages or other security issues and removed Proposal labels May 27, 2020
@andybons andybons added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 27, 2020
@andybons
Copy link
Member

andybons commented May 27, 2020

@FiloSottile @katiehockman

@ianlancetaylor ianlancetaylor added this to Incoming in Proposals (old) Jan 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Proposal Proposal-Crypto Proposal related to crypto packages or other security issues
Projects
Status: Incoming
Development

No branches or pull requests

3 participants