- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Feb 2017 12:49:47 +0000
- To: public-device-apis-log@w3.org
@maryammjd, thanks for your reply. A couple of comments: > Hi all, may I please ask you to clarify what is the exact problem?\ Security and privacy concerns of using sensors at frequencies above 60 Hz. > In terms of sampling rate, we have never experience 1 Hz with motion and orientation (we have been testing different browsers for years). Is this something browser-related or network-related (e.g. connection problems)? Not sure what you mean. I don't see any reference to 1 Hz in the whole thread. Did you misread 1 KHz way above? > From the security point of view, as long as the right permission is given to the eligible code, we don't mind the sampling rate. In fact, we believe increasing the sampling rate both on native apps and js in inevitable. Vendor security teams do care however. I'm interested in determining whether they are right to care or not. That is, does increasing frequency create new attack scenarios (e.g. key logging of a nearby keyboard, pin logging on touch phones, crude voice recording, etc). And if so, at what frequency do they appear? What mitigation strategy exist beyond limiting the frequency (e.g. making sure the sensor doesn't report reading when the user is entering their pin code). -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/98#issuecomment-281335577 using your GitHub account
Received on Tuesday, 21 February 2017 12:49:54 UTC