| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
Most of these are simple. The only nontrivial part is that our
pattern for using ENUM_BF was confusing doxygen by making declarations
that didn't look like declarations.
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
src/or/entrynodes.c
|
| | |
|
| |
| |
| |
| | |
Implements ticket 9934; patch from "ra"
|
|\ \
| |/
|/|
| |
| |
| | |
Conflicts:
src/common/util.c
src/or/entrynodes.h
|
| |
| |
| |
| |
| |
| | |
- Make parse_bridge_line() return a struct.
- Make bridge_add_from_config() accept a struct.
- Make string_is_key_value() less hysterical.
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
We shouldn't be calling choose_random_entry() for directory
conncetions; that's what choose_random_dirguard() is for.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Now we can specify to skip bridges that wouldn't be able to answer the
type of dir fetch we're launching.
It's still the responsibility of the rest of the code to prevent us from
launching a given dir fetch if we have no bridges that could handle it.
|
| |
| |
| |
| |
| |
| | |
Now as we move into a future where most bridges can handle microdescs
we will generally find ourselves using them, rather than holding back
just because one of our bridges doesn't use them.
|
|/
|
|
|
| |
I think we want both sets of messages to appear independently to help us know
what needs tuning.
|
|
|
|
|
|
|
| |
Path use bias measures how often we can actually succeed using the circuits we
actually try to use. It is a subset of path bias accounting, but it is
computed as a separate statistic because the rate of client circuit use may
vary depending on use case.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
We need to use the success count or the use count depending on the consensus
parameter.
|
| |
| |
| |
| | |
Let's hope this solves the rounding error issue..
|
| |
| |
| |
| |
| |
| | |
For consistency and great justice.
Ok, mostly consistency.
|
| |
| |
| |
| |
| | |
Since we've generalized what we can count from (first or second hop), we
should generalize the variable and constant naming too.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Turns out there's more than one way to block a tagged circuit.
This seems to successfully handle all of the normal exit circuits. Hidden
services need additional tweaks, still.
|
| | |
|
| | |
|
| |
| |
| |
| | |
May want to squash this forward or back..
|
| |
| |
| |
| | |
This is purely for informational reasons for debugging.
|
| |
| |
| |
| | |
Implements proposal 207; ticket 6526.
|
|/ |
|
|
|
|
|
| |
Also, add a hack Roger suggested where we're more patient if no circuits are
opened yet.
|
|
|