Re:TCP simultaneous open and peer to peer networking
by ars on Monday July 01, 2013 @03:33AM
(#5969252)
Yes, but your approach requires a lot of bandwidth on the 3rd party.
But a 3rd party doing nothing except helping with synchronization uses barely any bandwidth and someone could easily host it for free on some server that is not otherwise fully used, simply as a service to the public.
Re:TCP simultaneous open and peer to peer networking
by idupree on Monday July 01, 2013 @03:17AM
(#5969209)
That's standardized as TURN, if I'm not mistaken ( https://en.wikipedia.org/wiki/Traversal_Using_Relays_around_... ). Other NAT traversal mechanisms (STUN) don't make the server pay for bandwidth. (Which methods work with TCP, in practice?)
Re:TCP simultaneous open and peer to peer networking
by dfc on Monday July 01, 2013 @03:38AM
(#5969263)
There was a good thread on p2p-hackers a little while back. I apologize for not digging up the link but I'm on my way to bed. I think the thread was something like "state of the art NAT traversal"
Re:TCP simultaneous open and peer to peer networking
by amenod on Monday July 01, 2013 @10:06AM
(#5970686)
I have to disagree on that - can you really trust encrpytion? Are you sure? On the other hand, why depend on (supposedly) strong encryption against 3rd party if you can just avoid passing the message through their hands altogether?
This seems like a great stuff if it works. Unbeleviable I was able to avoid knowing about it until now. Kudos to top poster, great info.
Re:TCP simultaneous open and peer to peer networking
by mixedbit on Monday July 01, 2013 @10:27AM
(#5970828)
If you don't want to trust encryption you are screwed. Unencrypted TCP doesn't give any snooping protection, it also doesn't give any way to enforce and validate that a route that packets traverse is trusted.
Re:TCP simultaneous open and peer to peer networking
by amenod on Monday July 01, 2013 @04:22PM
(#5973330)
My point was different. If there is no need for someone to see the (encrypted, if you like) traffic, then it would be safer not to send it through their server at all. It is difficult to decrypt the stream you don't have access to.
The only thing that the third party learns is that there is a connection, but the proposes solution also has this drawback.