Having both version in the same process can only raise strange failure $ rpm -q --requires libvirt-libs | grep ssh libssh.so.4()(64bit) libssh2.so.1()(64bit) $ rpm -qf /usr/lib64/libssh.so.4 libssh-0.7.5-4.fc27 (x86_64) $ rpm -q --requires libssh | grep crypto libcrypto.so.10()(64bit) libcrypto.so.10(OPENSSL_1.0.1_EC)(64bit) libcrypto.so.10(libcrypto.so.10)(64bit) libk5crypto.so.3()(64bit) $ rpm -qf /usr/lib64/libssh2.so.1 libssh2-1.8.0-5.fc27 (x86_64) $ rpm -q --requires libssh2 | grep crypto libcrypto.so.1.1()(64bit) libcrypto.so.1.1(OPENSSL_1_1_0)(64bit)
There's nothing libvirt can do about this, because the openssl deps are pulled in by a third party library. We need libssh to update to the modern openssl 1.1 too.
It seems than debian use a 0.8.0 git snapshot which have support for OpenSSL 1.1
libssh-0.7.5-6.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-513481e672
I confirm, everything seems ok now $ rpm -q libssh libssh-0.7.5-6.fc27.x86_64 $ rpm -q --requires libssh | grep crypto libcrypto.so.1.1()(64bit) libcrypto.so.1.1(OPENSSL_1_1_0)(64bit) libk5crypto.so.3()(64bit) Also inherited on consumers $ ldd /usr/lib64/php/modules/libvirt-php.so | grep crypto libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007fa3f5d61000) libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007fa3f54c6000) Thanks a lot
libssh-0.7.5-6.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-513481e672
libssh-0.7.5-6.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.