Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security/privacy considerations #17

Open
lknik opened this issue Aug 8, 2016 · 0 comments
Open

Security/privacy considerations #17

lknik opened this issue Aug 8, 2016 · 0 comments
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.

Comments

@lknik
Copy link

lknik commented Aug 8, 2016

Please find below the security/privacy considerations. I tried to think broadly. I am also aware of #4, but the considerations proposed below are broad enough to include this issue.

Proximity Sensor provides information about the distance between an object (such as the user) and the device. As such, it reports the information environmental information, as well as the device use patterns. Among the privacy risks are: information leaks and behavioral analysis.

Information leaks may arise as a result of the proximity sensor readout analysis. Distance between the user and a device might be distinctive and help to differentiate between users; a similar comment applies to the frequency of the distance changes. In this case, behavioral analysis resulting from the analysis of users’ patterns of use.

Possibility of using the values of max and distance as short-lived identifiers cannot be ruled out. The consequences are unexpected.

Recommendations follow.

The user agent MUST expose adequately discretized and minimized distance values.

The user agent MUST inform the user about the current and past use patterns of the API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
Projects
None yet
Development

No branches or pull requests

2 participants