-
Notifications
You must be signed in to change notification settings - Fork 95
Interoperability
Michael Baentsch edited this page Oct 27, 2022
·
9 revisions
oqsprovider by default follows the implementation of oqs-openssl111 which in turn follows the above RFC draft.
This more recent RFC draft calls for Dilithium private keys to only optionally contain public key components. Enabling conceptual interoperability with this proposal, a cmake build define is available in oqsprovider for all QSC algorithms supported:
Setting this cmake build variable to "ON" eliminates public key components from PKCS#8 files. A provider binary built with this capability is denoted by the added "-nopub" designation in its version information. This can be displayed for example by running openssl list -providers -provider oqsprovider.