Opened 16 months ago

Last modified 15 months ago

#30348 new enhancement

Update padding negotiation with preference menu, response delays

Reported by: mikeperry Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: wtf-pad
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor: Sponsor2-can


As we add more padding machines across different Tor versions, padding negotiation will become more and more likely to fail. We could send a preference list to the relay instead, so that if any of the machines we could use are supported, they would be chosen in preference order.

We could also add a delay field asking the relay to delay before responding, as an alternate way to deal with concerns in #30172.

Child Tickets

Change History (1)

comment:1 Changed 15 months ago by mikeperry

This will be useful if we have different sets of machines across different Padding protover versions.

So long as each Padding protover value contains a fixed set of machines that is well known, we can negotiate, though. Toss up.

Note: See TracTickets for help on using tickets.