package mirage-crypto-rng
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=a27910365d59b02c3f0e8a40d93a5b81835acf832e1ffa596ee772b41e8a900b
sha512=eb0d5a947649d6d9d55b8f5d5ea624e7b2b969baf7b855bf86b46cfadf9312e42e9caea479eb9c364a3c9cd4b3aa56f3a6a1b0cc20e022fdbd82bdb722df1198
Description
Mirage-crypto-rng provides a random number generator interface, and implementations: Fortuna, HMAC-DRBG, getrandom/getentropy based (in the unix sublibrary)
Published: 26 Jul 2021
README
mirage-crypto - Cryptographic primitives for MirageOS
v0.10.3
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, ChaCha20/Poly1305), 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-rng embeds the former mirage-entropy opam package, which implements various entropy sources:
non-deterministic execution time (used at initial seeding, see the whirlwind RNG paper)
a hook into the Lwt event loop that collects a timestamp of each event
rdseed and rdrand (x86/x86-64 only)
Build
dune build
dune runtest
FAQ
RNG seeding
If RNG fails with Fatal error: exception Unseeded_generator
, you need to seed it.
Lwt:
let () = Mirage_crypto_rng_lwt.initialize ()
Unix:
let () = Mirage_crypto_rng_unix.initialize ()
Dependencies (9)
-
lwt
>= "4.0.0"
-
mtime
>= "1.0.0"
-
mirage-crypto
= version
- logs
-
cstruct
>= "4.0.0"
- duration
-
dune-configurator
>= "2.0.0"
-
dune
>= "2.6"
-
ocaml
>= "4.08.0"
Dev Dependencies (2)
-
randomconv
with-test & >= "0.1.3" & < "0.2.0"
-
ounit
with-test
Used by (51)
-
albatross
< "1.5.6"
-
awa
< "0.1.2"
- awa-lwt
-
builder-web
< "0.2.0"
-
caldav
< "0.2.3"
-
capnp-rpc-mirage
>= "0.9.0" & < "1.2.3"
-
capnp-rpc-net
>= "0.9.0" & < "1.2.4"
-
capnp-rpc-unix
>= "0.9.0" & < "1.2.3"
-
caqti-eio
>= "2.1.1"
-
certify
>= "0.3.3"
- conduit-async-tls
- conduit-lwt-tls
- conex-mirage-crypto
-
current_web
>= "0.3" & < "0.6.4"
- dirsp-proscript-mirage
-
dkim
>= "0.2.0" & < "0.5.0"
-
dkim-mirage
>= "0.2.0" & < "0.5.0"
-
dns-certify
>= "4.6.3" & < "9.0.0"
-
dns-cli
>= "4.4.0" & != "4.6.0" & < "7.0.0"
-
dns-client
>= "4.5.0" & < "7.0.0"
-
dns-server
>= "4.4.0" & < "7.0.0"
-
dream
< "1.0.0~alpha7"
-
git
>= "2.1.3" & < "3.17.0"
-
git-mirage
= "2.1.3"
-
git-unix
>= "2.1.3" & < "3.13.0"
-
http-mirage-client
>= "0.0.3"
- hyper
-
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-ec
= "0.10.3"
-
mirage-crypto-pk
= "0.10.3"
-
mirage-crypto-rng-async
= "0.10.3"
-
mirage-crypto-rng-mirage
= "0.10.3"
-
mrmime
>= "0.5.0"
- oidc
-
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" & < "1.0.0"
-
tls-eio
< "0.17.2"
- tls-liquidsoap
- twostep
- u2f
-
webauthn
< "0.2.0"
-
x509
>= "0.10.0" & < "0.16.4"
Conflicts (1)
-
mirage-runtime
< "3.8.0"