I follow libssh since many years now, mainly in the shadow.
Don't take this the wrong way, both projects have advantages and defects.
Please keep going, we love you!
Maybe asks publicly what are the reasons, so that if are just technical, you can push for improvements.
If the reasons are around the licensing, well that's life, their choice
On May 5, 2018 6:31:10 PM UTC, Will Cosgrove <will_at_panic.com> wrote:
>This is disappointing, but not surprising, given the lack of modern
>cryto support. I hope my ECDSA/ED25519 key support and up-coming etm
>and chacha20 support will help spur renewed interest in maintaining the
>library.
>
>Will
>
>> On May 5, 2018, at 5:45 AM, Peter Stuge <peter_at_stuge.se> wrote:
>>
>> Daniel Stenberg wrote:
>>> ... instead of libssh2.
>>>
>>> Info:
>>>
>>> https://fedoraproject.org//wiki/Changes/libssh-in-libcurl
>>
>> This is typical behavior from Red Hat, as expected given their
>> position as a Linux vendor.
>>
>> The sad part of the story is how distributions often demonstrate
>> utter disinterest in choice, diversity and information. When one
>> major distribution makes some change it's a pretty sure bet that
>> most other will copy shortly thereafter.
>>
>> For libssh2 I guess this means Kamil's contribution will end - sorry
>> to see you leave the project Kamil - thanks for your work so far!
>>
>>
>> //Peter
>> _______________________________________________
>> libssh2-devel
>https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
>
>
>_______________________________________________
>libssh2-devel
>https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
_______________________________________________
libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2018-05-05