-
Notifications
You must be signed in to change notification settings - Fork 41
HOL-Light: Add hol-server for interactive proof development #1500
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
base: main
Are you sure you want to change the base?
Conversation
CBMC Results (ML-KEM-512)Full Results (139 proofs)
|
CBMC Results (ML-KEM-1024)Full Results (139 proofs)
|
CBMC Results (ML-KEM-768)Full Results (139 proofs)
|
|
I tried the PR locally.
The failure looks a bit odd, as if the hol-light or s2n-bignum version aren't right. But then the CI shouldn't be happy either? I need to take a closer look. @mkannwischer Any idea from the top of your head? |
Integrates hol_server (https://github.com/monadius/hol_server) to enable TCP-based communication with HOL Light. This allows sending commands programmatically via netcat or the VS Code extension. Usage: hol-server [port] # default port is 2012 Update documentation accordingly. - Ported from pq-code-package/mldsa-native#883 Signed-off-by: Matthias J. Kannwischer <matthias@kannwischer.eu>
0265f8c to
a1f2360
Compare
Running just the x86_64 poly_tobytes proof works fine for me with the hol-server in this branch. in a single HOL-Light session which is what you would need to do if you want to run both an AArch64 and x86_64 proof. But it happily continue to execute, so you may have not seen those exceptions. I'd say that limitation is not introduced by this PR and you'll probably have to fix it upstream if you really want to support it. |
|
@mkannwischer Agreed |
Integrates hol_server (https://github.com/monadius/hol_server) to enable TCP-based communication with HOL Light. This allows sending commands programmatically via netcat or the VS Code extension.
Usage: hol-server [port] # default port is 2012
Update documentation accordingly.