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.

Bug 2070610

Summary: Consider enabling sntrup761x25519-sha512@openssh.com in LEGACY, DEFAULT and FUTURE
Product: Red Hat Enterprise Linux 9 Reporter: Alexander Sosedkin <asosedki>
Component: crypto-policiesAssignee: Alexander Sosedkin <asosedki>
Status: CLOSED DEFERRED QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: medium    
Version: 9.1CC: omoris, pmendezh, ssorce
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-11 12:31:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2070604    
Bug Blocks:    

Description Alexander Sosedkin 2022-03-31 14:15:01 UTC
Once we add support for enabling 'sntrup761x25519-sha512' kex in bz2070604,
we should also consider enabling it by default.

OpenSSH already has support for it the version shipped in RHEL 9.0 and
it will be the default in the next OpenSSH version (>8.9) as per:
https://github.com/openbsd/src/commit/0726d1207d0c034cb9acde3ff0b12c3afc772e37.

Comment 3 Alexander Sosedkin 2022-04-11 12:31:53 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=2070604#c5:
  Until there are algorithms selected by the NIST PQC competition we will not be enabling any post-quantum algorithms by default (or semi-default, like with LEGACY, FUTURE or FIPS policies).

https://bugzilla.redhat.com/show_bug.cgi?id=2073387#c2:
  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.