On 04/28/2014 04:45 AM, Tom_Z wrote:
Hi guys,
while looking at NMS we found that in SslTransport.cs
<http://svn.apache.org/viewvc/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/trunk/src/main/csharp/Transport/Tcp/SslTransport.cs>
it is hard coded to use 'SslProtocols.Default' which points to TLS 1.0 only
(see API
<http://msdn.microsoft.com/en-us/library/system.security.authentication.sslprotocols%28v=vs.110%29.aspx>
).
How can we force the usage of TLS 1.1 or higher while connecting via NMS to
the broker?
Thanks,
Tom
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Apache-NMS-using-other-SSL-TLS-Version-rather-than-SslProtocols-Default-tp4680612.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
You have two options
1. Change the source locally to what you want and build your own client
libraries.
2. Submit a patch to a Jira ticket that allows setting the value while
keeping the current setting as the default. The patch should provide a
means of mapping a URI option to the appropriate enum value keeping in
mind that the 1.1 and 1.2 TLS entries are only valid on .NET 4.5+
--
Tim Bish
Sr Software Engineer | RedHat Inc.
[email protected] | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
