Using liboqs algorithms not in the fork

If an algorithm is provided by liboqs but has not been listed as being supported by OQS-OpenSSL, it can still be used through either one of the two following methods:

• oqsdefault
• Code Generation

oqsdefault

liboqs can be configured at compile-time to use any of its algorithms as the "default" algorithm. If OpenSSL 1.1.1 is told to use oqs_kem_default or oqsdefault, then it will respectively use whichever KEM or signature algorithm was set as the default in liboqs at compile time. Similarly if OpenSSL 1.0.2 is told to use DEFAULT, it will use whichever KEM as the default in liboqs at compile time. To set the default algorithm:

1. Follow instructions here to compile liboqs with your preferred default algorithms.

2. Recompile OpenSSL against the newly built liboqs as in the Quickstart section here

Code Generation

The oqs-template folder contains a mechanism by which the code to add a new key-exchange or digital signature algorithm is automatically generated and inserted at the appropriate locations in the OpenSSL code base. If support for a new algorithm is required, the steps for adding it can be found in the Contributing Guide.