Update post-quantum open items

This commit is contained in:
JackDoan committed 2026-10-14 12:37:30 -05:00
1 parent e7b2abb0b2
commit a508a4e22c
1 file changed
+7 -4
+7 -4
View File
@@ -454,9 +454,12 @@ in every scenario above, and within three at least 99.99%.
## Open items ## Open items
- Publish DefinedNet/noise, or upstream the hybrid patterns, and drop the `replace` in `go.mod`. - Publish DefinedNet/noise and drop the `replace` in `go.mod`, once Nate says the fork is ready to
The classical-only responder `e` is on the local clone's `drop-responder-ekem-key` branch ship. The classical-only responder `e` is on the local clone's `drop-responder-ekem-key` branch
(b4a892b), not yet in DefinedNet/noise. (b4a892b), not yet in DefinedNet/noise.
- Cryptographic review of the hybrid composition and of the v3 certificate signatures. - Cryptographic review of the hybrid composition and of the v3 certificate signatures.
- A tunnel that came up classical between two v3 holders (say, the hybrid attempt was dropped) - Field test of hybrid handshakes on real hosts, as was done for phase 1.
stays classical until it rehandshakes for another reason.
Accepted as is: a tunnel that came up classical between two v3 holders (say, the hybrid attempt
was dropped) stays classical until it rehandshakes for another reason. `require`, `sticky` and a
CA pool without v2 forms cover deployments that need more. PKCS#11 keys do not support v3.