From 472fd9f1c5421ce611ecb4f73b73eb1fb255418d Mon Sep 17 00:00:00 2001 From: Stefan Becker Date: Thu, 9 Feb 2012 22:05:21 +0200 Subject: [PATCH] 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. --- src/core/sip-sec-sspi.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/core/sip-sec-sspi.c b/src/core/sip-sec-sspi.c index c8bad7ff..97dff01f 100644 --- a/src/core/sip-sec-sspi.c +++ b/src/core/sip-sec-sspi.c @@ -3,7 +3,7 @@ * * pidgin-sipe * - * Copyright (C) 2011 SIPE Project + * Copyright (C) 2011-12 SIPE Project * Copyright (C) 2009 pier11 * * @@ -44,7 +44,7 @@ #define SSPI_MECH_NTLM "NTLM" #define SSPI_MECH_KERBEROS "Kerberos" #define SSPI_MECH_NEGOTIATE "Negotiate" -#define SSPI_MECH_TLS_DSK "TLS-DSK" /* educated guess :-) */ +#define SSPI_MECH_TLS_DSK "Schannel" /* SSL/TLS provider, is this correct? */ #ifndef ISC_REQ_IDENTIFY #define ISC_REQ_IDENTIFY 0x00002000 -- 2.11.4.GIT