[new release] tls-mirage and tls (0.13.1) #18554
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CHANGES: * Breaking: use deriving sexp_of instead of sexp. Constructing a state from a sexp has not been supported (lead to exception), and is now removed (mirleft/ocaml-tls#430 by @torinnd, continued in mirleft/ocaml-tls#431 by @hannesm) * Bugfix: TLS 1.3 client authentication with certificate, client side. This used to work accidentally before 0.13.0 changed the signature algorithms handling, now the right signature algorithm (as requested by server) is used. (mirleft/ocaml-tls#431 @hannesm, @talex5 reported mirage/capnp-rpc#228) * adapt to x509 0.13.0 and mirage-crypto-ec 0.10.0 changes (mirleft/ocaml-tls#431 @hannesm)
hannesm
force-pushed
the
release-tls-0.13.1
branch
from
92dd592
to
e00d7b6
Compare
|
I re-released (force-pushed) to avoid the "missing function client_of_sexp" errors in conduit. |
|
failures look unrelated, good to be merged. |
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Transport Layer Security purely in OCaml, MirageOS layer
CHANGES:
a sexp has not been supported (lead to exception), and is now removed
(Use sexp_of ppx and remove unnecessary t_of_sexp stubs mirleft/ocaml-tls#430 by @torinnd, continued in updates for dependent APIs (mirage-crypto-ec, x509), fix client authentication mirleft/ocaml-tls#431 by @hannesm)
used to work accidentally before 0.13.0 changed the signature algorithms
handling, now the right signature algorithm (as requested by server) is used.
(updates for dependent APIs (mirage-crypto-ec, x509), fix client authentication mirleft/ocaml-tls#431 @hannesm, @talex5 reported Update to latest X509, TCP and TLS APIs mirage/capnp-rpc#228)