| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| |
| |
| | |
Conflicts:
src/or/entrynodes.c
|
| | |
| |
| |
| |
| |
| |
| |
| | |
My first implementation was broken, since it returned "whether there
is one bridge" rather than "how many bridges."
Also, the implementation for the n_options_out feature in
choose_random_entry_impl was completely broken due to a missing *.
|
| | |
| |
| |
| |
| |
| | |
This is meant to be a better bug 9229 fix -- or at least, one more
in tune with the intent of the original code, which calls
router_retry_directory_downloads() only on the first bridge descriptor.
|
| |\ \
| |/
|/| |
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| | |
Conflicts:
src/or/router.c
src/test/test_dir.c
|
| | |
| |
| |
| | |
resolves ticket 5528.
|
| | |
| |
| |
| | |
(rather than router->address)
|
| | |
| |
| |
| | |
since it was always just the string version of "addr" anyway
|
| | |
| |
| |
| |
| |
| | |
The old behavior was that NULL matched only bridges without known
identities; the correct behavior is that NULL should match all
bridges (assuming that their addr:port matches).
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Conflicts:
src/or/entrynodes.c
|
| | | |
| | |
| | |
| | |
| | | |
By Roger at
https://trac.torproject.org/projects/tor/ticket/5018#comment:11.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Implements ticket 9934; patch from "ra"
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also fix a bug where if the guard we choose first doesn't answer, we
would try the second guard, but once we connected to the second guard
we would abandon it and retry the first one, slowing down bootstrapping.
The fix in both cases is to treat all our initially chosen guards as
acceptable to use.
Fixes bug 9946.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
(These have proved invaluable for other global accessors.)
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Change the global circ_times to a static variable and use
accessor functions throughout the code, instead of
accessing it directly.
|
| |\| | |
|
| | | |
| | |
| | |
| | |
| | | |
Now a user who changes only NumEntryGuards will get the behavior she
expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
|
| |\| | |
|
| | | |
| | |
| | |
| | |
| | | |
We now know the bug is present in 0.2.4.12-alpha too. It should be fixed in
0.2.4.13-alpha, though.
|
| |\| | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
There was a bug in Tor prior to 0.2.4.10-alpha that allowed counts to
become invalid. Clipping the counts at startup allows us to rule out
log messages due to corruption from these prior Tor versions.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
It can never be NULL, since it's an array in bridge_line_t.
Introduced in 266f8cddd87f. Found by coverity; this is CID 992691. Bug
not in any released Tor.
|
| |\| | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This caused an assertion failure when pruning guards.
Fixes bug #8553; bug not in any released Tor.
|
| |\| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
doc/tor.1.txt
src/or/circuitbuild.c
src/or/config.c
src/or/or.h
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | | |
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.
|
| | | | |
|
| | | | |
|
| | |/ |
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
In addition to rejecting them post-hoc, avoid picking them in the
first place. This makes us less likely to decide that we can't add
guards at all.
|
| | |/
| |
| |
| |
| |
| | |
Apparently something in the directory guard code made it possible
for the same node to get added as a guard over and over when there
were no actual running guard nodes.
|
| | |
| |
| |
| | |
(Second part of a bug8367 fix. -NM)
|
| | |
| |
| |
| |
| | |
This fixes bug 8367, introduced in d7089ff228227259137b5a8b. Not in
any released Tor.
|
| | |
| |
| |
| |
| | |
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;
|
| |\ |
|
| | | |
|