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.

Sign up for GitHub

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

Jump to bottom

Document why Tls.Engine.send_application_data is None #492

Merged

hannesm merged 1 commit into mirleft:main from reynir:send_application_data-ready

Apr 24, 2024

Contributor

reynir commented Apr 24, 2024

As discussed in https://github.com/robur-coop/miragevpn/pull/234/files/4f553471dc81e03790ead342caba5e50ac05fd71#r1576424941


          Document why send_application_data is None

61abc5a

hannesm merged commit 556033f into mirleft:main

1 check passed

Member

hannesm commented Apr 24, 2024

thanks!

reynir deleted the send_application_data-ready branch

April 25, 2024 11:35

hannesm mentioned this pull request

[new release] tls (5 packages) (0.17.5) ocaml/opam-repository#25870

Merged

raphael-proust pushed a commit to ocaml/opam-repository that referenced this pull request


          [new release] tls (5 packages) (0.17.5)

b711179

CHANGES:

* tls: documentation: clarify send_application_data (mirleft/ocaml-tls#492 @reynir)
* BUGFIX: tls: export_key_material was wrong for the server side on TLS 1.3,
  reported in robur-coop/miragevpn#181 by @reynir, fix in mirleft/ocaml-tls#495 @hannesm
* FEATURE: tls: add channel_binding (RFC 5929, RFC 9266) support (tls_unique,
  tls_exporter, tls_server_endpoint), requested by @Neustradamus in mirleft/ocaml-tls#484, added
  in mirleft/ocaml-tls#496 by @hannesm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment