Skip to content
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.

Correlate a visit from the same user over time #1

Open
martinthomson opened this issue Sep 18, 2019 · 1 comment
Open

Correlate a visit from the same user over time #1

martinthomson opened this issue Sep 18, 2019 · 1 comment

Comments

@martinthomson
Copy link

For 6.1, the attacker might want to take a visit from a particular user and correlate that with another visit from the same user at a different time. Sites do this all the time to measure the number of unique visitors in a given time period.

Now, like with click tracking, we might decide that this is worth keeping, but it can be in the threat model.
@jyasskin
Copy link
Member

I think this ties into anti-fingerprinting: the site should be able to reidentify a user until that user clears its storage, and then the site shouldn't be able to tell that it's the same user. +1 that it should be added to the document.

jyasskin added a commit to jyasskin/privacy-threat-model that referenced this issue Dec 19, 2019
@jyasskin
Elaborate the high-level threats section.
71c9fba 
I framed the threats that came out of the TPAC discussion as the web's
interpretation of the general threats in RFC 6973.

This explicitly describes same-site visit correlation as requested by
w3cping#1, although it
doesn't do so in the low-level goals section.
@jyasskin jyasskin mentioned this issue Dec 19, 2019
Merged
jyasskin added a commit to jyasskin/privacy-threat-model that referenced this issue Dec 19, 2019
@jyasskin
Elaborate the high-level threats section.
bd13fec 
I framed the threats that came out of the TPAC discussion as the web's
interpretation of the general threats in RFC 6973.

This explicitly describes same-site visit correlation as requested by
w3cping#1, although it
doesn't do so in the low-level goals section.
jyasskin added a commit to jyasskin/privacy-threat-model that referenced this issue Dec 20, 2019
@jyasskin
Elaborate the high-level threats section.
111c8d6 
I framed the threats that came out of the TPAC discussion as the web's
interpretation of the general threats in RFC 6973.

This explicitly describes same-site visit correlation as requested by
w3cping#1, although it
doesn't do so in the low-level goals section.
jyasskin added a commit to jyasskin/privacy-threat-model that referenced this issue Jan 9, 2020
@jyasskin
Elaborate the high-level threats section.
22dfa13 
I framed the threats that came out of the TPAC discussion as the web's
interpretation of the general threats in RFC 6973.

This explicitly describes same-site visit correlation as requested by
w3cping#1, although it
doesn't do so in the low-level goals section.
jyasskin added a commit to jyasskin/privacy-threat-model that referenced this issue Jan 13, 2020
@jyasskin
Elaborate the high-level threats section.
8e3736f 
I framed the threats that came out of the TPAC discussion as the web's
interpretation of the general threats in RFC 6973.

This explicitly describes same-site visit correlation as requested by
w3cping#1, although it
doesn't do so in the low-level goals section.
jyasskin added a commit that referenced this issue Mar 9, 2020
@jyasskin
Elaborate the high-level threats section. (#6)
7ccc40f 
I framed the threats that came out of the TPAC discussion as the web's
interpretation of the general threats in RFC 6973.

This explicitly describes same-site visit correlation as requested by
#1, although it
doesn't do so in the low-level goals section.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martinthomson @jyasskin