Kasper Laudrup

@anarthal Thanks. First of all I was mostly interested in knowing whether it might make sense to even try getting it included but I guess the mailing list might be...

> I think Boost.Wintls fits well into Boost. I am not windows user, but as you have seen above there are people that don't want to depend on openssl on...

>Boost.WinTLS seems not to compile as CERT_CHAIN_ENGINE_CONFIG lacks hExclusiveRoot. That member only exists if NTDDI_VERSION >= NTDDI_WIN7 (0x06010000). The only explanation: NTDDI_VERSION Not sure if this is relevant for you...

@jens-diewald First of all thanks a lot for this PR. I really appreciate it. Regarding the implementation of the handshake as a coroutine I had a lot of help from...

@jens-diewald So sorry for the late reply and thanks once again for your pull request. I would definitely like this to work with boost versions earlier than the latest. A...

Hi @jens-diewald, So sorry for not having looked at this for ages. I haven't really looked at this library for quite some time. Is this still something you'd like me...

@madmongo1 has said he'll have a look at this when time permits. Hope we can get this merged.

@InternalHigh I guess it's up to you to complete this @jens-diewald :-)

Hi @windowsair Sorry for the very late reply. It seems like you are right that this does not work when building on Windows 2022 where TLS 1.3 ought to be...

I have not been able to reproduce this issue. The way the SSPI headers are included [here](https://github.com/laudrup/boost-wintls/blob/0077d733984f84a2a85e216ced29f73b173ae472/include/wintls/detail/sspi_types.hpp#L16) should ensure that the non wide-character versions of the functions are being used....