On Sat, 5 May 2018, Antenore wrote:
Maybe asks publicly what are the reasons, so that if are just technical, you can push for improvements.
The reasons are actually stated in the page I linked to: libssh has some features that libssh2 lacks (I think that refers to crypto algos) and apparently curl was about the only package left in Redhat that used libssh2.
Redhat put in a lot of effort when they provided the libssh-using backend to curl a while back so that we can now chose to use either library at build-time and curl works just the same for SCP and SFTP transfers.
I personally don't have any actual technical argument against this decision. I have an emotional attachment to and argument for libssh2 of course but I don't think that's very helpful...
-- / daniel.haxx.se _______________________________________________ libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
