Removed duplicate history disclosures from adversary goals (as it deals with methods) authored by Richard Pospesel's avatar Richard Pospesel
...@@ -251,12 +251,6 @@ Let's start with the goals. ...@@ -251,12 +251,6 @@ Let's start with the goals.
The adversary may want to correlate user identities or sessions across multiple remote services. The adversary may want to correlate user identities or sessions across multiple remote services.
For instance, advertising networks may wish to know that a user who visited `site-x.com` is the same user that visited `site-y.com` to serve them targeted ads while law-enforcement may wish to associate anonymous activity on `site-b.com` with a known identity on `size-a.com` to build a criminal case. For instance, advertising networks may wish to know that a user who visited `site-x.com` is the same user that visited `site-y.com` to serve them targeted ads while law-enforcement may wish to associate anonymous activity on `site-b.com` with a known identity on `size-a.com` to build a criminal case.
6. **History records and other on-disk information**
In some cases, the adversary may opt for a heavy-handed approach, such as seizing the computers of all Tor users in an area (especially after narrowing the field by the above two pieces of information).
History records and cache data are the primary goals here.
Secondary goals may include confirming on-disk identifiers (such as hostname and disk-logged spoofed MAC address history) obtained by other means.
7. **Censorship** 7. **Censorship**
`TODO: section about censorship goals` `TODO: section about censorship goals`
... ...
......