-
Notifications
You must be signed in to change notification settings - Fork 573
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
Refactor public key related performance test code #4367
Conversation
8b6f333
to
fc2d731
Compare
Also remove the pcurves ECDH/ECDSA benchmarks which are not relevant anymore, now that EC_Group/EC_Scalar/EC_AffinePoint use pcurves internally.
This is apparently necessary for MSVC to export it
"Kyber-512-r3", | ||
"Kyber-512-90s-r3", | ||
"Kyber-768-r3", | ||
"Kyber-768-90s-r3", | ||
"Kyber-1024-r3", | ||
"Kyber-1024-90s-r3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Admittedly, a bit late to the party. Nevertheless: When building with --disable-modules=kyber_90s
, this will error with:
Kyber-Kyber-512-r3 65559 KEM encrypt/sec; 0.02 ms/op 38070 cycles/op (26176 ops in 399 ms)
Kyber-Kyber-512-r3 52351 KEM decrypt/sec; 0.02 ms/op 47679 cycles/op (26176 ops in 500 ms)
Error: Not implemented requested Kyber mode is not enabled in this build
... instead of skipping the Kyber 90s modes. Similarly for other algorithms where specific groups of modes may be disabled at build time.
Could be fixed by (for instance):
#if defined(BOTAN_HAS_KYBER)
"Kyber-512-r3",
"Kyber-768-r3",
"Kyber-1024-r3",
#endif
#if defined(BOTAN_AS_KYBER_90S)
"Kyber-512-90s-r3",
"Kyber-768-90s-r3",
"Kyber-1024-90s-r3",
#endif
No description provided.