Adding hotfix that will ensure any secure connections use TLS instead of SSLv3

Ran into this problem while applying STIGs to Windows Server 2008 R2.  If you enable the Group Policy to enforce FIPS compliant connections, any connection attempted by the .NET RabbitMQ client using the default protocol of SSLv3 will fail to complete.

This change resolves this issue by setting the protocol to TLSv1 thus complying with FIPS.

If you'd like I could run git flow finish hotfix/amp-3.2.2 and do a push up to master.