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.

Created attachment 1888547 [details]
Pictrure of the error log on the server.

Description of problem:
After enable password log in (PermitRootLogin yes) the log in fails with an crypto error.

Version-Release number of selected component (if applicable):
openssh-server-8.7p1-7.el9

How reproducible:
Every time


Steps to Reproduce:
1. Enable "PermitRootLogin yes"
2. restart the service
3. try to login

Actual results:
The log in fails from an remote system. (See picture)



Expected results:
Working SSH connection.


Additional info:
Using an local login will work. (ssh root@localhost)
The remote system is using Fedora 35.

Created attachment 1888548 [details]
The debug log on the client

Created attachment 1888549 [details]
Nmap scan of the server

I assume this is a client misconfiguration and duplicate of a bug #2088750. I think you have somwhere in the client configuration written HostkeyAlgorithms ssh-rsa, which is no longer supported in RHEL9.

Yes it was and missing cipher, but the error message is strange. Better will be an message like "Cipher error: requested foo available bar". Because the error only happens after enter the correct password. When using an wrong one, the error will not happens.

I agree that the error message is weird. Hopefully we will improve the diagnostics, but I close the bug as a duplicate.

*** This bug has been marked as a duplicate of bug 2088750 ***