SSL implementation on Windows?

[GoogleCodeExporter]

What steps will reproduce the problem?
base/sslidentity.cc
base/sslstreamadapter.cc
#if SSL_USE_SCHANNEL
#error "Not implemented yet"

What version of the product are you using? On what operating system?
libjingle 0.5.1 on Windows 7

Please provide any additional information below.
Any timeline as to when SSL will be implemented for Windows?
Thanks.

Original issue reported on code.google.com by dqaminh16@gmail.com on 30 Oct 2010 at 11:02

[GoogleCodeExporter]

According to the libjingle document, SSL should be supported on Windows 
platforms.
SSL Support

libjingle supports two types of SSL:

    * OpenSSL (for UNIX)
    * SChannel (for Windows)

To use SSL, you must perform the following steps:

   1. #define FEATURE_ENABLE_SSL (in the Visual Studio project, this value is defined in the project settings, not in the code).
   2. Ensure that either SSL_USE_OPENSSL or SSL_USE_SCHANNEL are #defined in ssladapter.cc. One of these should be defined by default, depending on the build settings for your operating system.
   3. Call InitializeSSL to initialize required components. This function is defined in ssladapter.cc. When the application closes down, call CleanupSSL. You do not need to call InitializeSSLThread (it is used internally by InitializeSSL).

For details, please refer to:
http://code.google.com/apis/talk/libjingle/important_concepts.html

Original comment by jun...@google.com on 3 Nov 2010 at 4:54

[GoogleCodeExporter]

Another note, as far as the specific issue you pointed out, quote:
"base/sslidentity.cc
#if SSL_USE_SCHANNEL
#error "Not implemented yet"
"
this is for P2P only, which hasn't been implemented.

Original comment by jun...@google.com on 3 Nov 2010 at 6:36

[GoogleCodeExporter]

Original comment by pthatc...@google.com on 3 Nov 2010 at 7:16

• Changed state: Done

[GoogleCodeExporter]

> Another note, as far as the specific issue you pointed out, quote:
> "base/sslidentity.cc
> #if SSL_USE_SCHANNEL
> #error "Not implemented yet"
> "
> this is for P2P only, which hasn't been implemented.

Thanks for the response. I ran into this issue when I was trying to compile 
libjingle as a DLL. The linker couldn't resolve references to sslstreamadapter 
and sslidentity.

How might I minimally modify these source files so that the linker stops 
complaining (and generates a DLL)? I really don't mind that the workaround will 
be a hack (i.e. linking symbols that don't have a working implementation), 
because I won't be using the feature.

I'm attaching here the modified libjingle.scons file that I'm using to build 
the DLL, and the linker error messages from scons's build log.

Thanks.

Original comment by dqaminh16@gmail.com on 8 Nov 2010 at 12:47

Attachments:

• scons_buildlog.txt
• libjingle.scons

[GoogleCodeExporter]

But now, GTalk have using TLSv1.0 as connection security solution. If, there is 
no TLS  implemented in Windows, login sample also can not work. Is that so?

Original comment by spidder2...@gmail.com on 6 Mar 2011 at 3:34