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:
curve25519-sha256 is not compatible with DEFAULT profile (and perhaps others)

Version-Release number of selected component (if applicable):
RHEL-8.0.0-20190213.0
# rpm -q crypto-policies openssh
crypto-policies-20181217-5.git9a35207.el8.noarch
openssh-7.8p1-4.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. ssh -o KexAlgorithms=curve25519-sha256 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no localhost

Actual results:
Unable to negotiate with ::1 port 22: no matching key exchange method found. Their offer: curve25519-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1

Expected results:
Connects normally.

Additional info:
This is regression against RHEL-7, so we need to at least document it as known issue. Not a blocker material.

Mirek, can we document it as known issue in RHEL-8.0?
Do we need a separate bug for the documentation?

Verify test runs in CI: https://baseos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-openstack/29584//console

[10.0.132.116        ] T:       5 [-ciphers-in-practice-do-not-meet-the-stated] Running
[10.0.132.116        ] 1562575727 [Setup                                      ] PASS Score: 0
[10.0.132.116        ] 1562575728 [Test-available-ciphers                     ] PASS Score: 0
[10.0.132.116        ] 1562575729 [Test-available-macs                        ] PASS Score: 0
[10.0.132.116        ] 1562575730 [KEX-algorithms                             ] PASS Score: 0
[10.0.132.116        ] 1562575731 [Key-types                                  ] PASS Score: 0
[10.0.132.116        ] 1562575732 [Cleanup                                    ] PASS Score: 0
[10.0.132.116        ] T:       5 [-ciphers-in-practice-do-not-meet-the-stated] Completed: PASS

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3644