New Post: using SSL with websocket4net

November 1, 2015, 4:03 am

≫ Next: Commented Unassigned: websocket connection closes unexpectedly [50]

≪ Previous: New Post: Mocking WebSocket

$

0

0

We are planning to use SSL with websocket4net. Right now we are using "wss" in our implementation but allowing untrusted certificate. Now we want to validate the certificate and then do the secure communication.

Is there already a way in websocket to implement SSL certification validation and use a secure communication. Please provide it as we would need to implement the same.

Regards,
Abhiraj

---

Commented Unassigned: websocket connection closes unexpectedly [50]

November 1, 2015, 3:55 am

≫ Next: New Post: using SSL with websocket4net

≪ Previous: New Post: using SSL with websocket4net

$

0

0

We are using Websocket4net.dll (ver 0.9.0.0). At one of our customer site, the websocket client connects with server but after a while websocket is getting closed unexpectedly, this issue is happening quite frequently at the site. The server is not closing the connection that is confirmed but still the websocket connection is closed. At the websocket client side, we do get closed event, however there is no websocket error with that event to identify the issue.

It is a known issue ?, I don't have a clue why it is getting closed unexpectedly. Does websocket4net has any logging which can be seen to identify the issue. Any pointers for this issue will be highly appreciated.

Regards,
Abhiraj
Comments: Thanks for the reply.. 1. We have given latest version of websocket4net DLL and have asked for the wireshark traces if the issue is reproduced again. Will again prompt you if there is a reply Regards, Abhiraj

New Post: using SSL with websocket4net

November 3, 2015, 6:15 pm

≫ Next: New Post: using SSL with websocket4net

≪ Previous: Commented Unassigned: websocket connection closes unexpectedly [50]

$

0

0

Hi, you can hook the global event ServicePointManager.ServerCertificateValidationCallback, which is checked by WebSocket4Net too.

New Post: using SSL with websocket4net

November 9, 2015, 8:55 am

≫ Next: Created Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

≪ Previous: New Post: using SSL with websocket4net

$

0

0

Could you please share an example to hook websocket4net DLL with this static callback to validate certificate based on our defined condition.

Regards,
Abhiraj

Created Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

November 10, 2015, 6:21 am

≫ Next: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

≪ Previous: New Post: using SSL with websocket4net

$

0

0

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

Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

November 10, 2015, 5:59 pm

≫ Next: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

≪ Previous: Created Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

$

0

0

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: 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

Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

November 11, 2015, 8:25 am

≫ Next: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

≪ Previous: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

$

0

0

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: 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.

Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

November 12, 2015, 5:24 am

≫ Next: New Post: using SSL with websocket4net

≪ Previous: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

$

0

0

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: HI Kerry, Could you please let us know when it will be available. I need to forward that to our team. Regards, Abhiraj

---

New Post: using SSL with websocket4net

November 12, 2015, 5:28 am

≫ Next: Source code checked in, #02d0f5859fcef035802ff1a98fa7c5fda1c9a699

≪ Previous: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

$

0

0

Hi Kerry,

I understood what you have mentioned. But is there any way to verify that my websocket connection is getting certified. Actually, I have bunch of webservice calls before the websocket connection. My validation callback gets is invoked many times for the webservices, as I see the webservice uri in that callback but for websocket I am not able to make out when our callback was hit.
I will highly appreciate any pointers which will help to validate the websocket is also validated.

Regards,
Abhiraj

Source code checked in, #02d0f5859fcef035802ff1a98fa7c5fda1c9a699

November 14, 2015, 9:50 pm

≫ Next: Source code checked in, #bda0bc3eb3e3a0f435c2e3e4c2337fa31c9264b4

≪ Previous: New Post: using SSL with websocket4net

$

0

0

improved the references and build

Source code checked in, #bda0bc3eb3e3a0f435c2e3e4c2337fa31c9264b4

November 14, 2015, 9:51 pm

≫ Next: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

≪ Previous: Source code checked in, #02d0f5859fcef035802ff1a98fa7c5fda1c9a699

$

0

0

Merge branch 'master' of https://github.com/kerryjiang/WebSocket4Net

Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

November 16, 2015, 1:56 pm

≫ Next: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

≪ Previous: Source code checked in, #bda0bc3eb3e3a0f435c2e3e4c2337fa31c9264b4

$

0

0

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: 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

Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

November 21, 2015, 12:09 am

≫ Next: Source code checked in, #ed336df2ba37687e48adfcc4ea533d5ff324e0b1

≪ Previous: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

$

0

0

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: Hello, I commit a change to reference SuperSocket.ClientEngine 0.6.0.3 which is signed.

Source code checked in, #ed336df2ba37687e48adfcc4ea533d5ff324e0b1

November 20, 2015, 11:58 pm

≫ Next: Source code checked in, #ccc87d39b370b6763a4e5e9babd7b6aba7f6ff18

≪ Previous: Commented Unassigned: Use only TLSv1.1 or TLSv1.2 in websocket [52]

$

0

0

upgraded to SuperSocket.ClientEngine 0.6.0.3

Source code checked in, #ccc87d39b370b6763a4e5e9babd7b6aba7f6ff18

December 4, 2015, 6:44 am

≫ Next: Source code checked in, #c4be7c0a84cb4398f2640f2975429c0ac85faa14

≪ Previous: Source code checked in, #ed336df2ba37687e48adfcc4ea533d5ff324e0b1

$

0

0

upgraded SuperSocket.ClientEngine

---

Source code checked in, #c4be7c0a84cb4398f2640f2975429c0ac85faa14

December 4, 2015, 6:51 am

≫ Next: Source code checked in, #80b8e7d31e07225c722c316049149a5baf513475

≪ Previous: Source code checked in, #ccc87d39b370b6763a4e5e9babd7b6aba7f6ff18

$

0

0

improved the build script

Source code checked in, #80b8e7d31e07225c722c316049149a5baf513475

December 4, 2015, 7:04 am

≫ Next: Source code checked in, #8128cc5cf427cbb246e0d24af4ae3618a24bd194

≪ Previous: Source code checked in, #c4be7c0a84cb4398f2640f2975429c0ac85faa14

$

0

0

fixed monodroid output assembly issue

Source code checked in, #8128cc5cf427cbb246e0d24af4ae3618a24bd194

December 4, 2015, 7:04 am

≫ Next: Source code checked in, #46ba4cff83af6f65a3c298f13480bcfaceb9dba2

≪ Previous: Source code checked in, #80b8e7d31e07225c722c316049149a5baf513475

$

0

0

improved build script

Source code checked in, #46ba4cff83af6f65a3c298f13480bcfaceb9dba2

December 4, 2015, 7:11 am

≫ Next: Reviewed: WebSocket4Net 0.14 (十二月 15, 2015)

≪ Previous: Source code checked in, #8128cc5cf427cbb246e0d24af4ae3618a24bd194

$

0

0

removed reference folder because we use nuget now

Reviewed: WebSocket4Net 0.14 (十二月 15, 2015)

December 15, 2015, 6:15 pm

≫ Next: New Post: would this work on .NET 3.5 Compact (Win CE 5)?

≪ Previous: Source code checked in, #46ba4cff83af6f65a3c298f13480bcfaceb9dba2

$

0

0

Rated 5 Stars (out of 5) - I need it~~~~ Thank you