W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2018

Re: [webrtc-stats] Exposing RTCIceCandidateStats.networkType might trigger fingerprinting

From: Varun Singh via GitHub <sysbot+gh@w3.org>
Date: Mon, 01 Oct 2018 08:09:22 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-425822906-1538381361-sysbot+gh@w3.org>
> For diagnostics, couldn't you infer this in most cases by looking at:
> 
> Network metrics like packet loss

Packet loss is a complicated metric because packet loss can appear due to congestion or due to the wireless channel. Knowing there was a wireless channel helps immensely.

> IP addresses, including private IP addresses if getUserMedia is granted

Knowing an IP address is not very useful in this regard. The IP address does not reveal networkType.

I maybe speaking about a minority of the apps, however. we and other companies, because of GDPR, COPTA, or HIPAA ---  drop/hash/encrypt the candidate pair IP addresses, and generally make it inaccessible except for specific use-cases listed in data privacy agreements (DPA). 

> > There are also situations when the networkType is wrong, because someone is tethering (for example: LTE over WiFi).
> >
> If the info is wrong enough to prevent fingerprinting, it should probably not be exposed as it might prevent good diagnostics

It still helps to know wireless was present.

-- 
GitHub Notification of comment by vr000m
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/374#issuecomment-425822906 using your GitHub account
Received on Monday, 1 October 2018 08:09:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:07 UTC