Calascibetta Romain
Calascibetta Romain
> @hannesm There is a PR to address some of the CI errors (https://github.com/mirage/mirage-crypto/pull/157). Could we merge this PR. Once that is merged, I will look into adding github actions...
Yes. this is the length (`digest_size`) of the BLAKE2B hash. You can decide the length of the BLAKE2{B,S} hash and it will be a part of the initial `IV` used....
I try to figure out how to complete the documentation but since #103, I arbitrary did the choice to delete this argument (which can be error-prone and generate segfaults with...
It seems that this instruction: https://github.com/mirage/digestif/blob/7adc43cc8d1d80c2d9104dabd5730425b1b7ace8/digestif.opam#L32 Is not executed properly with OCaml. Not sure where is the error. I will try to look deeper and fix your issue.
@RyanGibb I suspect that you currently trying to compile `mirageos` (on another system) and I would like to know if you got the same issue as @davisuga.
Hmmhmm, I think the best is just to delete such code. I trying to figure out how long I can keep it and break the support of MirageOS 3 but...
Which parameters you want to personalize in BLAKE2? The interface currently allows to personalize the length of the hash: https://github.com/mirage/digestif/blob/891907675ead09b5e1c5de28c24246a0e411a546/src/digestif.mli#L232-L238 I'm aware about some others parameters but I need to...
As I said, an other `init` function with personalization should be fine for me 👍 . So if you want to propose something like that, I will happy to review...
According to #92, `ocaml-ci` will be used but a problem persist, `ocaml-ci` wants to install `ocaml-freestanding` **and** `ocaml-freestanding-cross-aarch64` which are incompatible for MirageOS 4-**rc1**. When we will fix the co-instability...