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.
The None cipher/mac is certainly no-go. The SSH is secure shell and implementing none cipher and mac is explicitly not recommended by RFC4253 [1]. If you want to transfer files in plaintext, please use ftp or something like that.
I think the concerns stated in the bug #537198 still apply. Reading through the patches (not clear if you want just the first HPN one or some others) [2], it is several thousands lines long and really the only performance improvement that is viable would be the multi-threaded AES-CTR cipher, some buffer sizes and dynamic windows, which might be something we can consider to push upstream and maybe downstream, if there will be no other concerns.
The question is how this would work for FIPS/CC certifications, as mutli-threaded encryption is not common out there. Simo?
Maintaining two versions of OpenSSH is not something we have a cycles to do either.
[1] https://datatracker.ietf.org/doc/html/rfc4253#page-11
[2] https://sourceforge.net/projects/hpnssh/files/Patches/HPN-SSH%2015v2%208.5p1/