Hi Rob,
Would you like to have a quick chat to discuss the options? If you would feel free to reach out,
martin.evans1@ibm.comRegards,
Martin
------------------------------
Regards,
Martin Evans
IBM MQ Technical Product Manager
------------------------------
Original Message:
Sent: Tue November 29, 2022 08:56 PM
From: Rob Anderson
Subject: .NET MQ Client TLS 1.3 support
Thank you for the update Martin. QQ. What are the alternatives, if we need a client to connect to a queue manager using TLS 1.3?
------------------------------
Rob Anderson
Original Message:
Sent: Wed October 05, 2022 03:29 AM
From: Martin Evans
Subject: .NET MQ Client TLS 1.3 support
Hi Daniel,
We are working towards support for TLS 1.3 for .NET clients, but we haven't committed to a date for it yet.
------------------------------
Regards,
Martin Evans
IBM MQ Technical Product Manager
Original Message:
Sent: Wed September 28, 2022 11:34 AM
From: Daniel Bolin
Subject: .NET MQ Client TLS 1.3 support
I'm looking for a way to use TLS 1.3 in the .NET MQ or XMS client packages for a .net 6 app. The current .NET MQ managed client (v9.3.0) uses .NET Framework and support only goes up to TLS 1.2:- "The managed .NET client uses the Microsoft.NET Framework libraries to implement TLS secure socket protocols." - .NET managed TLS support
- "Based on the SSLCipherSpec value, the SSLProtocol version can be TLS 1.0, or TLS 1.2, depending on which version of the Microsoft.NET Framework you are using." - .NET managed client support cipher specs
Microsoft has add full support for TLS 1.3 with .net 6, so I'm also hoping that IBM is working to add TLS 1.3 support in their own .NET and XMS clients. Is there any recent news to say that IBM is working on this? And are there any workarounds to get a TLS 1.3 connection in a .NET MQ app? The .NET MQ unmanaged client uses a different library for TLS connections, but I believe the unmanaged mode is only available in a full client (not available in the nuget packages that IBM provides for .net).