Re: F28 System Wide Change: Switch libcurl to use libssh instead of libssh2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday, December 4, 2017 3:31:32 PM CET Michael Cronenworth wrote:
> On 12/04/2017 07:47 AM, Jan Kurik wrote:
> 
> > libcurl currently uses libssh2 to implement the SSH layer of SCP and
> > SFTP protocols. The libssh2 library uses outdated crypto algorithms
> > and lacks important features like GSS-API authentication. After
> > implementing this change, libcurl will use the libssh library instead,
> > which is now more secure, feature-complete, and with more active
> > upstream community.
> 
> 
> They are both equally active.

How are you backing up your statement?

If we count upstream commits in 2017, I see 93 commits in libssh whereas
only 13 commits in libssh2 (including two commits authored by me).

> If you were worried about ECDSA support, guess what?
> Libssh2 now supports it:
> 
> https://github.com/libssh2/libssh2/issues/41

You are not referring to any upstream commit.  The link above points to a 
Github issue, which is open since September 2015 and without any progress 
since September 2017.

Kamil
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux