Supported cryptocurrencies:
BCH Bitcoin Cash
0.0001 BTC
Englishbird's view at how to add encryption to websocket *implementation*, how integration with TLS library works

Artemciy 1 week ago

Please Sign-in to post a comment.
ylomat 6 days ago
Mahdi 6 days ago
Depends on the kind of server you have.
but the easiest way is to use some kind of web-proxy like nginx.
let's imagine you can run your websocket server on localhost http port 8000.
all you need to do is to run https server with nginx on port 443 with a valid trusted ssl certificate. then you need to configure nginx to redirect all websocket requests incoming to this service(port 443 ssl) to your local port 8000. in this case nginx is a proxy server between client and your websocket server. connection between your web service and nginx is inside your server so it's safe, and the connection between client and nginx is based on trusted ssl over internet, which is safe too.
Rafael 6 days ago
Since the main focus of WAMP is web applications and the Internet of Things, clients are implemented in languages ​​that have proven themselves in these industries (only WAMP v2 clients are listed): The minimum requirement for building a WAMP client is the ability to use sockets and JSON serialization. Thus, many modern languages ​​already fulfill these requirements using standard libraries. Additional features that would add dependencies to the project, such as TLS encryption or MessagePack serialization, are optional.However, the persistence of WebSocket connections requires the use of blocking-protected libraries and asynchronous APIs. In languages ​​with one official mechanism like JavaScript, Erlang, or Go, this is not a problem. But languages ​​with several competing asynchronous programming solutions, such as Python or PHP, force the client author to commit to a specific part of the ecosystem.

For the same reason, integrating legacy projects can also take work. As an example, most of the popular Web Python frameworks that use WSGI, a synchronous API and run a WAMP client inside the WSGI worker need hand adapters like crochet. Routers
Although routers can be embedded directly into application code, and some client libraries also provide a router, this architecture is discouraged by the specification. [13]

Since the router is a moving part, it is best used as a replaceable black box, just like Apache or Nginx for HTTP:

Router Language Python (CPython and PyPy)
Erwa Erlang
Jawampa Java
Thruway PHP
wamp.rt JavaScript (Node.js only)
WampSharp C #
Wiola Lua
Nightlife-Rabbit JavaScript (Node.js only)
nexus go.WAMP is currently in version 2 [20], which introduces routed RPC. Version 1 is now obsolete. [21] At the moment, all routers are version 2 compatible. Some clients remain unported:, AutobahnAndroid and cljWAMP.

Version 2 of the specification is split into two parts: a baseline profile including Router RPC and Pub / Sub, and an advanced profile specifying trust levels, URI pattern matching, and client enumeration. The baseline profile is considered stable and implemented in current libraries while the extended profile is still evolving.
kimo2 5 days ago
1. change websocket protocol from "ws://" to "wss://" (websockets over tls) in your app, e.g.
const ws = new WebSocket('wss://');
2. set up https on your webserver (a self-signed ssl certificate would be enough for testing)
3. configure your webserver to proxy websockets to your ws server (proxy_pass)

after this, you'll be able to use an encrypted data channel to send messages.
Larcah95 3 days ago
trevaughn hamilton 1 day ago
You know that you can find all of these on Youtube right
shalini 20 hours ago
This does not need any TLS library integration. We just need a webserver like apache where you need to configure WSS protocol.

1. First configure you webserver to support Secure Web socket (WSS) ex: webserver should allow wss://
2. Ex. How to configure apache web server for wss:
Add these two directives to webserver apache: ProxyPassMatch and ProxyPassReverse as shown below
<VirtualHost *:443>
ProxyPassMatch ^/wss2/(.*) ws://$1
ProxyPassReverse ^/wss2/(.*) ws://$1
3. After Step 2 changes on Apache webserver configuration, restart the server and connect to the WebSocket server using: wss://
4. With WSS protocol in place all transactions are encrypted on wire
Mohamad4900 19 hours ago
Search in google
Wasabi 15 hours ago
A well-structured webservice will do the trick.
Abose 9 hours ago
You can help yourself with research, I could be of assistance.