package mirage-crypto-rng
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=85c2e419fb8215ff354988ee58f1335b452da41f1bf3022a62d29ab8af56d462
sha512=ea3f1a99f9e7e1d66198a8ca7a07ae2f11ac6ef49f2a8b3d14f414a70243db09ec79454200e423d3792f58effa421fe3213e5ee6efe5e9ec8e43fd3444dad22c
Description
Mirage-crypto-rng provides a random number generator interface, and implementations: Fortuna, HMAC-DRBG, getrandom/getentropy based (in the unix sublibrary)
Published: 11 Mar 2020
README
mirage-crypto - Cryptographic primitives for MirageOS
v0.6.0
mirage-crypto is a small cryptographic library that puts emphasis on the applicative style and ease of use. It includes basic ciphers (AES, 3DES, RC4), hashes (MD5, SHA1, SHA2 family), AEAD primitives (AES-GCM, AES-CCM), public-key primitives (RSA, DSA, DH) and a strong RNG (Fortuna).
RSA timing attacks are countered by blinding. AES timing attacks are avoided by delegating to AES-NI.
Mirage-crypto is a fork of the ocaml-nocrypto written by David Kaloper. It was forked with the permission of the original author in order to facilitate changes (e.g. build system) required by Mirage that the upstream didn't have time to keep up with.
Mirage-crypto-entropy embeds the former mirage-entropy opam package, which implements various entropy sources for MirageOS unikernels:
timer based ones (see whirlwind RNG paper)
rdseed and rdrand (x86/x86-64 only)
Status
This is a work in progress repository that is not yet released. Please see https://github.com/mirage/mirage-crypto/issues/1 for our progress towards a stable release.
Build
dune build
dune runtest
FAQ
RNG seeding
If RNG fails with Fatal error: exception Uncommon.Boot.Unseeded_generator, you need to seed it.
Unix:
let () = Mirage_crypto_rng_unix.initialize ()
Illegal instructions
Program terminated with signal SIGILL, Illegal instruction.
#0 _mm_aeskeygenassist_si128 (__C=<optimized out>, __X=...)
Mirage_crypto has CPU acceleration support (SSE2+AES-NI), but no run-time autodetection yet. You compiled the library with acceleration, but you are using it on a machine that does not support it.
The environment variable MIRAGE_CRYPTO_ACCELERATE can be used to override detection:
MIRAGE_CRYPTO_ACCELERATE=false dune buildforce-disables non-portable code.MIRAGE_CRYPTO_ACCELERATE=true dune buildforce-enables non-portable code.Otherwise, it matches the capabilities of the build machine.
Dependencies (4)
-
mirage-crypto
= version -
cstruct
>= "3.2.0" -
dune
>= "1.7" -
ocaml
>= "4.07.0"
Dev Dependencies (3)
-
ounit
with-test -
randomconv
with-test & >= "0.1.3" & < "0.2.0" -
ounit
with-test
Used by (38)
-
awa
< "0.1.2" - awa-lwt
-
builder-web
< "0.2.0" -
caldav
< "0.2.3" -
capnp-rpc-net
>= "0.9.0" -
caqti-eio
>= "2.1.1" -
certify
>= "0.3.3" - conex-mirage-crypto
-
current_web
>= "0.3" & < "0.6.4" -
dkim
>= "0.2.0" & < "0.5.0" -
dkim-mirage
>= "0.2.0" & < "0.5.0" -
dns-cli
>= "4.4.0" & < "4.6.0" -
dns-client
>= "4.5.0" & < "4.6.1" -
dns-server
>= "4.4.0" & < "7.0.0" -
dream
>= "1.0.0~alpha5" & < "1.0.0~alpha7" -
git
= "2.1.3" -
git-mirage
= "2.1.3" -
git-unix
= "2.1.3" -
http-mirage-client
>= "0.0.3" -
hyper
>= "1.0.0~alpha2" -
jose
>= "0.8.2" -
letsencrypt
>= "0.2.1" & < "0.5.0" -
letsencrypt-app
< "0.5.0" - miou
-
mirage-block-ccm
= "1.1.0" -
mirage-crypto-entropy
< "0.6.1" -
mirage-crypto-pk
< "0.6.1" -
mrmime
>= "0.5.0" -
otr
>= "0.3.7" & < "0.3.10" -
paf
< "0.5.0" -
paf-cohttp
< "0.5.0" -
rfc6287
>= "1.0.4" -
session
>= "0.5.0" -
ssh-agent
>= "0.3.0" & < "0.4.1" -
tls
>= "0.11.0" & < "0.12.2" - u2f
-
webauthn
< "0.2.0" -
x509
>= "0.10.0" & < "0.16.4"
Conflicts
None