[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
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
…age, mirage-crypto-rng-lwt, mirage-crypto-rng-eio, mirage-crypto-rng-async, mirage-crypto-pk and mirage-crypto-ec (0.11.2) CHANGES: * mirage-crypto-rng-eio: improve portability by using eio 0.7's monotonic clock interface instead of mtime.clock.os. (mirage/mirage-crypto#176 @TheLortex) * mirage-crypto-rng-eio: update to eio 0.12 (mirage/mirage-crypto#182 @talex5) * mirage-crypto-rng: fix typo in RNG setup (mirage/mirage-crypto#179 @samueldurantes) * macOS: on arm64 with clang 14.0.3, avoid instcombine (due to miscompilations) reported by @samoht mit-plv/fiat-crypto#1606 (comment) re-reported in ulrikstrid/ocaml-jose#63 and mirleft/ocaml-tls#478 (mirage/mirage-crypto#185 @hannesm @kit-ty-kate) * avoid "stringop-overflow" warning on PPC64 and S390x (spurious warnings) when in devel mode (mirage/mirage-crypto#178 mirage/mirage-crypto#184 @avsm @hannesm) * stricter C prototypes, unsigned/signed integers (mirage/mirage-crypto#175 @MisterDA @haesbaert @avsm @hannesm) * support DragonFlyBSD (mirage/mirage-crypto#181 @movepointsolutions) * support GNU/Hurd (mirage/mirage-crypto#174 @pinotree)
This was referenced Sep 18, 2023
Closed
|
a note about the ca-certs failures: version 0.2.3 has a fix for alpine -- should the previous releases be marked as unavailable (or unavailable for alpine)? I've no clue what the policy is -- from my point of view, the earlier releases should be removed from opam-repository to avoid anyone installing them (but I understand that the policy is to never remove anything). |
This was referenced Sep 18, 2023
|
remaining failures are unrelated |
|
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.
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_privJwk always failsvalidate_signaturewithInvalid_signatureulrikstrid/ocaml-jose#63 and TLSIllegal_parameteron 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)