-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ML-KEM C extraction to CI #200
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Work is happening on franziskus/ml-kem-c-extraction. This is currently blocked by issues in #199 .
A way of running the hax verification toolchain that is reproducible and maintainable.
Requirements
Design
The approach depends on two main parts: configuration, and driver.
A
hax.toml
defines how to run the hax toolchain, what to extract and how to verify it.A
hax.py
script uses the config to drive the toolchain.Config
[target]
cargo
: arguments for cargotarget
: the hax backend to useinclude
: the-i
include string (optional)interfaces
: the F*interfaces
string (optional)verify
: the commands to run verificationclean
: the commands to clean the target[dependencies]
git
: the git url to get the dependency fromversion
: the version (tag) to use (optional)rev
: the revision to use (optional)build
: the commands to build the dependencyDriver
The driver calls all the different tools to
extract
the code for the targetdependencies
for the verification and extractionverify
the targetextract_c
The text was updated successfully, but these errors were encountered: