Releases: mirage/digestif
Releases · mirage/digestif
1.2.0
CHANGES:
- Update the description to include SHA3 (@Leonidas-from-XIV, #146)
- Add a new type
hash'
, a polymorphic variant (@reynir, @dinosaure, #150) - Lint
fmt
dependency lower-bound (@reynir, #152) - Add
get_into_bytes
function and a fuzzer about it (@reynir, @dinosaure, #149)
1.1.4
CHANGES:
- Add a test about CVE-2022-37454 (@dinosaure, #143)
- Lint the distribution and delete the
pkg-config
dependency (@dinosuare, 1eff5c5) - Fix primitives used for bytes and fix the support of
js_of_ocaml
5 (@hhugo, #144)
1.1.3
CHANGES:
- Support MSVC compiler (@jonahbeckford, #137)
- Fix CI on Windows (
test_conv.ml
requires/dev/urandom
) (@dinosaure, #138) - Fix threads support (@dinosaure, #140)
- Delete the META trick needed for MirageOS 3 when we install
digestif
(@dinosaure, #141)
This version ofdigestif
breaks the compatibility with MirageOS 3
andocaml-freestanding
. This PR should unlock the ability to
usedune-cache
.
1.1.2
1.1.1
CHANGES:
- Hide C functions (
sha3_keccakf
) (@hannesm, #125) - Use
ocaml
to runinstall.ml
instead of a shebang (@Nymphium, #127) - Use
command -v
instead ofwhich
(@Numphium, #126) - Add
@since
meta-data in documentation (@c-cube, @dinosaure, #128) - Update the README.md (@dinosaure, @mimoo, #130)
ocaml-solo5
provides__ocaml_solo5__
instead of__ocaml_freestanding__
(@dinosaure, #131)
1.1.0
CHANGES:
- Add Keccak256 module (ethereum padding) (@maxtori, @dinosaure, #118)
- Update README.md to include the documentation (@mimoo, @dinosaure, 65a5c12)
- Remove deprecated function from
fmt
library (@dinosaure, #121) - NOTE: This version lost the support of OCaml 4.03 and OCaml 4.04.
1.0.1
CHANGES:
- Fix
esy
support (@dinosaure, #115) - Fix big-endian support (@dinosaure, #113)
v1.0.0
CHANGES:
- breaking changes Upgrade the library with MirageOS 3.9 (new layout of artifacts)
Add tests about compilation of unikernels (execution and link)
(#105, @dinosaure, @hannesm) - Fix
esy
installation (#104, @dinosaure) - breaking changes Better GADT (#103, @dinosaure)
As far as I can tell, nobody really use this part ofdigestif
.
The idea is to provide a GADT which contains the type of the hash.
From third-part libraries point-of-view, it's better to pattern-match with
such information instead to use a polymorphic variant (as before). - breaking changes key used for HMAC is a constant
string
(#101, @dinosaure, @hannesm)
The key should not follow the same type as the digest value (string
,bytes
,bigstring
).
This update restricts the user to user only constant key (as astring
).