This project is read-only.
3
Vote

Use only TLSv1.1 or TLSv1.2 in websocket

description

Hi,

I am using wesocket4net v 0.14.0 and looking a way in websocket client to specify that we will use only TLSv1.1 or TLS v1.2

I have seen in some post where in Websocket we have added one more argument in the constructor to specify SSL protocol. However it is not visible in websocket 0.14.0

Please let me know what needs to be done here to have this working using TLSv1.1 or TLSv1.2

Regards,
Abhiraj

comments

abhirajgandhi wrote Nov 11, 2015 at 1:59 AM

Hi Kerry,

Is there any way, I can get the below mentioned change request to get support of TLS v 1.1 and TLS v1.2.

https://github.com/kerryjiang/WebSocket4Net/pull/39


Regards,
Abhiraj

kerryjiang wrote Nov 11, 2015 at 4:25 PM

Actually, it's a pull request in SuperSocket.ClientEngine.

I have accept it just now, but I reorganized the solution structure of SuperSocket.ClientEngine.
So it needs time to clean it and let WebSocket4Net reference it again.

abhirajgandhi wrote Nov 12, 2015 at 1:24 PM

HI Kerry,

Could you please let us know when it will be available. I need to forward that to our team.

Regards,
Abhiraj

abhirajgandhi wrote Nov 16, 2015 at 9:56 PM

Hi Kerry,

I do see you have checked in the changes to support TLS v1.1 or TLSv1.2 in websocket4net. I downloaded the latest source code but it is giving build error "Super Socket Client engine DLL assembly does not have a strong name."

Once you have done the fix for the strong name issue, should we take the latest source code and use it or you will need to more check in to provide support for TLS v1.1 or TLSv1.2.

Please let us know.

Regards,
Abhiraj

kerryjiang wrote Nov 21, 2015 at 8:09 AM

Hello, I commit a change to reference SuperSocket.ClientEngine 0.6.0.3 which is signed.