| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |\
| |
| |
| |
| | |
Conflicts:
src/or/dirserv.c
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
There are still quite a few 0.2.3.2x relays running for x<5, and while I
agree they should upgrade, I don't think cutting them out of the network
is a net win on either side.
|
| |\ \ |
|
| | | | |
|
| |/ /
| |
| |
| | |
Resolves ticket 11149.
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/or/router.c
src/test/test_dir.c
|
| | | |
| | |
| | |
| | | |
(rather than router->address)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
since router_parse_entry_from_string() already checks whether
!tor_inet_aton(router->address, &in)
(And no need to print address, since router_describe does that.)
|
| | |/
|/| |
|
| | |
| |
| |
| | |
(This was a squash commit, but I forgot to squash it. Sorry! --Nick)
|
| | |
| |
| |
| |
| |
| | |
The remaining vestige is that we continue to publish the V2dir flag,
and that, for the controller, we continue to emit v2 directory
formats when requested.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
As a bridge authority, before we create our networkstatus document, we
should compute the thresholds needed for the various status flags
assigned to each bridge based on the status of all other bridges. We
then add these thresholds to the networkstatus document for easy access.
Fixes for #1117 and #9859.
|
| | |
| |
| |
| | |
Addresses ticket 9206.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We previously used FILENAME_PRIVATE identifiers mostly for
identifiers exposed only to the unit tests... but also for
identifiers exposed to the benchmarker, and sometimes for
identifiers exposed to a similar module, and occasionally for no
really good reason at all.
Now, we use FILENAME_PRIVATE identifiers for identifiers shared by
Tor and the unit tests. They should be defined static when we
aren't building the unit test, and globally visible otherwise. (The
STATIC macro will keep us honest here.)
For identifiers used only by the unit tests and never by Tor at all,
on the other hand, we wrap them in #ifdef TOR_UNIT_TESTS.
This is not the motivating use case for the split test/non-test
build system; it's just a test example to see how it works, and to
take a chance to clean up the code a little.
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A new option TestingV3AuthVotingStartOffset is added which offsets the
starting time of the voting interval. This is possible only when
TestingTorNetwork is set.
This patch makes run_scheduled_events() check for new consensus
downloads every second when TestingTorNetwork, instead of every
minute. This should be fine, see #8532 for reasoning.
This patch also brings MIN_VOTE_SECONDS and MIN_DIST_SECONDS down from
20 to 2 seconds, unconditionally. This makes sanity checking of
misconfiguration slightly less sane.
Addresses #8532.
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | | |
This is another fix to try to mitigate recurrences of 8031/8822.
|
| |\| | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It appears that moria1 crashed because of one instance of this (the
one in router_counts_toward_thresholds). The other instance I fixed
won't actually have broken anything, but I think it's more clear this
way.
Fixes bug 8833; bugfix on 0.2.4.12-alpha.
|
| |\| | |
|
| | | |
| | |
| | |
| | | |
Implements #8711.
|
| |\| |
| | |
| | |
| | |
| | | |
Conflicts:
src/common/crypto.c
|
| | |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/or/dirserv.c
src/or/dirserv.h
src/test/test_dir.c
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It sure is a good thing we can run each test in its own process, or
else the amount of setup I needed to do to make this thing work
would have broken all the other tests.
Test mocking would have made this easier to write too.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now we can compute the hash and signature of a dirobj before
concatenating the smartlist, and we don't need to play silly games
with sigbuf and realloc any more.
|
| | | | | |
|
| | | | | |
|
| |\| | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/or/dirserv.c
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We were using credible_bandwidth to build the fast_bandwidth
threshold, but comparing it to bandwidth_for_router.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We were mixing bandwidth file entries (which are in kilobytes) with
router_get_advertised_bw() entries, which were in bytes.
Also, use router_get_advertised_bandwidth_capped() for credible_bandwidth.
|
| |/ / / |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This adds a new option to fix bug 8508 which broke chutney
networks. The bug was introduced by 317d16de.
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | | |
Resolves ticket 6164
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
dirserv_query_measured_bw_cache()
|
| | | | |
|
| | | | |
|