Denis Zabavchik

+1 - optionally Websocket is supported via `websocketpp` (wss:// TLS via OpenSSL)

Afterthought... > libsodium will be a mandatory dependency, and we'll reuse crypto utility stuff from there (eg HMAC-SHA256 for WAMP-CRA). And we have it for WAMP-cryptosign. Since it already uses...

I'm not married to OpenSSL, and not opposed to libsodium as default option (+ elimination of OpenSSL from default deps). I'm only concerned about mandates that hinder opportunities. Regardless of...

Base64 implementation is really irrelevant. WAMP-CRA defines HMAC-SHA256 as one and only supported algo - NaCl fits the bill across all platforms (if authentication is even used). Using WAMP-cryptosign is...

@oberstet, thanks for clarifications. As long as the overhead of cryptography is not required (inside secure perimeter where trust is implicit) dormant crypto-code is not an issue. Speaking of crossbar...

100% on the same page

A dirty solution is to define `MSGPACK_DEFAULT_API_VERSION=1` in project settings. That will effectively disable v2 namespace. It will compile and run fine.

It compiles with VS2015, runs, connects and authenticates with crossbar.io 0.12.1. After fixing auth flow, I have not tried anything beyond authenticating and receiving a WELCOME. If you are running...

Just noticed, part of my fix for wampcra got overwritten by most recent merge. `break` missing for CHALLENGE again. ``` case message_type::CHALLENGE: process_challenge(std::move(message)); + break; case message_type::AUTHENTICATE: ```

Sorry l, forgot to mention msg pack on server side. I stepped on that rake also. MSGPACK_DEFAULT_API_VERSION=1 is now defined in the headers for _WIN32 Regards, Denis > On Feb...