Also, it would have been good to start with the RFC8446bis as -00 so that one could more easily see what are the changes.
On Tue, Sep 30, 2025 at 9:22 PM Bocai Zhou
<[email protected]> wrote:
This approach is designed to establish a cleaner, unambiguously
secure, and sustainable foundation for PQC-era deployments.
Could the claim of "unambiguously secure" be substantiated? Is there any
ongoing formal analysis for this draft? If so, please point me to that.
*
Mandatory Hybrid Authentication: To effectively mitigate
potential downgrade and substitution attacks in the long term,
the design requires hybrid authentication to utilize two
distinct certificate chains—one classical and one PQC.
Crucially, these chains must be cryptographically linked
(e.g., through cross-signatures or a Certified Linking X.509
Extension). The CertificateVerify message is accordingly
updated to mandate the inclusion and validation of both
signatures over the identical transcript hash.
What exactly does "effectively" mean here? Is the claim that the
proposed TLS 1.4 is better compared to an extension of TLS 1.3? If so, I
would like to see some formal reasoning for that.
-Usama
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
