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

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

From: Marc Hoersken <info_at_marc-hoersken.de>
Date: Wed, 19 Mar 2014 06:25:36 +0100

On 19. März 2014 01:45:44 MEZ, Alexander Lamaison <swish_at_lammy.co.uk> wrote:
>On 18 March 2014 22:01, Alexander Lamaison <swish_at_lammy.co.uk> wrote:
>I see that wincng.h/c import bcrypt.h unconditionally, but wincrypt.h
>conditionally? Is this difference intentional? Can the WinCNG
>backend work without wincrypt.h and crypt32.lib, or should it be
>all-or-nothing?

It is intentional. The WinCNG backend requires bcrypt, but can work without wincrypt. Loading keys from files is disabled in that case. Please take a look at the ifdefs later in the code.

I am looking forward to the CMake files.

_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2014-03-19