Opened 3 years ago

Last modified 12 months ago

#25574 new defect

Eliminate "silent-drop" side channels in Tor protocol — at Version 4

Reported by: mikeperry Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: guard-discovery-stats
Cc: dmr Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by dmr)

There are lots of ways to inject data into Tor streams, and this is a vector of attack for guard discovery and confirmation ("DropMark" attack):

I have a branch that tries to eliminate a pile of these from a while ago, but it has lots of false positives due to the common occurrence of invalid stream IDs in practice (see #25573).

I think we may want to do #25573 before trying to merge that branch.

Child Tickets

#25573closedTrack half-closed stream IDsCore Tor/Tor

Change History (4)

comment:1 Changed 3 years ago by nickm

I really want to ask for a proposal on this -- if only a formal list of the stuff you want to change here.

comment:2 Changed 2 years ago by dmr

Cc: dmr added

comment:3 Changed 2 years ago by asn

Milestone: Tor: unspecified

comment:4 Changed 2 years ago by dmr

Description: modified (diff)

Adding parenthetical to tie that term 'DropMark' to the paper (it might not otherwise be obvious by context).

Note: See TracTickets for help on using tickets.