Opened 7 years ago

Closed 3 years ago

#6588 closed enhancement (wontfix)

torouter should attempt to screw with timing analysis

Reported by: ioerror Owned by: ioerror
Priority: Medium Milestone:
Component: Archived/Torouter Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Dan is giving a talk about timing leaks at Toorcamp and he made this suggestion:

tc qdisc change dev eth0 root netem delay 3ms 1ms

The Torouter should probably do this for each interface. We should write remotely detectable timing bugs and see if it makes a difference.

Child Tickets

Change History (1)

comment:1 Changed 3 years ago by irl

Resolution: wontfix
Severity: Normal
Status: newclosed

This should probably be solved in Tor, as opposed to torouter specifically. Timing correlation attacks are well understood, and torouter is no longer an active project, so closing this as no longer relevant. See also: #20747.

Note: See TracTickets for help on using tickets.