Crowds (anonymity network)


Crowds is a proposed anonymity network for anonymous web browsing. The main idea behind Crowds anonymity protocol is to hide each user's communications by routing them randomly within a group of similar users. Neither the collaborating group members nor the end receiver can therefore be sure where in the group the packet originated. Crowds was designed by Michael K. Reiter and Aviel D. Rubin. It defends against internal attackers and a corrupt receiver, but provides no anonymity against a global attacker or a local eavesdropper. Crowds is vulnerable to the predecessor attack; this was discussed in Reiter and Rubin's paper and further expanded in "The Predecessor Attack: An Analysis of a Threat to Anonymous Communications Systems" by Matthew K. Wright, Micah Adler, And Brian Neil Levine. Crowds introduced the concept of users blending into a crowd of computers.

How crowds works

  1. Each user joins a crowd of other users by registering himself at the blender which is a single server responsible for membership management. When a user registers, all the other members in the crowd are notified. The blender is also responsible for key distribution, as it distributes symmetric keys to individual pairs of jondos, used for encryption and decryption, respectively of packets routed along the virtual paths.
  2. Each user is represented by a jondo on her machine which is an application that runs on a user’s computer.
  3. Each jondo either submits a request to the end server or forwards it to a randomly chosen jondo. Other jondo tasks are to strip out any personal information such as cookies, identifying header fields.
  4. A jondo cannot tell if a request is initiated by the previous jondo or one before it.
  5. Request and reply follow the same virtual paths which are constructed using an algorithm involving probabilities. The virtual paths are torn down and reconstructed on a regular basis to allow anonymity for newly added members.

    Definitions

Crowds uses and defines the following terms:
; Sender : The initiator of a message
; Receiver : The final recipient of a message
; Probable Innocence : The attacker is unable to have greater than 50% confidence that any node initiated the message
; Local Eavesdropper : An attacker that can observe all incoming and outgoing messages for any propersubset of the nodes
; Corrupt Node : A node is corrupt if it uses information obtained from forwarding the message to determine the sender
; : The number of corrupt nodes
; : The number of nodes
; : The probability of forwarding

Basic Design

Crowds works by making each node seem equally likely to be the initiator of the message. As we said each node joins the network by starting a jondo, which is a small process that will forward and receive requests from other users. When the jondo is started all nodes in the network are informed of the new node's entrance, and will begin to select him as a forwarder. To actually send a message a node chooses randomly from all nodes in the network and forwards the message to them. Upon receiving the message the node flips a biased coin and if it lands heads forwards it to another random node, otherwise it forwards it to the final destination. Each node when forwarding to another node records the predecessor and in this way a tunnel is built, this is used for the communication between the sender and the receiver.

The algorithm on each machine

  1. Flip biased coin
  2. # If Heads Then Select a uniformly random node and forward to them
  3. # Else Forward to destination
  4. Record P so that a tunnel can be built

    Security analysis

We consider the question of what information an attacker can learn about the senders and receivers of web transactions, given the mechanisms of Crowds we described.

Local eavesdropper

Recall that every message forwarded on a path, except for the final request to the end server, is encrypted. Thus, while the eavesdropper is able to view any message emanating from the user's computer, it only views a message submitted to the end server
if the user's jondo ultimately submits the user's request itself.
Since the probability that the user's jondo ultimately submits the request is 1/n where n is the size of the crowd when the path was created. Thus we learn that the probability that the eavesdropper learns the identity of the receiver decreases as a function of crowd size. Moreover, when the user's jondo does not ultimately submit the request, the local eavesdropper sees only the encrypted address of the end server, which we suggest yields receiver anonymity that is beyond suspicion.
.

Collaborating jondos

Consider a set of collaborating corrupted jondos in the crowd. Because each jondo can observe plaintext traffic on a path routed through it, any such traffic, including the address of the end server is exposed to this attacker.
The question we consider here is if the attacker can determine who initiated the path. The goal of the collaborators is to determine the member that initiated the path.
We now analyze how confident the collaborators can be that their immediate predecessor is in fact the path initiator:
  1. Let Hk, k >= 1, denote the event that the first collaborator on the path occupies the kth position on the path, where the initiator itself occupies the 0th position.
  2. Let define Hk+ = Hk or Hk+1 or Hk+2 or ....
  3. Let I denote the event that the first collaborator on the path is immediately preceded on the path by the path initiator.
Note that H1 => I, but the converse I => H1 is not true, because the
initiating jondo might appear on the path multiple times. There can be a case where path is composed as follow:
Note that the first collaborator on the path is in the third position.
P - given that a collaborator is on the path, what is the probability that the path initiator is the first collaborator's immediate predecessor?
Definition:

The path initiator has probable innocence if P<=1\2.
In order to yield probable innocence for the path initiator, certain
conditions must be met in our system.
In particular, let
pf > 1/2
The theorem below gives a sufficient condition on pf, c, and n to ensure
probable innocence for the path initiator.
Theorem:
The path initiator has probable innocence against c collaborators in case
Proof:
we want to show that pf > 1/2 if
note that:
P =
in order for the first collaborator to be in the ith position on the path, the path must first wander to i-1 noncollaborators each time with probability of
,each of which chooses to forward the path with probability pf, and then to a collaborator with probability.
The next two facts follow immediately from this
P =
P =
P =
P =
P =
Now, P can be captured as
P = PP + PP =
since I=>H1+
P= = =
so, if
then P<=1\2
E.g. if pf=3\4, then probable innocence is guaranteed as long as n >= 3.

Static paths

Dynamic paths tends to decrease the anonymity properties provided by the system against collaborating jondos. The reason is that the probable innocence vanishes if the collaborators are able to link many distinct paths as being initiated by the same jondo. Collaborating jondos might be able to link paths initiated by the same unknown jondo based on related path content or timing of
communication on paths. To prevent this, we made paths static, so the attacker simply does not have multiple paths to link to the same jondo.

Embedded images and timing attacks

An HTML page can include a URL that, when the page is retrieved, causes the user's browser to automatically issue another request. It is the immediate nature of these requests that poses the greatest opportunity for timing attacks by collaborating jondos.
The first collaborating jondo on a path, upon returning a web page on that path containing a URL that will be automatically retrieved, can time the duration until it receives the request for that URL. If the duration is sufficiently short, then this could reveal that the collaborator's immediate predecessor is the initiator of the request.
How to prevent?
When a jondo receives an HTML reply to a request that it either received directly from a user's browser or submitted directly to an end server, it parses the HTML page to identify all URLs that the user's browser will automatically request as a result of receiving this reply. The last jondo on the path requests these URLs and sends them back along the same path on which the original request was received.
The user's jondo, upon receiving requests for these URLs from the user's browser, does not forward these requests on the path, but rather simply waits for the URLs contents to arrive on the path and then feeds them to the browser. In this way, other jondos on the path never see the requests that are generated by the browser, and thus cannot glean timing information from them.

Scale

The measure of scale that we evaluate is the expected total number of appearances that each jondo makes on all paths at any point in time. For example, if a jondo occupies two positions on one path and one position on another, then it makes a total of three appearances on these paths.
Theorem : In a crowd of size n, the expected total number of appearances that any jondo makes on all paths is
Each jondo's expected number of appearances on paths is virtually constant as a function of the size of the crowd. This suggests that crowds should be able to grow quite large.

Attacks

Crowds provides perfect anonymity against a corrupt receiver as all members appear equally likely to have been the initiator. As we showed against collaborating corrupt nodes Crowds provides probable innocence as long as , and provides a degree of anonymity. Against the predecessor attack Crowds succumbs in ; this attack works by a corrupt node retaining the previous hop in the path, as this will be the sender more than any other node over the rounds of rebuilding the network it will become apparent who the initiator is. Reiter and Rubin mention this and recommend long time between path reformations. Crowds is unable to protect against a global eavesdropper as it cannot use encryption on the links, this is because each node in Crowds is able to communicate with every other node, because of this setting up symmetric keys requires pairwise keys; this is too large of a number to be feasible. Against a local eavesdropper again Crowds provides no protection as the eavesdropper will see a message coming out of a node that did not enter, and this positively identifies the node as the sender.