Subject: Re: [PATCH] Added Windows Cryptography API: Next Generation backend

Re: [PATCH] Added Windows Cryptography API: Next Generation backend

From: Alexander Lamaison <>
Date: Tue, 18 Mar 2014 22:11:18 +0000

On 18 March 2014 22:03, Daniel Stenberg <> wrote:
> On Tue, 18 Mar 2014, Alexander Lamaison wrote:
>> However, I've been planning a compromise solution for ages, where the API
>> is changed to wider types conditional upon some #define such as #ifdef
>> LIBSSH2_USE_LATEST_API. That lets you take advantage of the fix, as long as
>> you are willing to compile libssh2 yourself. On Windows that means
>> everyone.
> Yeah, I'd like that too. Then we could polish that for a year or two and
> then one day we just decide enough is enough and we do libssh2 version 2
> with a new ABI and remove the old API...

It's fairly high up my todo list as the hundreds of warnings
completely drown out any real problems with unrelated code. That
said, also on my libssh2 todo list is the CMake build work, a new
Boost.Test-based test suite against a real server and getting
continuous integration set up with Travis CI. So, if anyone else
wants to take this one on, don't be shy.


Swish - Easy SFTP for Windows Explorer (
Received on 2014-03-18