Rename ML-KEM hybrids to match IETF Draft.

This commit is contained in:
Anthony Hu
2025-07-25 13:27:26 -04:00
parent a06268f705
commit c7e054a7a7
10 changed files with 250 additions and 228 deletions
+5 -5
View File
@@ -208,13 +208,13 @@
For a quick start, you can run the client and server like this:
$ ./examples/server/server -v 4 --pqc P521_ML_KEM_1024
$ ./examples/client/client -v 4 --pqc P521_ML_KEM_1024
$ ./examples/server/server -v 4 --pqc SecP521r1MLKEM1024
$ ./examples/client/client -v 4 --pqc SecP521r1MLKEM1024
Look for the following line in the output of the server and client:
```
Using Post-Quantum KEM: P521_ML_KEM_1024
Using Post-Quantum KEM: SecP521r1MLKEM1024
```
For authentication, you can generate a certificate chain using the Open
@@ -236,13 +236,13 @@
-A certs/mldsa87_root_cert.pem \
-c certs/mldsa44_entity_cert.pem \
-k certs/mldsa44_entity_key.pem \
--pqc P521_ML_KEM_1024
--pqc SecP521r1MLKEM1024
$ examples/client/client -v 4 -l TLS_AES_256_GCM_SHA384 \
-A certs/mldsa44_root_cert.pem \
-c certs/mldsa87_entity_cert.pem \
-k certs/mldsa87_entity_key.pem \
--pqc P521_ML_KEM_1024
--pqc SecP521r1MLKEM1024
Congratulations! You have just achieved a fully quantum-safe TLS 1.3
connection!