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 905513 - Disable libssh2 transport support
Summary: Disable libssh2 transport support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-29 14:42 UTC by Jiri Denemark
Modified: 2014-06-18 00:44 UTC (History)
9 users (show)

Fixed In Version: libvirt-1.0.2-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 10:01:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jiri Denemark 2013-01-29 14:42:38 UTC 
Description of problem:

libssh2 transport is implemented upstream but it is not stable/usable enough to be supportable in RHEL 7.0.

Version-Release number of selected component (if applicable):

libvirt-1.0.1-1.el7

How reproducible:

100%

Steps to Reproduce:
1. virsh -c qemu+libssh2://127.0.0.1/system list
  
Actual results:

The command succeeds.


Expected results:

The command should fail with the following message:

error: libssh2 transport support was not enabled: Function not implemented
error: failed to connect to the hypervisor

Additional info:
Comment 1 Daniel Berrangé 2013-01-29 15:00:12 UTC 
(In reply to comment #0)
> Description of problem:
> 
> libssh2 transport is implemented upstream but it is not stable/usable enough
> to be supportable in RHEL 7.0.

Please provide links with details of the problems seen, so that when someone looks at this bug in a year's time, we know what motivated us to disable it in the first place.
Comment 2 Jiri Denemark 2013-01-30 10:48:19 UTC 
Dave/Peter can you shed some light on that?
Comment 3 Peter Krempa 2013-01-30 11:03:03 UTC 
One of the main problems is caused by the incomplete support for host keys stored in the known_hosts file. Libssh2 doesn't support ECDSA keys and corrupts the known hosts file containing those. Commit

commit 225f280744e38fae883bd289ef34bb3f6db71c10
Author: Peter Krempa <pkrempa>
Date:   Tue Aug 21 17:54:26 2012 +0200

    client: Change default location of known_hosts file for libssh2 layer
    
    Unfortunately libssh2 doesn't support all types of host keys that can be
    saved in the known_hosts file. Also it does not report that parsing of
    the file failed. This results into truncated known_hosts files where the
    standard client stores keys also in other formats (eg.
    ecdsa-sha2-nistp256).
    
    This patch changes the default location of the known_hosts file into the
    libvirt private configuration directory, where it will be only written
    by the libssh2 layer itself. This prevents trashing user's known_host
    file.

workarounds that partially by using a separate known_hosts file, but this solution isn't ideal.
Comment 6 Huang Wenlong 2013-02-04 08:24:44 UTC 
Verify this bug :
libvirt-1.0.2-1.el7.x86_64

# virsh -c qemu+libssh2://127.0.0.1/system list
error: failed to connect to the hypervisor
error: libssh2 transport support was not enabled: Function not implemented
Comment 8 Ludek Smid 2014-06-13 10:01:08 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.