[tor-bugs] #8193 [Tor Cloud]: Is this the best way to handle bandwidth limitations for bridges?
Tor Bug Tracker & Wiki
blackhole at torproject.org
Fri Feb 8 22:07:23 UTC 2013
#8193: Is this the best way to handle bandwidth limitations for bridges?
-------------------------+--------------------------------------------------
Reporter: cypherpunks | Owner: runa
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Tor Cloud | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
The Amazon ec2 bridge images contain the following lines in the torrc
file:
{{{
AccountingStart week 1 10:00
AccountingMax 10 GB
}}}
This means that each of those bridges suspends its service if either 10 GB
data has been uploaded or downloaded in the accounting period (not
combined values).
Is this really the best setting given the options which are offered by Tor
at the moment? Wouldn't it be better to set the "BandwidthRate" option
instead of Accounting* options? As I understand it, with the
!BandwidthRate option set, the bridges would likely be slower, but
available all the time.
From the user experience: Isn't it quite bad to have a bridge that stops
working at some point? The user even doesn't get informed whether the
bridge has stopped working indefinitely or just suspended for some days.
There should be more explanations for people who have just learned about
Tor...
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8193>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list