Skip to content

Commit f8a1aff

Browse files
JacobBarthelmehJacobBarthelmeh
authored
Merge pull request #215 from anhu/mlkem-hybrid-draft-names-docs
Rename ML-KEM hybrids to match IETF Draft.
2 parents b610e83 + f491e55 commit f8a1aff

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

‎wolfSSL/src/appendix07.md‎

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -67,15 +67,15 @@ You can run the server and client like this in separate terminals:
6767
-A certs/mldsa87_root_cert.pem \
6868
-c certs/mldsa44_entity_cert.pem \
6969
-k certs/mldsa44_entity_key.pem \
70-
--pqc P521_ML_KEM_1024
70+
--pqc SecP521r1MLKEM1024
7171
```
7272

7373
```sh
7474
$ examples/client/client -v 4 -l TLS_AES_256_GCM_SHA384 \
7575
-A certs/mldsa44_root_cert.pem \
7676
-c certs/mldsa87_entity_cert.pem \
7777
-k certs/mldsa87_entity_key.pem \
78-
--pqc P521_ML_KEM_1024
78+
--pqc SecP521r1MLKEM1024
7979
```
8080

8181
You have just achieved a fully quantum-safe TLS 1.3 connection using AES-256 for symmetric encryption, the ML-DSA signature scheme for authentication and ECDHE hybridized with ML-KEM for key establishment.
@@ -99,9 +99,9 @@ Post-Quantum hybrid KEM names:
9999

100100
wolfSSL Variant Name | NIST ECC Curve and PQC Submission Variant Name
101101
-------------------- | ----------------------------------------------
102-
`P256_ML_KEM_512` | ECDSA P-256 and KYBER512
103-
`P384_ML_KEM_768` | ECDSA P-384 and KYBER768
104-
`P521_ML_KEM_1024` | ECDSA P-521 and KYBER1024
102+
`SecP256r1MLKEM512` | ECDSA P-256 and KYBER512
103+
`SecP384r1MLKEM768` | ECDSA P-384 and KYBER768
104+
`SecP521r1MLKEM1024` | ECDSA P-521 and KYBER1024
105105

106106
## Cryptographic Artifact Sizes
107107

@@ -157,9 +157,9 @@ TLS_AES_256_GCM_SHA384 | RSA 2048 bit | ECC SECP256R1 | 5455
157157
TLS_AES_256_GCM_SHA384 | RSA 2048 bit | ML_KEM_512 | 6633
158158
TLS_AES_256_GCM_SHA384 | RSA 2048 bit | ML_KEM_768 | 7337
159159
TLS_AES_256_GCM_SHA384 | RSA 2048 bit | ML_KEM_1024 | 8201
160-
TLS_AES_256_GCM_SHA384 | RSA 2048 bit | P256_ML_KEM_512 | 6763
161-
TLS_AES_256_GCM_SHA384 | RSA 2048 bit | P384_ML_KEM_768 | 7531
162-
TLS_AES_256_GCM_SHA384 | RSA 2048 bit | P521_ML_KEM_1024 | 8467
160+
TLS_AES_256_GCM_SHA384 | RSA 2048 bit | SecP256r1MLKEM512 | 6763
161+
TLS_AES_256_GCM_SHA384 | RSA 2048 bit | SecP384r1MLKEM768 | 7531
162+
TLS_AES_256_GCM_SHA384 | RSA 2048 bit | SecP521r1MLKEM1024 | 8467
163163
TLS_AES_256_GCM_SHA384 | ML_DSA_44 | ECC SECP256R1 | 7918
164164
TLS_AES_256_GCM_SHA384 | ML_DSA_65 | ECC SECP256R1 | 10233
165165
TLS_AES_256_GCM_SHA384 | ML_DSA_87 | ECC SECP256R1 | 13477
@@ -635,7 +635,7 @@ wolfSSL Client Benchmark on TLS13-AES128-GCM-SHA256 with group ML_KEM_1024:
635635
Connect : 50.328 ms
636636
Connect Avg : 2.097 ms
637637
638-
wolfSSL Server Benchmark on TLS13-AES128-GCM-SHA256 with group P256_ML_KEM_512:
638+
wolfSSL Server Benchmark on TLS13-AES128-GCM-SHA256 with group SecP256r1MLKEM512:
639639
Total : 6029312 bytes
640640
Num Conns : 24
641641
Rx Total : 961.483 ms
@@ -644,7 +644,7 @@ wolfSSL Server Benchmark on TLS13-AES128-GCM-SHA256 with group P256_ML_KEM_512:
644644
Tx : 386.966 MB/s
645645
Connect : 55.885 ms
646646
Connect Avg : 2.329 ms
647-
wolfSSL Client Benchmark on TLS13-AES128-GCM-SHA256 with group P256_ML_KEM_512:
647+
wolfSSL Client Benchmark on TLS13-AES128-GCM-SHA256 with group SecP256r1MLKEM512:
648648
Total : 6029312 bytes
649649
Num Conns : 24
650650
Rx Total : 963.042 ms
@@ -654,7 +654,7 @@ wolfSSL Client Benchmark on TLS13-AES128-GCM-SHA256 with group P256_ML_KEM_512:
654654
Connect : 53.236 ms
655655
Connect Avg : 2.218 ms
656656
657-
wolfSSL Server Benchmark on TLS13-AES128-GCM-SHA256 with group P384_ML_KEM_768:
657+
wolfSSL Server Benchmark on TLS13-AES128-GCM-SHA256 with group SecP384r1MLKEM768:
658658
Total : 5767168 bytes
659659
Num Conns : 23
660660
Rx Total : 927.519 ms
@@ -663,7 +663,7 @@ wolfSSL Server Benchmark on TLS13-AES128-GCM-SHA256 with group P384_ML_KEM_768:
663663
Tx : 374.747 MB/s
664664
Connect : 64.464 ms
665665
Connect Avg : 2.803 ms
666-
wolfSSL Client Benchmark on TLS13-AES128-GCM-SHA256 with group P384_ML_KEM_768:
666+
wolfSSL Client Benchmark on TLS13-AES128-GCM-SHA256 with group SecP384r1MLKEM768:
667667
Total : 5767168 bytes
668668
Num Conns : 23
669669
Rx Total : 929.281 ms
@@ -673,7 +673,7 @@ wolfSSL Client Benchmark on TLS13-AES128-GCM-SHA256 with group P384_ML_KEM_768:
673673
Connect : 60.200 ms
674674
Connect Avg : 2.617 ms
675675
676-
wolfSSL Server Benchmark on TLS13-AES128-GCM-SHA256 with group P521_ML_KEM_1024:
676+
wolfSSL Server Benchmark on TLS13-AES128-GCM-SHA256 with group SecP521r1MLKEM1024:
677677
Total : 5767168 bytes
678678
Num Conns : 23
679679
Rx Total : 918.122 ms
@@ -682,7 +682,7 @@ wolfSSL Server Benchmark on TLS13-AES128-GCM-SHA256 with group P521_ML_KEM_1024:
682682
Tx : 361.941 MB/s
683683
Connect : 79.426 ms
684684
Connect Avg : 3.453 ms
685-
wolfSSL Client Benchmark on TLS13-AES128-GCM-SHA256 with group P521_ML_KEM_1024:
685+
wolfSSL Client Benchmark on TLS13-AES128-GCM-SHA256 with group SecP521r1MLKEM1024:
686686
Total : 5767168 bytes
687687
Num Conns : 23
688688
Rx Total : 919.900 ms
@@ -808,7 +808,7 @@ wolfSSL Client Benchmark on TLS13-AES256-GCM-SHA384 with group ML_KEM_1024:
808808
Connect : 50.758 ms
809809
Connect Avg : 2.115 ms
810810
811-
wolfSSL Server Benchmark on TLS13-AES256-GCM-SHA384 with group P256_ML_KEM_512:
811+
wolfSSL Server Benchmark on TLS13-AES256-GCM-SHA384 with group SecP256r1MLKEM512:
812812
Total : 6029312 bytes
813813
Num Conns : 24
814814
Rx Total : 971.832 ms
@@ -817,7 +817,7 @@ wolfSSL Server Benchmark on TLS13-AES256-GCM-SHA384 with group P256_ML_KEM_512:
817817
Tx : 381.096 MB/s
818818
Connect : 54.727 ms
819819
Connect Avg : 2.280 ms
820-
wolfSSL Client Benchmark on TLS13-AES256-GCM-SHA384 with group P256_ML_KEM_512:
820+
wolfSSL Client Benchmark on TLS13-AES256-GCM-SHA384 with group SecP256r1MLKEM512:
821821
Total : 6029312 bytes
822822
Num Conns : 24
823823
Rx Total : 972.623 ms
@@ -827,7 +827,7 @@ wolfSSL Client Benchmark on TLS13-AES256-GCM-SHA384 with group P256_ML_KEM_512:
827827
Connect : 52.613 ms
828828
Connect Avg : 2.192 ms
829829
830-
wolfSSL Server Benchmark on TLS13-AES256-GCM-SHA384 with group P384_ML_KEM_768:
830+
wolfSSL Server Benchmark on TLS13-AES256-GCM-SHA384 with group SecP384r1MLKEM768:
831831
Total : 5767168 bytes
832832
Num Conns : 23
833833
Rx Total : 921.217 ms
@@ -836,7 +836,7 @@ wolfSSL Server Benchmark on TLS13-AES256-GCM-SHA384 with group P384_ML_KEM_768:
836836
Tx : 355.285 MB/s
837837
Connect : 69.367 ms
838838
Connect Avg : 3.016 ms
839-
wolfSSL Client Benchmark on TLS13-AES256-GCM-SHA384 with group P384_ML_KEM_768:
839+
wolfSSL Client Benchmark on TLS13-AES256-GCM-SHA384 with group SecP384r1MLKEM768:
840840
Total : 5767168 bytes
841841
Num Conns : 23
842842
Rx Total : 923.622 ms
@@ -846,7 +846,7 @@ wolfSSL Client Benchmark on TLS13-AES256-GCM-SHA384 with group P384_ML_KEM_768:
846846
Connect : 63.739 ms
847847
Connect Avg : 2.771 ms
848848
849-
wolfSSL Server Benchmark on TLS13-AES256-GCM-SHA384 with group P521_ML_KEM_1024:
849+
wolfSSL Server Benchmark on TLS13-AES256-GCM-SHA384 with group SecP521r1MLKEM1024:
850850
Total : 5767168 bytes
851851
Num Conns : 23
852852
Rx Total : 920.447 ms
@@ -855,7 +855,7 @@ wolfSSL Server Benchmark on TLS13-AES256-GCM-SHA384 with group P521_ML_KEM_1024:
855855
Tx : 355.548 MB/s
856856
Connect : 78.446 ms
857857
Connect Avg : 3.411 ms
858-
wolfSSL Client Benchmark on TLS13-AES256-GCM-SHA384 with group P521_ML_KEM_1024:
858+
wolfSSL Client Benchmark on TLS13-AES256-GCM-SHA384 with group SecP521r1MLKEM1024:
859859
Total : 5767168 bytes
860860
Num Conns : 23
861861
Rx Total : 921.889 ms

0 commit comments

Comments
 (0)