- From: pes via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Apr 2020 18:20:49 +0000
- To: public-webrtc-logs@w3.org
@youennf @jan-ivar Do you know the amount of entropy that goes into those per origin seeds (that the hashes are generated from)? If its not a huge number of bits, maybe thats the way to solve this issue. Again, my main concern here isn't (main) situations where storage (and so device identifiers) is dual keyed; its in the majority of browsers where it isn't, where people use a variety of methods to try and reduce third party storage (extensions, for example), and so where storage may rotate on a different interval than deviceIds, and then having a highly unique device id is a way or linking the storage-based identifiers together. (a large number of people on gecko and blink based browsers, particularly privacy conscious users) So, hashes instead of UUIDs sounds fine; but constraining the entropy of the input to those hashes would be a very useful step that seems like it could be some middle ground / way forward? -- GitHub Notification of comment by pes10k Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/682#issuecomment-617332255 using your GitHub account
Received on Tuesday, 21 April 2020 18:20:51 UTC