5 ms·
To the security people here. I like the idea of P2P and UDP for better latency. But how dangerous is this?
by k__ 10y ago
To the security people here.
I like the idea of P2P and UDP for better latency.
But how dangerous is this?
- omginternets 10y agoAll I know (and this may not be relevant to you) is that WebRTC (can? will?) bypass Tor.
- k__ 10y agoAll I read was that it can directly connect two PCs, even if they are behind a NAT, which sounded like a cool idea at first. But having random sites doing this, didn't feel right to me.
- MichaelGG 10y agoThe real issue is that WebRTC ignores your proxy settings. This is obviously incorrect behaviour. Also there's no reason to allow silent P2P connections.
- cjbprime 10y agoIf you're thinking of the bug that exposed private IP addresses to the browser, it was fixed years ago.
- pmontra 10y agoIt's not fixed, see your addresses at https://www.privacytools.io/webrtc.html https://www.privacytools.io/webrtc.html
- pthatcherg 10y agoIf you want to force all traffic through a proxy, you must enable it using an extension, such as this one: https://chrome.google.com/webstore/detail/webrtc-network-limiter/npeicpdbkakmehahjeeohfdhnlpdklia https://chrome.google.com/webstore/detail/webrtc-network-lim...
- lallysingh 10y agoThere isn't a solid UDP proxying story for browsers, generally.
- omginternets 10y agoIs there a technical reason for this?
- ronsor 10y agoYes: it's not possible. Neither Socks(Tor) nor HTTP proxies forward udp. Only VPNs - which is an OS-level configuration (normally anyway)
- man5quid 10y agohttp://gafferongames.com/networking-for-game-programmers/what-every-programmer-needs-to-know-about-game-networking/ http://gafferongames.com/networking-for-game-programmers/wha... A great series for you to read. tl;dr Udp is good. client to client sessions are terrible over the internet.
- k__ 10y agoA nice. Didn't know that. But makes sense. In the WebRTC case, the server could simply be a "peer" too :)
- zurn 10y agoThe P2P case this article discusses is "peer-to-peer lockstep", which is only a small subset of possible p2p systems. (it's called peer-to-peer instead of client-to-client, because there is no client role in such a system).
- jaypaulynice 10y agoI think WebRTC is secure by default and everything is supposed to be encrypted and served over https...Chrome for example doesn't allow unsecure usage of the API's. See this for more: http://webrtc-security.github.io http://webrtc-security.github.io
- pmontra 10y agoI'm still blocking it with https://github.com/ChrisAntaki/disable-webrtc-firefox https://github.com/ChrisAntaki/disable-webrtc-firefox because it leaks the local IP addresses of the client over VPNs. Yes, addresses because there can be many of them at the same time, so it's useful for fingerprinting. Check your ones at https://www.privacytools.io/webrtc.html https://www.privacytools.io/webrtc.html I really don't know why the local IP addresses must be known to the server, maybe there are good technical reasons, but it's not OK.
- tokenizerrr 10y ago> I really don't know why the local IP addresses must be known to the server, maybe there are good technical reasons, but it's not OK. So they can pair you with other clients sharing a local network with you? This allows the client to talk peer to peer over their LAN which is extremely valuable.
- pmontra 10y agoThe public address could be enough for the server to realize there are two browsers from the same LAN. Then it tells the browsers to look for each other. I'm not really sure that it is practical with large LANs (a /16) but it doesn't look impossible. If they design for privacy they could develop an algorithm that works. And if I connect with a VPN I probably don't want to bypass it. I've got customers that accept unconveniences to protect their network with VPNs. Should browsers break it with WebRTC? I didn't think so. It's a vulnerability that I keep blocked.
- tokenizerrr 10y ago
- flamedoge 10y agoGames usually require central authoritative server for low latency and preventing cheating
- banachtarski 10y agoJust read the docs. WebRTC data channels are SCTP which is built on DTLS (datagram transport layer security) which uses the identical algorithm as TLS for encrypting traffic. It's as secure as TLS is, and hopefully you're using 1.2 or so.
- fulafel 10y agoWhat aspect are you worried about? In terms of plain and direct security holes in WebRTC, there is an extended attack surface. But your browser has this enabled anyway, no matter what you as an application developer or end user do. In terms of security properties delivered to the application/end user, there are security and privacy advantages in end-to-end communication instead of involving servers. But it all depends on your use case and threat model.