Project Everest aims to build and deploy a verified HTTPS stack.
The HTTPS ecosystem (HTTPS and TLS protocols, X.509 public key infrastructure, crypto algorithms) is the foundation on which Internet security is built. Unfortunately, this ecosystem is extremely brittle, with headline-grabbing attacks such as FREAK and LogJam http://mitls.org/pages/attacks/ and emergency patches many times a year.
Project Everest proposes to deﬁnitively solve this problem by constructing a high-performance, standards-compliant, veriﬁed implementation of the full HTTPS ecosystem, from the HTTPS API down to and including cryptographic algorithms such as RSA and AES. At the TLS level, for instance, we will develop new implementations of existing protocol standards and formally prove, by reduction to cryptographic assumptions on their core algorithms, that our implementations provide a secure-channel abstraction between the communicating endpoints. Project Everest aims to be a drop-in replacement for the HTTPS library in mainstream web browsers, servers, and other popular tools.
What is Project Everest?
Project Everest is the combination of the following projects. Read below for an easy way to install all these projects together.
- F*, a verification-oriented dialect of ML
- miTLS, our implementation of the TLS protocol, written in F*
- KreMLin, a compiler from a subset of F* to C
- HACL*, a verified library of cryptographic primitives written in F*
- Vale (formerly codenamed Spartan), a domain-specific language designed to implement verified cryptographic primitives in assembly
- Dafny, a program verifier that Vale currently relies on.
When combined together, the projects above will generate a C library that not only implements TLS 1.3 but is also proven secure.
We generate a C library, but the verification is not complete.
- The TLS 1.3 handshake verification is work in progress and still relies on the OCaml extraction mechanism of F*; thus, the C library still encapsulates the OCaml runtime system.
- We are nearing completion on the verification of the TLS 1.3 record layer; it currently extracts to C.
- The AES and SHA cryptographic assembly routines are verified and extract to assembly via Vale.
Our test client implements TLS 1.2 + TLS 1.3 Draft 18 and successfully connects
to TLS 1.3 test servers. We have a prototype integration of miTLS within libcurl
that one can use to
git clone a remote repository.
Getting started with Project Everest
To make things easier for prospective users, the everest script performs high-level project management and revision tracking.
Prerequisite (Windows only). Open up a Cygwin64 terminal with a Cygwin git client. Our library is a native Windows DLL but we rely on Cygwin to provide the Unix tools that many of our projects rely on.
The first step checks out the high-level
git clone https://github.com/project-everest/everest cd everest
This will ensure that your environment is sane. On Windows, this will fetch & install a proper version of OCaml and all packages for you.
If you just want to read the sources, then the step below is sufficient; it will fetch blessed versions of all the projects, which are known to work together.
Building all the projects together should work at any time, and be achieved by running
Testing the generated binaries can be achieved by running:
But, remember that the whole point of the Everest project is that our code is entirely verified. Verification (which can be as slow as 2 hours on recent machines) can be performed by running:
Finally, if you want to revert to a clean state, you can run:
For the lazy: the
projecteverest/everest Docker image
Every night, we automatically build the
Docker image with everything already built and verified, for you to
directly pull from
the Docker Hub. If
you have Docker installed on your machine, then you can pull the image
using the usual command:
docker pull projecteverest/everest
Please file bugs if something doesn’t work!
Coming soon. Subscribe via RSS