Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

Limit which applications can get sensor data #22

Closed
hadess opened this issue May 20, 2015 · 2 comments
Closed

Limit which applications can get sensor data #22

hadess opened this issue May 20, 2015 · 2 comments

Comments

@hadess
Copy link
Owner

hadess commented May 20, 2015

Only foreground applications? Only to applications in the current seat? Should applications request it through an agent a-la Geoclue?

@joshtriplett
Copy link

There are two independent concerns that seem applicable here.

First, there's the normal restriction to applications in the current seat, just as with local input devices or audio devices. I would suggest handling this via the standard "uaccess" mechanism.

Second, even for such applications that qualify, sufficiently clever applications could infer keyboard or mouse events from high-precision accelerometer information. For sandboxed applications that intentionally do not have access to input devices when not in the foreground, that could be a concern; however, for non-sandboxed applications, I don't think this is worth solving. So, I would suggest documenting that access to raw accelerometer data (rather than heavily cooked data like orientation in 90 degree increments) can potentially leak information about user input ,and then letting sandboxing mechanisms handle this via their permissions mechanism.

@hadess
Copy link
Owner Author

hadess commented Jan 9, 2020

@hadess hadess closed this as completed Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants