Build oqs-provider with only kyber tls key exchange functionality

[fwh-dc]

Hi,

Is it possible to configure the build to only include kyber (+hybrids) tls keyexchange functionality?

Regards,
Frederik

[Hawazyn]

Please see Minimal Build - OQS for guidance on configuring the build.

[baentsch]

Beyond the correct answer above for building a minimal liboqs also oqsprovider itself can be configured to carry fewer algorithms: See here. But it may be an interesting experiment to see how the build logic behaves if only providing a minimal liboqs as per the proposal be @Hayyaaf ... Ideal would be if it automatically skips algorithms unavailable in the library build. Feedback (or improvements if it fails) would be welcome!

[fwh-dc]

I haven't had the time to test it yet, but thanks for the suggestions!

[Hawazyn]

it may be an interesting experiment to see how the build logic behaves if only providing a minimal liboqs as per the proposal be @Hayyaaf ...

‎‏I successfully built liboqs as I proposed earlier. The build and installation completed without any issues. However, the tests from the ./scripts/runtests.sh script in the oqsprovider repository failed.

‎‏Nothing seems particularly weird in the logs, and I’ve tried several algorithms during testing. Interestingly, Wireshark only captured the algorithms configured in liboqs.

‎‏Let me know if you’d like me to share more specific details or perform further experiments.

[baentsch]

Well, if you think something's broken, please create a bug report (how to reproduce, what's expected vs. what's actually happening).