| commit | 472fd9f1c5421ce611ecb4f73b73eb1fb255418d | |
| author | Stefan Becker <chemobejk@gmail.com> | |
| Thu, 9 Feb 2012 20:05:21 +0000 (9 22:05 +0200) | ||
| committer | Stefan Becker <chemobejk@gmail.com> | |
| Thu, 9 Feb 2012 20:05:21 +0000 (9 22:05 +0200) | ||
| tree | de8baa084fe2535616d9b7016f4506a015015ef8 | treesnapshot (tar.gz zip) |
| parent | 02e96dfb2a724e6bdf810d7a2f22b98164bcaaae | commitdiff |
sspi: use "Schannel" as TLS-DSK provider
This is a much better educated guess then the previous choice, because
Schannel is the SSL/TLS provider for Windows programs. It still doesn't
work, but at least we no longer fail with
AcquireCredentialsHandleA: The requested security package does not exist
To get this working we will most likely have to figure out how to pass
the client certificate, which is stored in NSS binary format, down to
the SSPI layer in a form that Schannel will accept.
This is a much better educated guess then the previous choice, because
Schannel is the SSL/TLS provider for Windows programs. It still doesn't
work, but at least we no longer fail with
AcquireCredentialsHandleA: The requested security package does not exist
To get this working we will most likely have to figure out how to pass
the client certificate, which is stored in NSS binary format, down to
the SSPI layer in a form that Schannel will accept.
| src/core/sip-sec-sspi.c | diffblobblamehistory |