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

Improve ECC support in TLS 1.2 (RFC 8422) #424

Closed
wants to merge 1 commit into from

Conversation

hannesm
Copy link
Member

@hannesm hannesm commented Dec 7, 2020

The Go implementation of TLS dislikes client hello without a ECPointFormats
extension, so let's revert from #413 and re-add this extension with a single
value (uncompressed) to client hello (and server hello if client sent it, and
an ECC ciphersuite was selected).

In TLS 1.3 only settings, this change is a no-op.

The Go implementation of TLS dislikes client hello without a ECPointFormats
extension, so let's revert from mirleft#413 and re-add this extension with a single
value (uncompressed) to client hello (and server hello if client sent it, and
an ECC ciphersuite was selected).

In TLS 1.3 only settings, this change is a no-op.
@hannesm
Copy link
Member Author

hannesm commented Dec 8, 2020

merged manually

@hannesm hannesm closed this Dec 8, 2020
@hannesm hannesm deleted the ecc-go-tls-1-2 branch December 8, 2020 11:51
kit-ty-kate pushed a commit to ocaml/opam-repository that referenced this pull request Dec 8, 2020
CHANGES:

* Re-add ECPointFormats hello extension (both client and server) to avoid
  handshake failures with Go's TLS stack (RFC 8422 makes it optional, but go
  (1.15.5) requires it) - reported by @jeffa5 at
  https://discuss.ocaml.org/t/strange-prohibited-tls-1-2-cipher-suite-9d-issue/
  fix by @hannesm mirleft/ocaml-tls#424
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant