| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
also, snap the start time and end time to a day boundary, since most
certs in the wild seem to do this.
|
|
resolves ticket 8443.
|
|
no actual changes in behavior yet
|
|
|
|
|
|
since it's only enableable by authorities, nobody else would be able
to start their tor
|
|
|
|
I have no idea whether b0rken clients will DoS the network if the v2
authorities all turn this on or not. It's experimental. See #6783 for
a description of how to test it more or less safely, and please be
careful!
|
|
|
|
Now that circid_t is 4 bytes long, the default integer promotions will
leave it alone when sizeof(int) == 4, which will leave us formatting an
unsigned as an int. That's technically undefined behavior.
Fixes bug 8447 on bfffc1f0fc7616a25c32da2eb759dade4651659e. Bug not
in any released Tor.
|
|
|
|
(Second part of a bug8367 fix. -NM)
|
|
This fixes bug 8367, introduced in d7089ff228227259137b5a8b. Not in
any released Tor.
|
|
|
|
We don't use subversion or src/*/makefile.am any longer
|
|
|
|
|
|
This should prevent crashes on further recurrence of 8065, and help
diagnose such if they occur
|
|
|
|
|
|
|
|
Unmeasured=1 issue
|
|
This patch moves the measured_bw field and the has_measured_bw field
into vote_routerstatus_t, since only votes have 'Measured=XX' set on
their weight line.
I also added a new bw_is_unmeasured flag to routerstatus_t to
represent the Unmeasured=1 flag on a w line. Previously, I was using
has_measured_bw for this, which was quite incorrect: has_measured_bw
means that the measured_bw field is set, and it's probably a mistake
to have it serve double duty as meaning that 'baandwidth' represents a
measured value.
While making this change,I also found a harmless but stupid bug in
dirserv_read_measured_bandwidths: It assumes that it's getting a
smartlist of routerstatus_t, when really it's getting a smartlist of
vote_routerstatus_t. C's struct layout rules mean that we could never
actually get an error because of that, but it's still quite incorrect.
I fixed that, and in the process needed to add two more sorting and
searching helpers.
Finally, I made the Unmeasured=1 flag get parsed. We don't use it for
anything yet, but someday we might.
This isn't complete yet -- the new 2286 unit test doesn't build.
|
|
|
|
|
|
|
|
Instead of capping whenever a router has fewer than 3 measurements,
we cap whenever a router has fewer than 3 measurements *AND* there
are at least 3 authorities publishing measured bandwidths.
We also generate bandwidth lines with a new "Unmeasured=1" flag,
meaning that we didn't have enough observations for a node to use
measured bandwidth values in the authority's input, whether we capped
it or not.
|
|
|
|
Fixes bug 7876
|
|
Avoid the phrase "legally valid" (as opposed to valid but not legal)?
And document what functions really do.
Fix for bug 6935.
|
|
|
|
|
|
|
|
Conflicts:
src/or/channel.h
src/or/connection_or.c
src/or/cpuworker.c
|
|
|
|
|
|
Apparently there is a compiler that believes this is something to
warn about.
|
|
|
|
Stop marking every relay as having been down for one hour every
time we restart a directory authority. These artificial downtimes
were messing with our Stable and Guard flag calculations.
Fixes bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
|
|
This will get it building on systems that lack stdint.h
|
|
|
|
We shouldn't be calling choose_random_entry() for directory
conncetions; that's what choose_random_dirguard() is for.
|
|
|
|
|
|
(Cherry-picked from fc35ee4910326dc1ae718482b30e57666a71df85)
|
|
and replace it with the good old-fashioned two functions approach
|
|
now that both timers are on the same schedule, there's no point
tracking separate timers.
|
|
Relays used to check every 10 to 60 seconds, as an accidental side effect
of calling directory_fetches_from_authorities() when considering doing
a directory fetch. The fix for bug 1992 removes that side effect. At the
same time, bridge relays never had the side effect, leading to confused
bridge operators who tried crazy tricks to get their bridges to notice
IP address changes (see ticket 1913).
The new behavior is to reinstate an every-60-seconds check for both
public relays and bridge relays, now that the side effect is gone.
|
