Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

restricting the SensorManager #723

Closed
XS666 opened this issue Oct 14, 2013 · 6 comments
Closed

restricting the SensorManager #723

XS666 opened this issue Oct 14, 2013 · 6 comments

Comments

@XS666
Copy link

XS666 commented Oct 14, 2013

Originally Posted by Tungstwenty

@M66B,
You're not restricting the SensorManager yet, right?

You might want to have a look at this interesting article

http://bit.ly/1bg5HOA

@0x0878
Copy link

0x0878 commented Oct 14, 2013

Nice find.

@Cerberus-tm
Copy link

Ah, very interesting. I obviously support this, although I have no idea how difficult it would be to implement this. What sensors should be restrictable? All? Frankly I was very surprised that the browser in Android lets websites use the sensors without any use action!

@Cerberus-tm
Copy link

"Can Mobile Accelerometers Spy on Your Desktop Keystrokes? — The answer to the question above, as security researcher Philip Marquardt demonstrated, is “yes.” However, it’s not all that likely in practice, and there are several simple ways to protect yourself."
http://www.xda-developers.com/android/can-mobile-accelerometers-spy-on-your-desktop-keystrokes/

So allowing us to block programs from reading the various sensors would be a great addition to Xprivacy, to make it really future proof.

@M66B
Copy link
Owner

M66B commented Nov 8, 2013

@M66B M66B closed this as completed in 8a3a4a3 Nov 9, 2013
@Cerberus-tm
Copy link

Yay! Welcome back.

@M66B
Copy link
Owner

M66B commented Nov 9, 2013

Test version: http://d-h.st/kil

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

4 participants