Hi. Yes, by all means! There is a tiny problem though: please go over all GPL-licensed reverse-dependencies of libssh2 (including all the programs which load both a GPL-licensed library and libssh2 indirectly, say, via libcurl), and make sure they all have OpenSSL exception added to their license.
On Mon, 22 Jan 2018, at 10:05, jani wrote: > Package: libssh2-1 > Version: 1.7.0-1 > > If libssh2 was built with gcrypt it leaks memory with every secure > connection call through curl. > > The problem is the same as described here: > https://github.com/libssh2/libssh2/issues/124 > > This leak goes way back, i tested it on jessie, stretch, buster and it > is still present. > > I suggest to build the libssh with open-ssl, because it solves the > memory leak problem. > > I am using Linux 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) > x86_64 GNU/Linux and libc6 2.24-11+deb9u1
