We currently have a C++ project connected to a Crossbar.io server over RAW
Cool! Would you mind telling us a little bit about the project?
Socket. I think that back then, when we wrote this, it was only possible to
use rawsocket from C++, not the websocket. We had the communication only in
a Private Network area behind a firewall.
We now have to open the respective port to the outside, which means we have
to make this secure.
What are our options? Is it possible to make a raw socket secure enough to
You can run RawSocket transports over TLS on port 443.
That is, you only need to allow outgoing TCP connections in your firewall.
From a security perspective, this is comparable to WebSocket. The security comes from TLS.
Whether that works in your corporate network depends ..
Eg some companies only allow outgoing HTTP over an enforced Web proxies that will unwrap HTTPS connections, it won't work with RawSocket. But such proxies are basically MITM attack boxes from my view (bad stuff).
pass enterprise level audits?
Or Is it possible by now to switch to wss in C++ ?
Yes, we have a WebSocket transport in AB C++ now too:
This is using
and that support secure WebSocket too.
Am 14.09.2017 um 09:56 schrieb Dieter Morgenroth: