![]() |
![]() |
![]() |
|
|
|
|
|
|
|
|
|
|
Responsibilities of Mix OperatorsThis text explains what a cascade is and how to get your Mix into one.Cascade architectures (static or dynamic)In order to be able to forward and anonymize user web traffic, each Mix server must be part of exactly one Mix cascade. The interconnection between the Mixes is either static or dynamic. In a static cascade each Mix is configured to listen on a certain port for incoming data from it's previous Mix (or the JAP clients in case of being the first Mix). On the other hand, each Mix has to know how to connect to the following Mix (or the web-proxy in case of being the last Mix). So the host name and the port of the following Mix are needed. You get them from the next Mix' Operator, for example by e-mail.In a dynamic cascade (that is not fully functional yet) the Mixes have no static configuration, but may get connection information about their next Mix from the InfoService. Operators of last Mixes construct a cascade by choosing currently unconnected "free" Mixes and the chosen Mixes, together with the last Mix, will connect automatically when they get the approriate command from the InfoService. Of course, all messages are cryptographically signed, so no one will be able to fool the system. Planning a cascadeInitially it has to be clear with whom else and how a Mix cascade will be set up. First it's important to have fast data interconnections between the partners of a cascade. Planning a whole cascade by your own, you will later or earlier need adequate partners who also run Mix servers. If you are cannot find others or you maybe just need one more participant, you can write us an email. We will try to find other willing Operators with similar interests or we will, ourselves, run a server. In any case it's necessary that the partners of a cascade coordinate with each other so that finally a working cascade can be set up properly. |
|
||||||||||
|
|
|
|||||||||||