0.15.5

CHANGES:

• tls-eio release only: fix end-of-file handling (#454 @talex5), avoid
  deprecation warnings (#454 @hannesm)

0.15.4

CHANGES:

• New package tls-eio (#451 @talex5)
• Tls_async: expose tls_handler (#448 @mbacarella, reviewed by @torinnd)

0.15.3

CHANGES:

• Upgrade to v0.15 of Jane Street packages (#444 @bcc32)
• Use cmdliner 1.1.0 in lwt/examples (#445 @hannesm)

0.15.2

CHANGES:

• Drop dependency on async_find (#442 @torinnd)

0.15.1

CHANGES:

• Tls_lwt: avoid exception if connect is executed with a non-host name string
  (e.g. an IP address) (#441 @hannesm)
• Bugfix: log a warning if certificate decoding fails (#441 @hannesm)
• Remove rresult dependency (#441 @hannesm)

0.15.0

CHANGES:

• Adapt to x509 0.15.0 changes (#440 @hannesm)

0.14.1

CHANGES:

• Bugfix: do not filter signature_algorithms based on server certificate. Since
  signature_algorithms is also used for client authentication (as
  SignatureAlgorithms extension in CertificateVerify), previously the client
  needed the same key type as the server.
  Discovered in robur-coop/albatross@df434da

0.14.0

CHANGES:

• Breaking: peer_name (in config and epoch data, also own_name) is now a
  [`host] Domain_name.t instead of a string. (#434 #438 @torinnd @hannesm)
• Add a X509_async module (#435 @torinnd)
• Client and server constructor log messages are on the debug level (#436
  reported by @talex5, fix by @hannesm)
• Adapt to cstruct 6.0.0 API (Cstruct.len is deprecated) #439 @hannesm

v0.13.2

CHANGES:

• New package tls-async that provides an effectful layer of TLS using async.
  (#432, @torinnd, @dinosaure, @kit-ty-kate, reviews by @hannesm @avsm @seliopou)

v0.13.1

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
  (#430 by @torinnd, continued in #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.
  (#431 @hannesm, @talex5 reported mirage/capnp-rpc#228)
• adapt to x509 0.13.0 and mirage-crypto-ec 0.10.0 changes (#431 @hannesm)