Add support for websocket (ws and wss) in bootstrap node

[iphydf]

This is useful for supporting webtox and later to get around application layer firewalls like the ones in airports that only allow http connections.

We can look into mbed TLS as a library for crypto needed for https/wss. For webtox, that's a requirement. For native tox, we don't need encrypted websockets since we'll be sending tox crypto over it anyway.

[emdee-is]

Does websocket (ws and wss) in bootstrap node work over Tor?

If not, and I suspect not, then it raises the question of priority planning in the project: does the project want Tox in Tor more than it wants websockets?

There is a prominent wiki that would be good for project planning on wiki.tox.chat that I think @nurupo maintains, but you would need people to use it, and to prioritize things. (I made an accout there and applied for write permissions by never heard back as I wamted to add some of the pages from my wiki.) There's a lot of outdated information there that needs cleaning up: the people interested in the project must realize that it is the public face of Tox.

The reason I suggest this is because I'm seeing a lot of "rewrite-from-scratch" which can be a planning failure if it's not been thought out (think Netscape) and for that you need discussion in something like a wiki. You can't use NGC for that sort of thing, as you have no history of when you're not connected, and it's susceptible to impersonation JFreegman/toxic#622

[iphydf]

Yes, it works over tor. Websockets are TCP.

[emdee-is]

Yes, it works over tor. Websockets are TCP.

Yes I know they're TCP but I don't think websockets are easy to run over Tor. I'll check to see, but I think the Tor browser disables them, perhaps because of IP leakage.

To see what it takes to use them over Tor see: https://meejah.ca/blog/end-to-end-encrypted-rpc-over-tor and WAMP https://blog.torproject.org/secure-messaging-onion-services-how/ but I don't think any of that works these days, although I'm no expert at it. Their solution used a clearnet router crossbar.io.

No feeback on the idea of project planning and prioritization?

[emdee-is]

I'll take that as No to the idea of project planning and prioritization.

If the project changes it mind and decides to proritize the work, here is my list of suggestions :

• support Python Please add docs/tutorial py-toxcore-c#78 (comment)
• support Corporate proxies Feature request: authentication support for proxies #1682
• test Tor proxies -DSOCKS_HOST_TEST and -DSOCKS_PORT_TEST for testing #2469 (comment)
• test Corporate proxies Feature request: authentication support for proxies #1682
• support Tox in Tor - blockers:
  • Please break the list of nodes out of the C code #2467
  • An equivalent to the other/fun/bootstrap_node_info.py script for TCP #2331
  • tox-bootstrapd goes into an infinite loop  #2332
• Fix DNS leakage in Tor When using SOCKS5 proxy, do name resolution through the proxy #469
• Fix the KCI if it leads to IP disclosure in Tor Tox Handshake Vulnerable to KCI #426
• mainain a ChangeLog and distill it into release notes
• solve Multidevice to prevent impersonation Can anyone change their name in NGC, even to other peoples names? JFreegman/toxic#622
• actively support an IRC channel for supporting new users Put the IRC channel in the README #2463
• adopt one of the abandonned GUI clients into TokTok so that there's at least one supported Desktop client,
• integrate the testing of the supported GUI client.
• bring the https://wiki.tox.chat up to date and mark the abandonned clients - it is the visible face of Tox.
• start project planning and prioritization, perhaps using the wiki