Issue metadata
Sign in to add a comment
|
webrtc-internals: incomplete ip addresses for candidates in JSON dump
Reported by
fi...@appear.in,
Apr 20 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/49.0.2623.108 Chrome/49.0.2623.108 Safari/537.36 Steps to reproduce the problem: 1. go to https://webrtc.github.io/samples/src/content/peerconnection/pc1/ 2. make a call 3. open webrtc-internals 4. create a dump 5. inspect dump, compare ip address to Cand-something report What is the expected behavior? What went wrong? In the attached dump, Cand-KKWryrTd-ipAddress is 10.6. In internals, the full address is shown as 10.6.6.0 While that is a nice change from a privacy PoV, is that intentional? Happens in M49 - M52 at least. Also, (thanks jansson) this only affects candidates, not googLocalAddress etc so it doesn't enhance privacy. Did this work before? Yes in the past Chrome version: 49.0.2623.108 Channel: n/a OS Version: Flash Version:
,
Apr 20 2016
,
Apr 20 2016
,
Apr 21 2016
,
Mar 10 2017
I think this is by design of how the stats are reported. I see the full address in googRemoteAddress. Since there hasn't been any activity for about a year and it's not clear to me that there's an action needed, I'm closing as wontfix. Please ping the bug if you disagree. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by fi...@appear.in
, Apr 20 2016114 KB
114 KB View Download
225 KB
225 KB View Download