For the WinCNG backend:
This would be great in that I'd have one less open source library (openssl)
to maintain.
I did look into this a bit but came up with too many questions:
Going through openssl.h to see what needed to be done, the hashes were
pretty simple except that LIBSSH2_HMAC_RIPEMD is not supported by WinCNG.
Supporting encryption/signing was less clear to me.
The following are also not supported by WinCNG:
LIBSSH2_AES_CTR
LIBSSH2_BLOWFISH
LIBSSH2_CAST
Modes WinCNG supports for AES:
- ECB
- CBC
- CFB
- CCM
- GCM
Not sure what _libssh2_bn would map to.
My purpose for using libssh2 is to implement SFTP. What does WinCNG need to
provide in order for SFTP to be fully implemented?
-----Original Message-----
From: libssh2-devel [mailto:libssh2-devel-bounces_at_cool.haxx.se] On Behalf Of
Daniel Stenberg
Sent: Wednesday, March 12, 2014 3:44 PM
To: libssh2 development
Subject: Re: [PATCH] Added Windows Cryptography API: Next Generation backend
On Sat, 8 Mar 2014, Marc Hoersken wrote:
> what do you think about making some progress regarding the
> implementation and merge of the Windows Cryptography API: Next Generation
backend.
Can you summerize for us what the outstanding issues/patches are?
-- / daniel.haxx.se _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-develReceived on 2014-03-13