Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
tfm-rubygem-net-ssh-4.2.0-1.el7sat.noarch provides:
diffie_hellman_group14_sha1.rb
diffie_hellman_group1_sha1.rb
diffie_hellman_group_exchange_sha1.rb
diffie_hellman_group_exchange_sha256.rb
ecdh_sha2_nistp256.rb
ecdh_sha2_nistp384.rb
ecdh_sha2_nistp521.rb
Requesting curve25519sha256 be included in supported kex.
Version-Release number of selected component (if applicable):
tfm-rubygem-net-ssh-4.2.0-1
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
curve25519sha256 is not supported with remote execution through Satellite as the Net::SSH module is used.
Expected results:
Additional info:
Also for transparency:
Upgrading to net-ssh-6.0.0 will be tricky. There were a lot of changes since the release we currently ship and some of the other gems we use (fog and friends) have not caught up yet. We are looking into alternative approaches to dealing with this, such as not using net-ssh and using a libssh wrapper or using system's ssh binary directly. It will most likely be a bumpy ride, but we'll get there eventually
Will align this to 7.0 as we move away from net-ssh. This will not be implemented in the Satellite 6.* release timeline.
The solution to this RFE will be the removal of net-ssh from Satellite and utilizing ssh more natively, going to reword the RFE to reflect this as the subject of the RFE is stating the solution which isn't the direction we are taking.
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 (Moderate: Satellite 6.11 Release), 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/RHSA-2022:5498