Opened 4 months ago

Closed 4 months ago

Last modified 4 months ago

#30667 closed defect (not a bug)

Shuffling, delaying and generating false packets at random

Reported by: torlove Owned by:
Priority: Medium Milestone:
Component: - Select a component Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

A gentleman has gone on a television program called Keiser Report on RT (Russian broadcaster). He gas expressed concerns about how it may be trivial for an adversary that controls a vast number of nodes, to de-anonymise the data transfer.

Episode number is 1386.

I can imagine that the network will be slower if we adopt these ideas in the title, but it may be worth it?

Child Tickets

Change History (3)

comment:1 Changed 4 months ago by torlove

The other question is whether we force browsers to become small scale nodes in themselves. Mobile devices might not be included.

The gentleman who explained the issues is a Harry Halpin, he says he studied machine learning if my memory serves.

comment:2 Changed 4 months ago by dgoulet

Resolution: not a bug
Status: newclosed

Tor design is low-latency so shuffling + delays is more in the mixnet domain.

comment:3 Changed 4 months ago by nickm

Attempts to do delays within Tor have been considered historically, but they're still an area of active research. Some of the papers on https://freehaven.net/anonbib are relevant here. Re-ordering has potential to introduce side-channels that nobody knows how to solve right now: https://lists.torproject.org/pipermail/tor-dev/2018-November/013562.html . Right now, padding seems like the most likely way to hinder correlation attacks on a low-latency network, but there is a lot more research to be done here too.

Note: See TracTickets for help on using tickets.