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

Define fingerprinting vector #115

Merged
merged 3 commits into from
Jan 15, 2020
Merged

Conversation

zcorpan
Copy link
Member

@zcorpan zcorpan commented Mar 29, 2017

Fixes #20.


This is blocked by speced/bikeshed#964


Preview | Diff

@zcorpan zcorpan mentioned this pull request Mar 30, 2017
zcorpan added a commit to whatwg/html that referenced this pull request Mar 30, 2017
infra.bs Show resolved Hide resolved
zcorpan added a commit to whatwg/html that referenced this pull request Aug 25, 2017
@annevk
Copy link
Member

annevk commented Dec 20, 2017

Hey, @othermaciej left some useful feedback in whatwg/html#3054 (comment) that suggests we should maybe rename this to "tracking vector" or some such.

@othermaciej
Copy link

I think it might be useful to define both "fingerprinting vector" and "tracking vector" as a superset of "fingerprinting vector". The current definition seems to be just about fingerprinting. But we need a way to tag features like LocalStorage and BroadcastChannel, and those are tracking but not fingerprinting.

@annevk
Copy link
Member

annevk commented Jan 7, 2018

@othermaciej should those exist separately? And do we want separate icons for both? Or would annotating all with "tracking vector" and mention the specifics on a per feature basis be sufficient?

@othermaciej
Copy link

@annevk I am not sure. Browsers may care about fingerprinting vectors and other tracking vectors at different levels. For Safari/WebKit, we care about both, but recognize that fully mitigating fingerprinting is a harder problem. Marking the two cases differently might help get better review from interesting parties.

Note: to be consistent, probably every stateful storage mechanism that exists in the web platform should be marked "tracking vector", including but not necessarily limited to: Session Storage, Local Storage, Cache API, HTTP cookies, IndexedDB, the HTTP cache, HSTS, HTTP ETags, SQL Storage, plugins (since many have their own storage mechanisms), CSS visited link history, Service Workers, Shared Workers.

(I realize not all of these are defined or even mentioned in WHATWG Living Standards or other standards that make use of Infra).

@annevk
Copy link
Member

annevk commented Aug 28, 2019

I'd like to push this forward as I think this is rather relevant these days. To keep it simple I suggest we go with "tracking vector" exclusively, defining it such that it is inclusive of fingerprinting. If at some point we establish that we need more categories we can cross that bridge then.

@npdoty
Copy link

npdoty commented Aug 28, 2019

I don't have strong feelings on "tracking vector" vs. "fingerprinting vector" or defining/using them both. But if we start with just "tracking vector" are we going to stick with fingerprint-style icons? Or do we need a different iconography for the more generic term?

@annevk
Copy link
Member

annevk commented Aug 29, 2019

I'm fine with keeping the icon Simon created and using it for a broader purpose, but we could replace it if someone is able to create something suitable under CC0.

@zcorpan
Copy link
Member Author

zcorpan commented Sep 2, 2019

I now think the fingerprint image I created looks kinda ugly, so I wouldn't mind a competing proposal. 🙂

@annevk
Copy link
Member

annevk commented Sep 10, 2019

I'd be happy to replace it if someone were to offer something under an equivalent license. Otherwise though, I'd rather move ahead with this than wait for something better to appear.

Copy link

@othermaciej othermaciej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left some comments on the assumption that this would be generalized to "tracking vector".

(To be clear, I strongly support adding this material to Infra, my comments are more about not making it sound like fingerprinting is the only tracking vector, and also about not justifying interest-based targeting, since it's not necessarily agreed to be benign.)

infra.bs Outdated Show resolved Hide resolved
infra.bs Outdated Show resolved Hide resolved
infra.bs Outdated Show resolved Hide resolved
infra.bs Outdated Show resolved Hide resolved
infra.bs Outdated Show resolved Hide resolved
infra.bs Outdated Show resolved Hide resolved
infra.bs Outdated Show resolved Hide resolved
infra.bs Outdated Show resolved Hide resolved
infra.bs Outdated Show resolved Hide resolved
infra.bs Outdated Show resolved Hide resolved
@jyasskin
Copy link
Member

I've confirmed in a local build that the tracking vector paragraph gets a fingerprint icon, so no more need to wait for speced/bikeshed#964 (comment).

@annevk
Copy link
Member

annevk commented Jan 4, 2020

Well, I'd like it to also link and use the remote icon and such.

@jyasskin
Copy link
Member

jyasskin commented Jan 5, 2020

Yep, but Bikeshed's link will go to text that this PR is adding, so merging this shouldn't block on that.

@annevk
Copy link
Member

annevk commented Jan 6, 2020

I suppose that's true, although the styling leaves to be desired. whatwg/whatwg.org#64 fixes that, but does depend on the other changes.

Is there a reason to merge this early? Hopefully @tabatkins will soon be able to address the remaining issues.

@annevk
Copy link
Member

annevk commented Jan 7, 2020

Tab has now done so and will add the link to Infra once this PR is merged. That seems fine as only HTML is impacted and HTML does not depend on Bikeshed. I've created speced/bikeshed#1578 so we can start using an external image here. I'll also check all the other PRs again to ensure everything is in order for the big switch.

annevk added a commit to whatwg/html that referenced this pull request Jan 7, 2020
This allows other standards to designate something as a tracking vector and link this text for a
centralized explanation.

Fixes #20.

Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
@annevk annevk force-pushed the zcorpan/define-fingerprinting-vector branch from 84e3447 to 8d5fea4 Compare January 14, 2020 09:51
@annevk
Copy link
Member

annevk commented Jan 14, 2020

As there's always one more thing: speced/bikeshed#1586.

@annevk annevk merged commit 6fbd1fa into master Jan 15, 2020
@annevk annevk deleted the zcorpan/define-fingerprinting-vector branch January 15, 2020 08:14
@annevk
Copy link
Member

annevk commented Jan 15, 2020

Apologies for the commit title. Fortunately the description does mention "tracking vector" so git log --grep won't miss it.

I was too enthusiastic about finally being able to land this.

annevk added a commit to whatwg/html that referenced this pull request Jan 15, 2020
annevk added a commit to whatwg/html that referenced this pull request Jan 16, 2020
annevk added a commit to whatwg/html that referenced this pull request Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Tracking vector tracking
8 participants