Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
https://www.openssh.com/txt/release-9.0 states:

--- 8< ---
 * ssh(1), sshd(8): use the hybrid Streamlined NTRU Prime + x25519 key
   exchange method by default ("sntrup761x25519-sha512").
   The NTRU algorithm is believed to resist attacks enabled by future
   quantum computers and is paired with the X25519 ECDH key exchange
   (the previous default) as a backstop against any weaknesses in
   NTRU Prime that may be discovered in the future. The combination
   ensures that the hybrid exchange offers at least as good security
   as the status quo.

   We are making this change now (i.e. ahead of cryptographically-
   relevant quantum computers) to prevent "capture now, decrypt
   later" attacks where an adversary who can record and store SSH
   session ciphertext would be able to decrypt it once a sufficiently
   advanced quantum computer is available.
--- 8< ---

As conclusion I would like to see the same behaviour by default in RHEL 9.

Version-Release number of selected component (if applicable):
openssh-8.7p1-8

Actual results:
Other default key exchange method.

Expected results:
Make hybrid Streamlined NTRU Prime + x25519 key exchange method the default (like in OpenSSH 9.0)

Cross-filed case 03193392 at the Red Hat customer portal.

Dear Robert,

Unfortunately, no PQC algorithms are standardized by NIST yet. For our purpose it means that we will not use PQC algorithms by default until they are standardized by NIST.

Dmitry, so that would mean that if CentOS Stream 9 would ship OpenSSH 9.0, you would have patched it to change the upstream default (to the previous default) for the same reason as well?

Dear Robert,

Unfortunately, we aren't going to implement or enable by default any crypto algorithm unapproved by Standard Authority, because such approval is required to be sure that this algorithm is secure enough. There are many PQ crypto algorithms but until it is approved by a corresponding Standard Body, we don't want provide any of them by default.

Thank you for the clarification! :)