[tor-dev] Support for mix integration research

Katharina Kohls katharina.kohls at rub.de
Wed Feb 24 09:39:50 UTC 2016

> Does differentiating traffic into multiple timing classes make traffic timing analysis easier?
> (For example, while high-latency traffic is better protected from fingerprinting, low-latency traffic is easier to identify and fingerprint.)

The opposite should be the case, as the delaying of HL traffic should
slightly obfuscate the traffic patterns of LL packets. The idea is to
send everything through the mix but only delay what doesn't require
performance with low latencies.

Nevertheless, we are not sure if it's more secure to let the user decide
delays for packets (like in the alpha-mixing approach) to get a greater
fraction of the overall traffic delayed or to assign random delays
within the relay, based on a classification of the packets.
> The latest stable release is Tor

... and as there is also the new scheduler included we will continue our
work with the latest version :)

M.Sc. Katharina Kohls

Ruhr-University Bochum
Research Group Information Security
Uni­ver­si­täts­stras­se 150
ID 2/123
44780 Bochum / Germany

Phone: +49 234 / 32 - 26991
Web: www.infsec.rub.de

More information about the tor-dev mailing list