Hi,

On 8 January 2018 at 03:21,  <selva.n...@gmail.com> wrote:
> I am not sure how receptive the crypto maintaineres are to the
> idea of adding more code into cryptoapi.c, but here goes:
>
> I've been wanting to add TLS 1.2 support for certs in the
> Windows cert store using management external key. But that's
> a lot more work than extending cryptoapicert support. And,
> rather surprsingly, it turns out that the CNG API for signing is
> easy to use (well after some groping in the dark..) and doesn't
> take much to implement.
>
> So these patches..
>
> The first patch is not really related and to make the existing code
> "openssl-1.1 ready" (missed by past patches as no one probably builds
> Windows binary with 1.1..).
>
> The second patch is not dependent on this, but close-by code paths
> are touched by both.

This would fix a major shortcoming in our current cryptoapi code, so
I'm definitely open to accepting these patches. Just need to find some
time to do the review and dreaded windows testing :)

I actually tried this myself a while ago, but quickly gave up after
getting lost in and demotivated by the MSDN maze. So more than
grateful that you wrestled your way through!

-Steffan

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to