| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
This is an automatically generated commit, from the following perl script,
run with the options "-w -i -p".
s/smartlist_string_num_isin/smartlist_contains_int_as_string/g;
s/smartlist_string_isin((?:_case)?)/smartlist_contains_string$1/g;
s/smartlist_digest_isin/smartlist_contains_digest/g;
s/smartlist_isin/smartlist_contains/g;
s/digestset_isin/digestset_contains/g;
|
| |\ |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/or/cpuworker.c
src/or/or.h
src/test/bench.c
|
| | |
| |
| |
| | |
"works for me"
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
I think this is actually his third code review of this branch so far.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
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.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Needs manpage update and testing still..
|
| | | |
| | |
| | |
| | | |
This is purely for informational reasons for debugging.
|
| | | |
| | |
| | |
| | |
| | | |
In addition to all the other ways to make directory gurads not go,
you can now set UseEntryGuardsAsDirGuards to 0.
|
| | | |
| | |
| | |
| | | |
Implements proposal 207; ticket 6526.
|
| |/ / |
|
| |/
|
|
|
| |
Also, add a hack Roger suggested where we're more patient if no circuits are
opened yet.
|
| | |
|
| |
|