We already do this for libevent; let's do it for openssl too.

For now, I'm making it always a warn, since this has caused some
problems in the past.  Later, we can see about making it less severe.

OTOH, log the Libevent and OpenSSL versions on the first line when
we're starting Tor.

This is the preferred filename to use with Autoconf 2.50 and later.

specifically, specify what sort of routers we're fetching.

Reserve it for when new directory information arrives in response to
a fetch.

Resolves ticket 6760.

Addresses bug 6759.

Bugfix for #6732.

Fix for #6251

We are doing this merge to avoid taking the patch from
"nickm/disable_pathbias_warnings_v2" into 0.2.4 -- we're going to try
to fix the pathbias code for real here.

We've had over two months to fix them, and didn't.  Now we need
0.2.3.x stable.  Yes, it would be cool to get this working in
0.2.3.x, but not at the expense of delaying every other feature that
_does_ work in 0.2.3.x.  We can do a real fix in 0.2.4.

Conflicts:
	src/or/policies.c

a router that another router wasn't already connected to.

This can create a remote crash opportunity for/against directory
authorities.

This is important, since otherwise an attacker can use timing info
to probe the internal network.

Also, add an option (ExtendAllowPrivateAddresses) so that
TestingTorNetwork won't break.

Fix for bug 6710; bugfix on all released versions of Tor.

Jim Meyering authored Aug 27, 2012 and Nick Mathewson committed Aug 27, 2012

(commit message by nickm)