Loading...

Linking RHIVOS CVEs to...

Migration: Automation ...

Sync from "Extern...

XML

Word

Printable

Epic Name:
[RHEL EPIC] Test post-quantum cryptography in TLS in RHEL 10.1
Acceptance Criteria:
Hide

Test that:

The hybrid key exchange does not break your use cases.
Common pitfalls may be:

larger size of the key exchange communication

longer duration due to additional computation

your application not using PQC because it does not follow crypto-policies

Your application works with ML-DSA certificates

Your component supports a classic certificate chain and a post-quantum certificate chain at the same time based on the connecting client's preferences for a smooth transition.

See the Recommendation section for details on how to test on https://issues.redhat.com/browse/RHELMISC-11976
Show
Test that: The hybrid key exchange does not break your use cases. Common pitfalls may be: larger size of the key exchange communication longer duration due to additional computation your application not using PQC because it does not follow crypto-policies Your application works with ML-DSA certificates Your component supports a classic certificate chain and a post-quantum certificate chain at the same time based on the connecting client's preferences for a smooth transition. See the Recommendation section for details on how to test on https://issues.redhat.com/browse/RHELMISC-11976
Products:

Red Hat Enterprise Linux

RHEL 10.1 will enable hybrid key exchange with post-quantum cryptography by default in TLS 1.3 connections and pure ML-DSA TLS certificates.

This is expected to be a QE only task, unless issues are found.

is cloned by

RUN-3259 [RHEL EPIC] [QE-Test] Test post-quantum cryptography in TLS in RHEL 10.1