- From: Johannes Kron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Nov 2019 22:45:22 +0000
- To: public-webrtc-logs@w3.org
> > In the current context with the existing MediaCapabilities API, WebGL, and WebRTC stats, I don't see how this adds any new information to be used for fingerprinting. It just packages it in a format that is more convenient for web creators using WebRTC. > > I don't understand the claim here. Is this value available elsewhere? If so, then you can expect at some point we will try to gate it, under the broader goal of isolating pages from hardware capabilities w/o specific opt-in / permission / similar > This was written with this comment in mind: https://github.com/w3c/webrtc-pc/pull/2356#issuecomment-552409803 **In summary:** - Through the MediaCapabilities API it's possible to deduce if there's HW acceleration support for a particular codec. - WebGL provides the name of the GPU chipset, which contains even more information. - Once a WebRTC stream is started (which does not require any permission unless the camera/microphone is activated), it's possible to deduce if there's HW acceleration support by looking at the implementation name in getStats or by simply looking at decode times. -- GitHub Notification of comment by drkron Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2356#issuecomment-553152073 using your GitHub account
Received on Tuesday, 12 November 2019 22:45:24 UTC