Update Kyber and Dilithium to FIPS versions

[dstebila]

Once the FIPS drafts are released, we'll need to update Kyber and Dilithium based on the tweaks added by NIST.

Upstream already has started on this:

• https://github.com/pq-crystals/kyber/tree/standard
• https://github.com/pq-crystals/dilithium/tree/standard

[beldmit]

Could you please provide the links to the FIPS drafts?

[dstebila]

They're not publicly available yet.

[bhess]

The FIPS drafts are now available:
FIPS 203, Module-Lattice-Based Key-Encapsulation Mechanism Standard
FIPS 204, Module-Lattice-Based Digital Signature Standard
I'll do a pull from the pq-crystals repo/standard branch next week.

[dghgit]

One quick question (I hope) about this. I've heard the OIDs for Dilithium may be updated to reflect the change in algorithm. If so would it be possible to find out what the OID values will be now? I'm in the process of updating myself but want to make sure I can still interop (have some users chaffing at the bit as well). Thanks.

[baentsch]

the OIDs for Dilithium may be updated to reflect the change in algorithm.

The OIDs must be updated if KATs change. If IBM (current dilithium name range holder) or NIST (standards range) doesn't do it, I will :-) But as I am member of neither organization I cannot predict what those values will be. If OQS were the only organization interested in ensuring separation of "old" vs "new" artifacts, the numbers will be progressing from here which is our master file for OID allocation of algorithms without other OID management.

[dghgit]

Thanks for the definitive answer and the link. Okay, I guess we're waiting on IBM then. I hope they're feeling lively!

[bhess]

One quick question (I hope) about this. I've heard the OIDs for Dilithium may be updated to reflect the change in algorithm. If so would it be possible to find out what the OID values will be now? I'm in the process of updating myself but want to make sure I can still interop (have some users chaffing at the bit as well). Thanks.

Yes, an update is needed because of the KAT change.
Planning to use the following OIDs for the FIPS drafts of Dilithium/ML-DSA:

Dilithium2 (ML-DSA-44): 1.3.6.1.4.1.2.267.12.4.4
Dilithium3 (ML-DSA-65): 1.3.6.1.4.1.2.267.12.6.5
Dilithium5 (ML-DSA-87): 1.3.6.1.4.1.2.267.12.8.7

[dghgit]

thanks, that's a big help. I'll get to work.

[baentsch]

thanks, that's a big help. I'll get to work.

Sad I cannot say the same: I've got to wait for "liboqs" to merge this and only then can add it to "oqsprovider" -- and only after that can do a new iteration after IETF-Hackathon/pqc-certificates#65 gets merged (if it gets merged -- still waiting for feedback there whether/when to do it).

[bwesterb]

@cjpatton Did we pin liboqs? Otherwise things will break when this lands.