Skip to content
This repository has been archived by the owner. It is now read-only.

Editorial: Privacy information updates #1580

Merged
merged 6 commits into from Jul 31, 2018
Merged

Editorial: Privacy information updates #1580

merged 6 commits into from Jul 31, 2018

Conversation

@chaals
Copy link
Collaborator

chaals commented Jul 28, 2018

fixes #1311, #1312

Clarify privacy section and note that privacy can be comprmised by interaction with the user's external environment

chaals added 3 commits Jul 26, 2018
Note attacks based on interacting with the physical environment.
The `audio` element potentially enables Dolphin attacks, or mimcking voice interfaces e.g. for phishing.
@chaals chaals changed the title Privacy information updates Editorial: Privacy information updates Jul 28, 2018
@chaals chaals requested a review from scottaohara Jul 28, 2018
@chaals
Copy link
Collaborator Author

chaals commented Jul 28, 2018

@npdoty, ping for the privacy group to have a look.

@siusin
Copy link
Contributor

siusin commented Jul 30, 2018

Marked as non substantive for IPR from ash-nazg.

@LJWatson LJWatson merged commit a391ea0 into master Jul 31, 2018
2 checks passed
2 checks passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
ipr PR deemed acceptable as non-substantive by @siusin.
Details
plehegar pushed a commit that referenced this pull request Jul 31, 2018
@npdoty
Copy link

npdoty commented Aug 4, 2018

Yes, I believe this privacy text could use an extensive update, and it would be good to schedule meetings with PING (Privacy Interest Group) and the TAG on that topic.

On just a brief reading, I think the benign uses of browser fingerprinting is misleading. You don't need and shouldn't use combinations of browser configuration details to remember whether a user prefers larger text; local storage mechanisms like cookies work fine for that and we wouldn't want to recommend fingerprinting as an alternative. Perhaps a benign use would be in trying to detect fraudulent logins to a banking site.

It's also good to start describing other privacy issues available in HTML, or in the Web platform, as in the audio/dolphin attack example. It would be useful to do a broader review at some point, rather than just adding individual examples when they arise.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

4 participants
You can’t perform that action at this time.