From: Jonathan Protzenko <jonathan.protzenko@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] [ANN] Official OCaml bindings for verified Everest cryptography
Date: Thu, 14 May 2020 08:00:18 -0700 [thread overview]
Message-ID: <f5b42a5d-5e64-520e-6e05-0b7864e1ea9e@gmail.com> (raw)
The Everest team is pleased to announce the release of official OCaml
bindings for all of our verified cryptographic algorithms, now available
through OPAM as packages hacl-star and hacl-star-raw.
We provide bindings for the following:
- HACL*, a library of pure C algorithms
- Vale, a collection of optimized core assembly routines for maximum
performance
- EverCrypt, an agile, multiplexing API with CPU auto-detection that
brings together HACL* and Vale.
Our code is compiled from the F* programming language to C via the
KReMLin compiler ("K&R meets ML"). We offer two OPAM packages:
- hacl-star-raw consists of low-level ocaml-ctypes bindings generated by
KReMLin
- hacl-star is a hand-written OCaml idiomatic API that uses much more
pleasant signatures, types and abstractions and is also safer, as it
checks all static preconditions at run-time
We support AES{128,256}-GCM, Chacha20-Poly1305, Curve25519 / Ed25519,
P256, MD5, SHA-{1,2,3} (all variants), Blake2 (s&b), HMAC/HKDF, and the
HPKE and SecretBox high-level APIs. Some algorithms are optimized for
Intel chips, notably AES-GCM -- see
https://hacl-star.github.io/Supported.html for full details.
General documentation about the project is available at
https://hacl-star.github.io/index.html -- sample code for the OCaml API
is provided as part of the test suite
https://github.com/project-everest/hacl-star/tree/master/bindings/ocaml/tests
This work was performed by Victor Dumitrescu from Nomadic Labs, one of
the teams responsible for the core development of the Tezos blockchain.
Happy hacking,
Jonathan, on behalf of the Everest Team
reply other threads:[~2020-05-14 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f5b42a5d-5e64-520e-6e05-0b7864e1ea9e@gmail.com \
--to=jonathan.protzenko@gmail.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox