WebGL fingerprinting profile setting

[nradosevic]

I just realized that navigator.hardwareConcurrency is different depending on the device, and it is well known for mobile devices, for example it's 6 for all iPhones and all iPads older then 2018, and it's 8 newer ones and for most Android devices

And that's also the case for

WebGLRenderingContext.getSupportedExtensions()
WebGLRenderingContext.getParameter()

as WebGL Vendor and WebGL Renderer are different across different devices and again known for mobile devices, and can be used to detect if data is inconsistent

[ttlns]

Yeah, I am aware of that.

• navigator.hardwareConcurrency I can implement easely using the chrome-developer-protocoll
• WebGl fingerprinting is more challenging. Because currently, I don't have any way to overwrite javascript objects on chrome, without any possibility of getting detected. resource

[ttlns]

@nradosevic navigator.hardwareConcurrency implemented with new version (9f47904)

Note: Seems not to be implemented on chrome-90.0... (=> google-colab)

[ttlns]

Closing as it seems to be resolved