Golgi_SDK
Debouncing your IoT Buttons
IoT Beyond WiFi – Connecting Your Product
Free IoT Whitepaper:Bridging the Gap Btw Devices and Developers with Cloud Service
Feeling Vulnerable: IoT Security
We’ve Got Issues: The Interoperability Challenge
Robert Scoble Chats with Golgi CTO Brian Kelly about IoT
IoT Connectivity: Getting It Right the First Time
Golgi's IoT Cloud Service Now Supports Arduino,Intel Galileo and Edison Boards
Taking the Pain Out of IoT Data Transport
Ovum's on the Radar Report:Golgi's IoT Mobile Cloud Service
Internet of Things: Making Sense of Standards
Happy Birthday Arduino
Building a Full Linux Image for Intel Galileo
5 Things to know about App to App communications
Re:Excuse Me Sir, Your WebRTC Is Leaking
on Friday February 27, 2015 @05:58AM (#9118220)
Thanks very much for your reply. I've been trying to enable the preference in Google Chrome Canary on Mac OSX. However, I haven't been able to successfully block the IP leak - I suspect because I haven't configured it correctly. I had to manually create the file "/Library/Google/Google Chrome Master Preferences" and add the setting you suggested. I then reinstalled Chrome Canary and tested but no effect. I also tried editing the user preferences file in ~/Library/Application\ Support/Google/Chrome\ Canary/Default/Preference but that seems to be overwritten by the browser. How should I be configuring this preference? Thanks again.
Re:Excuse Me Sir, Your WebRTC Is Leaking
on Thursday February 26, 2015 @11:41AM (#9113421)
I agree that WebRTC is very powerful and makes peer-to-peer communication from browsers easily accessible for developers. And I also love what it does. However, the issue raised in the post is seen from the point of view of the user. Convenience for the developer probably won't be a concern to a user who is concerned about IP leakage. Yes, the WebRTC API is still being standardised so perhaps this issue will be addressed in future
Re:Excuse Me Sir, Your WebRTC Is Leaking
on Thursday February 26, 2015 @11:40AM (#9113416)
There is a permission request to access the camera but this is triggered by a call to getUserMedia(). This would be done if setting up a peer connection to transmit voice and/or video. However, if you want to set up a WebRTC data channel no such prompt occurs.