Opened 7 years ago

Closed 3 years ago

#9762 closed enhancement (wontfix)

Make a torflow option that starts every testing circuit at a local Tor relay first

Reported by: arma Owned by: aagbsn
Priority: Medium Milestone:
Component: Core Tor/Torflow Version:
Severity: Blocker Keywords:
Cc: Actual Points:
Parent ID: #9368 Points:
Reviewer: Sponsor:


In the future we want to be able to turn on throttling at the entry guards (#9368). The main impediment is that the bwauths would then get throttled because they're not relays (#9369).

weasel suggests an alternate approach would be for his bwauth Tor client to make its first hop to tor26.

(Then we could add a feature to tor26 to not throttle -- or heck, maybe we don't/shouldn't throttle connections from localhost or equivalent by default. In any case this ticket is for the torflow changes, which historically require more effort and time since we have no torflow people.)

You might say "but wait, having the bwauths not go through the authorities is good, because the vantage points are anonymous so they're harder to game!" But if we're turning the bwauths into relays they're not going to do so well at anonymity anyway.

Child Tickets

Change History (3)

comment:1 Changed 7 years ago by aagbsn

Sketched out some rough ideas here:

So a few thoughts:

one, it's cumbersome to specify the relay by IP:Port, so I used the idhex here.
two, if I do it this way the relay must be in the consensus in order to learn about it.

Is this going to work for the intended use case?

comment:2 Changed 7 years ago by arma

Parent ID: #9368

comment:3 Changed 3 years ago by teor

Resolution: wontfix
Severity: Blocker
Status: newclosed

We never turned on perconnbwrate in the consensus, so these tickets are "wontfix".

Note: See TracTickets for help on using tickets.