Update to the September 2013 GeoIP database.
Merge remote-tracking branch 'origin/maint-0.2.2' into maint-0.2.3
Merge remote-tracking branch 'origin/maint-0.2.3' into maint-0.2.4
Document that disabledebuggerattachment prevents cores
Stop sending the current time in client NETINFO handshakes.

Implements part of proposal 222.
Get ready to stop sending timestamps in INTRODUCE cells

For now, round down to the nearest 10 minutes.  Later, eliminate entirely by
setting a consensus parameter.

(This rounding is safe because, in 0.2.2, where the timestamp mattered,
REND_REPLAY_TIME_INTERVAL was a nice generous 60 minutes.)
Remove the timestamp from AUTHENTICATE cells; replace with random bytes

This isn't actually much of an issue, since only relays send
AUTHENTICATE cells, but while we're removing timestamps, we might as
well do this too.

Part of proposal 222.  I didn't take the approach in the proposal of
using a time-based HMAC, since that was a bad-prng-mitigation hack
from SSL3, and in real life, if you don't have a good RNG, you're
hopeless as a Tor server.
Round down hidden service descriptor publication times to nearest hour

Implements part of proposal 222.  We can do this safely, since
REND_CACHE_MAX_SKEW is 24 hours.
Avoid error by not saying which intro cell type I mean
Merge branch 'no_client_timestamps_024_v2' into maint-0.2.4
back out most of 1d0ba9a

this was causing directory authorities to send a time of 0 on all
connections they generated themselves, which means everybody reachability
test caused a time skew warning in the log for that relay.

(i didn't just revert, because the changes file has been modified by
other later commits.)
Relays should send timestamp in NETINFO.

This avoids skew warnings as authorities test reachability.

Fix 9798; fix not on any released Tor.
Fix a compilation warning with older gcc
Always call circuit_n_chan_done(chan, 0) from channel_closed()
Merge branch 'maint-0.2.4' into release-0.2.4
fold in changes entries