• Xamarin.AsyncTests from the martin-newtls branch. This is included as a submodule.

• Mono 4.0 must be installed as system-default Mono in /Library/Frameworks/Mono.framework.

  This is required because some internals in the binary serialization format have changed, which Xamarin Studio uses to communicate to the external mdtool build process when building against a custom runtime.

• Mono from the work-newtls branch installed into a custom prefix.

  At the moment, this custom prefix must be /Workspace/INSTALL - this is unfortunately hardcoded in the native Xcode project at the moment.

  FIXME: To use a different prefix, need to make sure we find the openssl shared libraries at runtime.

  This version of Mono must be selected as current runtime in Xamarin Studio (go to Preferences / .NET Runtime to install it, then select via Project / Active Runtime ...).

• Shared-library build of OpenSsl 1.0.1.

  The default version of OpenSsl on OS X is too old and it's also not built as shared library. You need to download the openssl 1.0.1 sources, then configure and compile with:

    $ ./config -t
    $ ./Configure darwin-i386-cc --prefix=/Workspace/INSTALL -shared
    $ make
    $ make install

For full debugging use

    $ make CC='cc -g -O0 -DKSSL_DEBUG -DNDEBUG -DCRYPTO_MDEBUG -DTLS_DEBUG'

• Xcode

• Build the native library with

  $ make -f Makefile.native

• Open MartinsPlayground.sln in Xamarin Studio and select /Workspace/INSTALL as current runtime.

For Android and iOS you will need a custom build of Xamarin.Android / Xamarin.iOS with Mono from the work-newtls branch. You also need to build mcs/class/Mono.Security.Providers and install the binaries.

See mcs/class/Mono.Security.Providers/README.md for an overview of the new Mono.Security.Interface APIs.

The new TLS code requires Microsoft's SslStream implementation from the referencesource, the corresponding files are:

• System/Net/SecureProtocols/SslStream.cs
• System/Net/SecureProtocols/_SslStream.cs
• System/Net/SecureProtocols/_SslState.cs
• System/Net/_SecureChannel.cs

Main bridge between their code and ours is mcs/class/System/ReferenceSources/SSPIWrapper.cs.

All these classes are currently not built into System.dll, but into Mono.Security.Providers.NewSystemSource.dll.

Main bridge between our code and theirs is Mono.Security.Providers.NewTls.MonoNewTlsStreamFactory.

The Mono.Security.Providers.NewTls module uses advanced extern alias compilation magic to create an instance of their SslStream class from the Mono.Security.Providers.NewSystemSource module (again, this uses advanced extern alias compilation magic).

This Mono.Security.Providers.NewTls module provides an implementation of Mono.Security.Interface.MonoTlsProvider, which is then registered with the MonoTlsProviderFactory, a new public Mono.Security.dll (System.dll on Mobile) API.

When Mono's existing web-stack attempts to make a TLS call, it will query MonoTlsProviderFactory for the current provider, so it can use the new implementation. (FIXME: this is not done yet) (FIXME: the factory is currently per-process and needs to be set at application startup).

To use the new code, an application needs to call

MonoTlsProviderFactory.InstallProvider (new NewTlsProvider ());

See web-tests/README.md for a detailed overview of the test framework.

The platform-specific test implementation is Mono.Security.NewTls.TestProvider. This project currently exists in two versions: one for the Console and another one.

Due to some strong-name requirements, the actual Android app also needs to be in a different project.

To run the tests on the Console:

1. Build as explained above.
2. Build the Mac GUI. You may need to set the current Mono runtime to the default one for this.
3. Run as explained in the web-tests/README.md, using Mono.Security.NewTls.TestProvider.exe as custom test implementation.

To run the tests on Android, use the Mono.Security.NewTls.Android app. iOS is not done yet, but will come shortly.

Last changed March 13, 2015 Martin Baulig martin.baulig@xamarin.com