When we tried to use the deprecated non-threadsafe evdns
interfaces in Libevent 2 without using the also-deprecated
event_init() interface, Libevent 2 would sensibly crash, since it
has no guess where to find the Libevent library.
Here we use the evdns_base_*() functions instead if they're
present, and fake them if they aren't.
* debian-merge: (52 commits)
Ship debian source with src/test/test.h
New testsuite location
New upstream version
Fix testsuite call.
bump to 0.2.2.4-alpha
Don't set unreachable from dirvote unless we've been running a while.
correct the spec for the stream_bw event.
fix a bug where we were decrementing the wrong bucket
remove some dead code. some of it was tickling coverity.
add blurbs for recent alpha releases
Fix a memleak when throwing away some build times
amend changelog for recent commits, plus clean up
Tweak an assert that shouldn't fire either way.
Tweak values for when to discard all of our history.
Remove another overzealous assert.
try to stem the 'sea of fail'
fix the wiki link in doc pages. remove obsolete FAQ.
Ignore one-hop circuits for circuit timeout calc
Move Tonga to an alternate IP address
update spec to reflect change in Fast definition
...
Upstream failed to ship src/test/test.h. Ship it in debian/ and
manually copy it in place during configure and clean up in clean. Let's
not use the patch system as this will most likely be rectified by next
release.
* commit 'tor-0.2.2.4-alpha': (49 commits)
Fix testsuite call.
bump to 0.2.2.4-alpha
Don't set unreachable from dirvote unless we've been running a while.
correct the spec for the stream_bw event.
fix a bug where we were decrementing the wrong bucket
remove some dead code. some of it was tickling coverity.
add blurbs for recent alpha releases
Fix a memleak when throwing away some build times
amend changelog for recent commits, plus clean up
Tweak an assert that shouldn't fire either way.
Tweak values for when to discard all of our history.
Remove another overzealous assert.
try to stem the 'sea of fail'
fix the wiki link in doc pages. remove obsolete FAQ.
Ignore one-hop circuits for circuit timeout calc
Move Tonga to an alternate IP address
update spec to reflect change in Fast definition
Move moria1 to a nearby IP address
Dir auths reject relays running < Tor 0.1.2.14
Fix 1108: Handle corrupt or large build times state.
...
This is a possible fix for bug 1023, where if we vote (or make a v2
consensus networkstatus) right after we come online, we can call
rep_hist_note_router_unreachable() on every router we haven't connected
to yet, and thereby make all their uptime values reset.
"neonomad" pointed out on or-talk that the order is opposite from the
intuitive order. explain why. we chose to fix the spec rather than the
code because there are controllers like torflow that already expect
the current behavior.
This seems to be happening to me a lot on a garbage DSL line.
We may need to come up with 2 threshholds: a high short onehop
count and a lower longer count.
Don't count one-hop circuits when we're estimating how long it
takes circuits to build on average. Otherwise we'll set our circuit
build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
Directory authorities now reject Tor relays with versions less than
0.1.2.14. This step cuts out four relays from the current network,
none of which are very big.
Previously, tor-gencert would call RSA_generate_key() directly.
This won't work on Android, which removes the (deprecated since
OpenSSL 0.9.8) function. We can't call RSA_generate_key_ex()
unconditionally either, since that didn't exist before 0.9.8.
Instead, we must call our own crypto_pk_generate_key_with_bits,
which knows how to call RSA_generate_key or RSA_generate_key_ex as
appropriate.
[Based on patch by Nathan Freitas]
Apparently the Android developers dumped OpenSSL's support for hardware
acceleration in order to save some memory, so you can't build programs using
engines on Android.
[Patch revised by nickm]
This shouldn't be necessary, but apparently the Android cross-compiler
doesn't respect -I as well as it should. (-I is supposed to add to the
*front* of the search path. Android's gcc wrapper apparently likes to add to
the end. This is broken, but we need to work around it.)
Found by coverity
test_mem_op_hex was leaking memory, which showed up in a few
tests.
Also, the dir_param test had a memleak of its own.
Found by Coverity
