{"action":"created","issue":{"url":"https://api.github.com/repos/RequestPolicyContinued/requestpolicy/issues/586","labels_url":"https://api.github.com/repos/RequestPolicyContinued/requestpolicy/issues/586/labels{/name}","comments_url":"https://api.github.com/repos/RequestPolicyContinued/requestpolicy/issues/586/comments","events_url":"https://api.github.com/repos/RequestPolicyContinued/requestpolicy/issues/586/events","html_url":"https://github.com/RequestPolicyContinued/requestpolicy/issues/586","id":55609784,"number":586,"title":"RPContinued does not block/see WebRTC connections","user":{"login":"nodiscc","id":3950390,"avatar_url":"https://avatars.githubusercontent.com/u/3950390?v=3","gravatar_id":"","url":"https://api.github.com/users/nodiscc","html_url":"https://github.com/nodiscc","followers_url":"https://api.github.com/users/nodiscc/followers","following_url":"https://api.github.com/users/nodiscc/following{/other_user}","gists_url":"https://api.github.com/users/nodiscc/gists{/gist_id}","starred_url":"https://api.github.com/users/nodiscc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nodiscc/subscriptions","organizations_url":"https://api.github.com/users/nodiscc/orgs","repos_url":"https://api.github.com/users/nodiscc/repos","events_url":"https://api.github.com/users/nodiscc/events{/privacy}","received_events_url":"https://api.github.com/users/nodiscc/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/RequestPolicyContinued/requestpolicy/labels/bug","name":"bug","color":"fc2929"},{"url":"https://api.github.com/repos/RequestPolicyContinued/requestpolicy/labels/important","name":"important","color":"000000"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-01-27T12:06:49Z","updated_at":"2015-02-04T04:48:39Z","closed_at":null,"body":"https://diafygi.github.io/webrtc-ips/ leaks LAN and WAN IP addresses through WebRTC. By looking at the code at https://github.com/diafygi/webrtc-ips, I see the STUN server used for the demo is `stun.services.mozilla.com`. The request does not show up in the request log.\r\n\r\nAs the destination is on another domain, it should be blocked in _default deny_ mode."},"comment":{"url":"https://api.github.com/repos/RequestPolicyContinued/requestpolicy/issues/comments/72790252","html_url":"https://github.com/RequestPolicyContinued/requestpolicy/issues/586#issuecomment-72790252","issue_url":"https://api.github.com/repos/RequestPolicyContinued/requestpolicy/issues/586","id":72790252,"user":{"login":"futpib","id":4330357,"avatar_url":"https://avatars.githubusercontent.com/u/4330357?v=3","gravatar_id":"","url":"https://api.github.com/users/futpib","html_url":"https://github.com/futpib","followers_url":"https://api.github.com/users/futpib/followers","following_url":"https://api.github.com/users/futpib/following{/other_user}","gists_url":"https://api.github.com/users/futpib/gists{/gist_id}","starred_url":"https://api.github.com/users/futpib/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/futpib/subscriptions","organizations_url":"https://api.github.com/users/futpib/orgs","repos_url":"https://api.github.com/users/futpib/repos","events_url":"https://api.github.com/users/futpib/events{/privacy}","received_events_url":"https://api.github.com/users/futpib/received_events","type":"User","site_admin":false},"created_at":"2015-02-04T04:48:39Z","updated_at":"2015-02-04T04:48:39Z","body":"I looked for legit ways to intercept those connections and found none too. Right now it seems that the only way to block that selectively is to shim the WebRTC API on content `window` objects (like replace the `RTCPeerConnection` function with our own that first checks if it's allowed to work). Nice guys on irc suggested that [frame scripts](https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/The_message_manager#Loading_frame_scripts) might be the right way to do that, but I didn't tried it yet."}}