[new release] mirage-crypto, mirage-crypto-rng, mirage-crypto-rng-mirage, mirage-crypto-rng-lwt, mirage-crypto-rng-eio, mirage-crypto-rng-async, mirage-crypto-pk and mirage-crypto-ec (0.11.0)

[hannesm]

Simple symmetric cryptography for the modern age

• Project page: https://github.com/mirage/mirage-crypto
• Documentation: https://mirage.github.io/mirage-crypto/doc

CHANGES:

• BREAKING split mirage-crypto-rng-lwt away from mirage-crypto-rng (split mirage-crypto-rng into mirage-crypto-rng and mirage-crypto-rng-lwt mirage/mirage-crypto#168
  @hannesm, reported by @bikallem Split sub libraries in mirage-crypto-rng into individual packages mirage/mirage-crypto#158)
  This means, a "mirage-crypto-rng.lwt" should now be "mirage-crypto-rng-lwt"
  in your dune file (or in META requires, or in _tags).
• AEAD API improvements: provide tag_size, of_secret, and functions that deal
  with the tag separately (mirage-crypto: improve AEAD API, provide tag_size and of_secret mirage/mirage-crypto#171 @hannesm, fixes AEAD interface improvements mirage/mirage-crypto#74 Question: Exposing the tag in AES-GCM mirage/mirage-crypto#144 @orbitz @anmonteiro)
  Only CCM16 (with tag size 16) is now exposed, the former API does not exist
  anymore (passing ~maclen to of_secret), according to sherlocode the only
  usage was CCM16 anyways
  This means any "Mirage_crypto.AES.CCM" should now be "Mirage_crypto.AES.CCM16"
  and any "CCM.of_secret ~maclen:16 key" should now be "CCM16.of_secret key"
  Any occurrence of "Mirage_crypto.Cipher_block.S.CCM" should now be
  "Mirage_crypto.Cipher_block.S.CCM16"
• BREAKING unify RNG initialization (reported by @talex5 in mirage-crypto-rng-eio: Eio backend of mirage-crypto-rng mirage/mirage-crypto#155, fixes RNG initialization inconsistencies mirage/mirage-crypto#160,
  PR [API change] rng: unify API for initialize, as reported in #160 mirage/mirage-crypto#162 @hannesm)
  This means:
  • "Mirage_crypto_rng_lwt.initialize ()" should now be
    "Mirage_crypto_rng_lwt.initialize (module Mirage_crypto_rng.Fortuna)"
  • "Mirage_crypto_rng_unix.initialize ()" should now be
    "Mirage_crypto_rng_unix.initialize (module Mirage_crypto_rng.Fortuna)"
• remove mirage 3 cross-compilation runes (remove mirage3 cross-compilation runes mirage/mirage-crypto#163 @hannesm)
• CI: mirage-crypto-rng-eio requires ocaml 5 and dune 2.7 (mirage-crypto-rng-eio: require ocaml 5, and dune 2.7 mirage/mirage-crypto#170 @hannesm, fixes
  mirage-crypto-rng-eio questions mirage/mirage-crypto#169 thanks to @bikallem @talex5)
• CI: use miage 4 (Ci use mirage4 mirage/mirage-crypto#166 @hannesm)

[hannesm]

Reverse dependencies have been addressed in #23238 #23239 #23240 #23242:

• x509 with-test Mirage_crypto_rng_unix.initialize API change (see test: use mirage-crypto-rng 0.11.0 API mirleft/ocaml-x509#162)
• tls: Mirage_crypto_rng_lwt is now in a separate package (mirage-crypto-rng-lwt), API for initialize changed, CCM API changed (see update to mirage-crypto 0.11, split tls-lwt away mirleft/ocaml-tls#468)
• awa: Mirage_crypto_rng_unix.initialize API change (see update to mirage-crypto-rng 0.11.0 API mirage/awa-ssh#49)
• certify: Mirage_crypto_rng_unix.initialize API change //cc @yomimono
• chamelon/chamelon-unix with-test: Mirage_crypto_rng_lwt is now part of mirage-crypto-rng-lwt package, also it's API changed //cc @yomimono
• conex-mirage-crypto: API of Mirage_crypto_rng_unix.initialize changed //cc @hannesm snapshot and timestamp support hannesm/conex#22
• current_web: API of Mirage_crypto_rng_unix.initialize changed /cc @talex5 current_web: update to mirage-crypto-rng 0.11.0 API changes ocurrent/ocurrent#408
• dirsp-proscript-mirage: Mirage_crypto_rng_lwt is now part of mirage-crypto-rng-lwt package (+ it's API changed) /cc @jonahbeckford update to mirage-crypto-rng 0.11 API changes diskuv/dirsp-exchange#1
• dns*: Mirage_crypto_rng_unix.initialize API change, split dns-client opam package into three: dns-client, dns-client-lwt, dns-client-mirage mirage/ocaml-dns#331
• dream / hyper: Mirage_crypto_rng_lwt is now part of mirage-crypto-rng-lwt package //cc ??
• jose API of Mirage_crypto_rng_unix.initialize changed /cc @ulrikstrid
• letsencrypt: API of Mirage_crypto_rng_unix.initialize changed /cc @hannesm robur-coop/ocaml-letsencrypt@dffa394
• rfc6287: API of Mirage_crypto_rng_unix.initialize changed /cc @sg2342 Update dependencies sg2342/ocaml-rfc6287#14
• mirage-block-ccm: API of Mirage_crypto.AES.CCM changed //cc @sg2342 Adapt to mirage-crypto 0.11 API changes sg2342/mirage-block-ccm#30
• ssh-agent API of Mirage_crypto_rng_unix.initialize changed /cc @reynir Update to mirage-crypto-rng.0.11.0 reynir/ocaml-ssh-agent#18
• twostep: API of Mirage_crypto_rng_unix.initialize changed /cc @marcoonroad update to mirage-crypto-rng 0.11 API changes marcoonroad/twostep#4
• spoke update to mirage-crypto 0.11.0 API dinosaure/spoke#3

[hannesm]

Please see the CHANGES above (or in the tarball / repository) for a brief guide of the RNG initialization API changes.

[hannesm]

now that #23297 is merged, I rebased on master, and this should be good to be merged. The remaining CI failures were unrelated (http errors, timeout in the solver, ...). See https://opam-ci.ci3.ocamllabs.io/github/ocaml/opam-repository/commit/5cfaa49d060d3f326128f6c8b2ab181a7416ba78 for the old CI run :)

To me it looks like, this can be directly merged. But if you prefer to wait for CI, that's fine with me as well.