[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) #23282
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
|
Reverse dependencies have been addressed in #23238 #23239 #23240 #23242:
|
|
Please see the CHANGES above (or in the tarball / repository) for a brief guide of the RNG initialization API changes. |
hannesm
force-pushed
the
release-mirage-crypto-v0.11.0
branch
from
9e87ae3
to
5cfaa49
Compare
…age, mirage-crypto-rng-lwt, mirage-crypto-rng-eio, mirage-crypto-rng-async, mirage-crypto-pk and mirage-crypto-ec (0.11.0) CHANGES: - BREAKING split mirage-crypto-rng-lwt away from mirage-crypto-rng (mirage/mirage-crypto#168 @hannesm, reported by @bikallem 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/mirage-crypto#171 @hannesm, fixes mirage/mirage-crypto#74 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/mirage-crypto#155, fixes mirage/mirage-crypto#160, PR 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 (mirage/mirage-crypto#163 @hannesm) - CI: mirage-crypto-rng-eio requires ocaml 5 and dune 2.7 (mirage/mirage-crypto#170 @hannesm, fixes mirage/mirage-crypto#169 thanks to @bikallem @talex5) - CI: use miage 4 (mirage/mirage-crypto#166 @hannesm)
hannesm
force-pushed
the
release-mirage-crypto-v0.11.0
branch
from
5cfaa49
to
5857120
Compare
|
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. |
This was referenced Feb 23, 2023
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.
Simple symmetric cryptography for the modern age
CHANGES:
@hannesm, reported by @bikallem Split sub libraries in
mirage-crypto-rnginto 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).
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
~maclentoof_secret), according to sherlocode the onlyusage 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"
PR [API change] rng: unify API for initialize, as reported in #160 mirage/mirage-crypto#162 @hannesm)
This means:
"Mirage_crypto_rng_lwt.initialize (module Mirage_crypto_rng.Fortuna)"
"Mirage_crypto_rng_unix.initialize (module Mirage_crypto_rng.Fortuna)"
mirage-crypto-rng-eio questions mirage/mirage-crypto#169 thanks to @bikallem @talex5)