-
Notifications
You must be signed in to change notification settings - Fork 75
TLS Support #77
Comments
@Hywan next step is to make real test with anothers Clients. The Browser client like Chrome still don't work, but I only make test with self-signed TLS certificate. |
@Pierozi Why not having a self-signed certificate for both the client and the server and test with |
Huh ? Both ? It's web standard SSL handshake is one way, server side certificate. now we need make it compatible with others clients, and maybe is not an |
Hi @Pierozi and @Hywan Since I am new to websockets, I couldn't come up with a solution. Let me know if I can help. |
@rokha thanks for your feedback, issue is clearly related to our implementation of Let's encrypt is a good candidate for our test, i will try to update my POC today with it and let you know. btw, you didn't know a WebSocket client supporting TLS ? |
Hello @rokha, after couples research it seems no one really care about direct TLS encryption of websocket server because in real use case you will certainly have a Load balancer or Proxy webserver like Nginx who will deal the encryption and forward into your private network the websocket. |
ping? |
Encryption work between our Client and Server, but not with HTTPS Client. |
@Pierozi What should we do to get it works? |
The TLS support of WebSocket is partially working.
The
enableEncryption
method was forgot in Server side.I've open a PR with demo on my Fork for trying to make it work. (certificate included)
Once the enableEncryption are fix; the php client are working, but not a web browser.
https://github.com/Pierozi/Websocket/pull/1/files#diff-5a72b4fa5efc1217f53f085c8580c79eR94
Maybe this is due to my certificate, self-signed, works great with php client because i've set context who allow self-signed and not verify peer.
If anyone have time to test it with real certificate, that could be good.
The text was updated successfully, but these errors were encountered: