[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.2) #24461
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:
interface instead of mtime.clock.os. (mirage-crypto-rng-eio: use monotonic clock from eio's environment instead of mtime mirage/mirage-crypto#176 @TheLortex)
reported by @samoht unsigned char is not uint1, truncations != C casts != promises mit-plv/fiat-crypto#1606 (comment)
re-reported in
Es256_priv
Jwk always failsvalidate_signature
withInvalid_signature
ulrikstrid/ocaml-jose#63 and TLSIllegal_parameter
on macOS mirleft/ocaml-tls#478(on macos (arm64), avoid -O3 due to miscompilations mirage/mirage-crypto#185 @hannesm @kit-ty-kate)
in devel mode (Build powerpc64 with -Wno-stringop-overflow tests due to false positives mirage/mirage-crypto#178 avoid stringop-overflow warning on ppc64, s390x mirage/mirage-crypto#184 @avsm @hannesm)
@avsm @hannesm)