Re: On Bug 23934 "Always launch permission prompt to avoid leakage"

I think this is reasonable.  (As as aside, if the app is calling gUM 
repeatedly in order to fingerprint, won't it likely trigger the 
permissions prompt?  If the app already knows which calls to gUM it can 
make without triggering the permissions prompt, it doesn't need to 
finger print, does it?)

- Jim
On 5/14/2014 1:01 PM, Stefan Håkansson LK wrote:
> Bug 23934 has been sitting there for quite some time with no further input.
>
> Some persons (me included) argued that the permission prompt should
> always be launched (even if there are no devices available to meet the
> required constraints). The argument has been that otherwise the app
> (which may not have any intent to use camera or mike - its intent is to
> fingerprint) can experiment around with a lot of different constraint
> combinations in gUM without the user knowing, and in that way fingerprint.
>
>
> On the other hand many have argued that if there are no input devices
> available that meets the requirements of the app the user should not be
> bothered at all.
>
> My proposal is that we leave the text as is, i.e. there is no prompt if
> the required constraints cannot be met, and mitigate fingerprinting by
> adding wording about rate limiting gUM in the privacy and security section.
>
> How does this sound?
>
> Stefan
>

-- 
Jim Barnett
Genesys

Received on Wednesday, 14 May 2014 18:16:47 UTC