Skip to content
Discussion options

You must be logged in to vote

In general you just need to list your specific dependencies - the module system should always correctly enable internally anything that is required (if any module configuration fails to build or fails to pass all tests, it's a bug and a report would be appreciated). So for example for NIST standard ML-KEM you would just need to enable ml_kem - this will implicitly enable kyber because of how the implementation is currently structured, but you don't need to ask for it if you don't need it. The only really tricky part is that right now, hardware specific modules are not implicitly enabled. So for example for SHA-512 you would enable sha2_64 but this will not enable hardware acceleration. To…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@nata11
Comment options

Answer selected by nata11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants