These files allow pqcrystals to determine/drive how/what downstream repositories, particularly OQS, imports from this repository.
These files are designed very much like the PQClean META.yml files and thus may also ease automated integration to that repository and its downstreams if and when so desired (future work).
Conceptually missing is a separation into common and algorithm specific files (pursuant #21). Thus, the common files are currently all concentrated in the DILITHIUM_3_META.yml. This will cause downstream problems if a liboqs build of DILITHIUM4 without DILITHIUM3 is requested. At this time (prior to NIST round 3 decision, missing implementation of #21, missing integration with Kyber common code) this is considered an acceptable limitation.
Coverage remained the same at 94.537% when pulling 843bcdc7f6923effb394fdfd304b6bff1f977c0a on baentsch:oqs-prep into 17e7e5baf5263fb882f3140ae11b2e1ad2500535 on pq-crystals:master.
These files allow
pqcrystals
to determine/drive how/what downstream repositories, particularly OQS, imports from this repository.These files are designed very much like the
PQClean
META.yml files and thus may also ease automated integration to that repository and its downstreams if and when so desired (future work).Conceptually missing is a separation into common and algorithm specific files (pursuant #21). Thus, the common files are currently all concentrated in the
DILITHIUM_3_META.yml
. This will cause downstream problems if aliboqs
build of DILITHIUM4 without DILITHIUM3 is requested. At this time (prior to NIST round 3 decision, missing implementation of #21, missing integration withKyber
common code) this is considered an acceptable limitation.