TLS v1.3

Mar 2, 2015 at 11:22 PM

Greate work with SuperSocket. It really helped us.

So, we've configured SS to required TLS, which was really easy as stated here

Our problem is that we need enable TLV v1.3 but SS only allows 1.0.

Is there a way to do it?

Best regards,
Mar 3, 2015 at 7:48 AM
Sorry for the mistake. I meant TLS v1.2.

Mar 4, 2015 at 6:42 PM
Edited Mar 4, 2015 at 6:43 PM
You would try to insert the following 4 lines into SocketEngine\AsyncStreamSocketSession.cs (after 214 line)
                case (SslProtocols.Tls12):
                                    SslStream tlsStream = CreateSslStream(certConfig);
                                    result = tlsStream.BeginAuthenticateAsServer(AppSession.AppServer.Certificate, certConfig.ClientCertificateRequired, SslProtocols.Tls | SslProtocols.Tls12, false, asyncCallback, tlsStream);
Mar 5, 2015 at 5:52 AM

Can I do a push request so you can merge it on the NuGEt package? We cant use your code directly, only the NuGet. Sorry, company policy.

If its OK i can do it right now.


Sent from Outlook

Mar 5, 2015 at 2:35 PM
I have made a fix, please get the latest code in the 1.6 branch.
Mar 5, 2015 at 8:24 PM

Hello Kerry,

I can’t see in the source where you added v1.2, I only see Tls being handled on your commit.

Also, if it will work, what string should I pass on the Security property? Instead of “tls” use “tls12” ???

Could you please update the NuGet package with those changes? We are not (and we can’t) use your code directly, only on a component, in this case, the NuGet package (compliance crap).

Thanks for the support!


Mar 6, 2015 at 1:36 AM
Should be Tls12, same with the SslProtocols enum name in dotnetfix 4.5

Mar 6, 2015 at 1:37 AM
Ok thank you. Can you update the NuGet package?


Sent from Outlook

On Thu, Mar 5, 2015 at 5:36 PM -0800, "kerryjiang" <[email removed]> wrote:

From: kerryjiang

Should be Tls12, same with the SslProtocols enum name in dotnetfix 4.5

Mar 6, 2015 at 1:39 AM
Tell me your test result, then I can make a new release.