STANDARDS.md update (#420)

* add composite to standards doc [skip ci] Signed-off-by: Michael Baentsch <[email protected]> * update link [skip ci] Signed-off-by: Michael Baentsch <[email protected]> * remove KEM encoder warning [skip ci] Signed-off-by: Michael Baentsch <[email protected]> * add KEM encoder config link [skip ci] Signed-off-by: Michael Baentsch <[email protected]> --------- Signed-off-by: Michael Baentsch <[email protected]>
open-quantum-safe · Jun 5, 2024 · 8b3d460 · 8b3d460
1 parent 1595f32
commit 8b3d460
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/STANDARDS.md b/STANDARDS.md
@@ -26,5 +26,6 @@ components, this provider implements the following standards:
   - Hybrid post-quantum / traditional private keys:
     - Simple concatenation of traditional and post-quantum components in plain binary / OCTET_STRING representations.
 
-Additionally worthwhile noting is that only quantum-safe [signature algorithms](README.md#signature-algorithms) are persisted via PKCS#8 and X.509. No corresponding encoder/decoder logic exists for quantum safe [KEM algorithms](README.md#kem-algorithms) -- See also [#194](https://github.com/open-quantum-safe/oqs-provider/issues/194).
+- For composite signatures, the implementation follows [this IETF draft](https://datatracker.ietf.org/doc/draft-ounsworth-pq-composite-sigs/) (version 13). Note that only those PQ algorithms denoted with the marker "composite" in [oqs-template/generate.yml](oqs-template/generate.yml) are provided with composite variants and not all.
 
+Note: Please heed the [documentation on the enablement of KEM encoders](CONFIGURE.md#oqs_kem_encoders) via PKCS#8 and X.509.