add WSS support

[oberstet]

No description provided.

[oberstet]

"""
The "problem" with adding WSS support to Autobahn is as follows.

First, if you use classic, blocking netwoork code (which also does
involve copying things around) like i.e. Weberknecht, adding SSL
is totally easy:

http://code.google.com/p/weberknecht/source/browse/trunk/src/main/de/roderick/weberknecht/WebSocketConnection.java#247

Now, Autobahn uses Java NIO .. for performance reasons, since it
doesn't copy things around.

Unforntunately, there doesn't seem to be an easy analog to

SocketChannel

like i.e. SSLSocketChannel.

When you Google for "Java NIO SSL" .. it seems to be non-trivial, sadly.

What's needed with Autobahn and WSS is extending the code here:

https://github.com/oberstet/AutobahnAndroid/blob/master/Autobahn/src/de/tavendo/autobahn/WebSocketConnection.java#L76
"""

[sublimator]

@oberstet

I'm working on a proof of concept prototype app using Autobahn at the moment. I can't get wss:// to work atm, so will just use ws://, however, for production a secure transport will be a necessity.

Is wss:// very high on your priority? If all goes to plan and I could dedicate some time to working on wss:// would you imagine having the time/inclination to provide guidance?

Thanks.

[oberstet]

Unfort., I have currently no time to work on WSS .. there is a "nearly working" TLS-NIO version here: https://github.com/tavendo/AutobahnAndroid/tree/tlsnio
There are bugs left .. best would take that branch as starting point fixing the bugs. Also see the discussion here (which explains how we arrived at that branch):
#14

[sublimator]

Thanks for reply :) I'll get back if/when I look into it.

ps. Autobahn seems great thus far :)

[danieltwagner]

Have you been able to make any progress on wss? I'm evaluating different WebSocket libraries for Android and AutobahnAndroid is looking very good so far, but not being able to use WSS is a deal breaker. I might be able to contribute if there is a list of known bugs for the tlsnio branch?

[sublimator]

We just went ahead and used AutoBahn for our prototype and feel comfortable
that we can deal with wss when we need it. Autobahn is a solid project and
you'll find many others use their test suite.

Not sure exactly when we'll be focusing on wss, but it's on the cards as
we'll need it one day.

[danieltwagner]

I might consider doing this but will need to switch to WSS rather soon as we found that some mobile operators interfere with non-TLS connections, inadvertently breaking WebSocket connections.

[sublimator]

Will let you know when we can contribute. Will try and get boss to give it
some priority but at this point it's just not hugely important for us.

[danieltwagner]

Cool, thanks for being super responsive! :)

[sublimator]

Just FYI, in case you missed it, I'm not really involved in the project,
just a consumer :)

[danieltwagner]

Yeah, I got that. Still good to know that someone else is out there!

[sublimator]

Likewise :)

[danieloskarsson]

https://github.com/palmerc/SecureWebSockets

[darenschwenke]

"I might consider doing this but will need to switch to WSS rather soon as we found that some mobile operators interfere with non-TLS connections, inadvertently breaking WebSocket connections."

Yep. Seems to be common.

[ocroquette]

Just a note to say it would be really great to have TLS support in Autobahn Android!

[sublimator]

Yep :) !

[brunettia]

So at the moment, what's the best option for using wss on android ? Does it works in Autobahn ? 'Cause I really like this library!! :)

[tommyvn]

oberstet did mention that there may be bugs on the TLS branch for your wss needs but so far it has been good to me. What we've used it for isn't in production tho.....

[brunettia]

alright thank you very much, i'll try it!

[danieloskarsson]

I don't know if it's the best option, but we do use SecureWebSockets which I linked to above in our production code, sending quite a big number of messages.

[ocroquette]

For my app, I switched for this reason to https://github.com/koush/android-websockets
SSL is working fine.

[epicblood]

Any update on if/when this will be implemented?
Would really hate to have to switch my libs.

[oberstet]

Sorry, I am overloaded with stuff. This will be implemented, definitely. I cannot promise you a deadline, but I will take up dev on AutobahnAndroid again soon - WAMPv2 needs to be implemened as well.

[sublimator]

There is also: https://github.com/TooTallNate/Java-WebSocket

[mandrachek]

Since the NIO issue has supposedly been resolved on Android >= 3.0, will this work out of the box on API levels >= 14? I haven't had much luck with the other implementations mentioned on this thread. :(

[akhiljayaram]

@oberstet please add wss support.. Autobahn was super perfect for ws.. But for wss , using TLS branch, connection goes sometimes.

[prasad-1210]

+1 for wss support from autobahn. I've been watching this space since last 1 year for WSS ):

[xsren]

+1 for wss support from autobahn.

[ilber]

+1 for wss support from autobahn.

[LoveWalter]

+1 for wss support from autobahn..

[zeuscode]

+1 for wss support from autobahn..

[rsclmumbai]

+1 for wss support from autobahn.

[rsclmumbai]

BTW, is there any work around to have a secure data exchange?

[szczepaan]

is this topic alive ?

[goeddea]

We have found somebody who will do an update of Autobahn|Android (which will include support for WAMP v2). No definite timeline yet (best guess at the moment: Q3).

[oberstet]

this will be addressed as part of #92

[szczepaan]

Any status update on that timeline?

[RabbitPie]

+1 for wss support from autobahn.

[atonamy]

Hey today November 2016 and still no any official support for wss :(
I like this library but it's useless for production because ssl is very important for commercial app.
We tried to use this implementation https://github.com/palmerc/SecureWebSockets but is memory leak issue in the code :(

There only one stable option for Android now so far is https://github.com/TooTallNate/Java-WebSocket which is support ssl. The rest solutions is useless because lack of full wss support for websockets.

Why like this? Why we don't have strong secure layer support in websocket libraries for Android? Websocket is not popular for professional developers? Or anyone don't care about sensitivity of their data in apps and use ws in production?

[erobic]

@atonamy Neovisionaries web socket client: https://github.com/TakahikoKawasaki/nv-websocket-client also supports wss.

[atonamy]

@erobic
Thanks a lot for reference.