You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
Sites can't tell that a single user is visiting on two different devices until the user enters sufficiently-identifying information into the site on both devices independently or otherwise expresses a desire to sign into the same account on both devices.
The ideal threat model would prevent cross-device correlation until the user intentionally signs into a single account on both devices, but it seems impossible for a browser to prevent users from, say, typing a credit card number or home address into the site on each device, which doesn't express the user's intent to share an account, but does let the site guess it's the same or a closely-related user.
I think the only practical effect is to ban browsers from sync'ing storage across devices without per-site user intent (?), but that's still worth writing down.
The text was updated successfully, but these errors were encountered:
+1, but also I think better defining the threat of cross-device correlation will involve a lot more threats than just browser-synced storage. Environmental sensors and out-of-band signaling mechanisms (e.g. correlating through similar changes in ambient light, hard-to-hear audio modulations, recognizing simultaneous idle or accelerometer changes) are known threats.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Roughly:
The ideal threat model would prevent cross-device correlation until the user intentionally signs into a single account on both devices, but it seems impossible for a browser to prevent users from, say, typing a credit card number or home address into the site on each device, which doesn't express the user's intent to share an account, but does let the site guess it's the same or a closely-related user.
I think the only practical effect is to ban browsers from sync'ing storage across devices without per-site user intent (?), but that's still worth writing down.
The text was updated successfully, but these errors were encountered: