svn:r18102

Now that we can hit the end of router_rebuild_store before chunk_list is set, we need to test it before freeing it.

svn:r18101

It was dumb to have an "announce the value if it's over 0" version of
the code coexisting with an "announce the value if it's at least N"
version.  Retain the latter only, with N set to 1.

Incidentally, this should fix a Coverity REVERSE_INULL warning.

svn:r18100

svn:r18099

svn:r18097

Fix up (I hope) most ot the things that coverity suddenly claimed were REVERSE_INULL.  This is what we get for bragging about being down to 0 issues.

svn:r18096

svn:r18095

svn:r18094

svn:r18074

svn:r18073

There was a field that _HT_FOI_INSERT was never setting. Everything that calls _HT_FOI_INSERT was setting it via tor_malloc_zero, but that's fragile.

svn:r18064

Bugfix on 0.2.1.7-alpha.  Backport candidate. Fixes bug 905.

svn:r18063

svn:r18024

svn:r18019

svn:r18015

Unfortunately, old Libevents don't _put_ a version in their headers, so
this can get a little tricky.  Fortunately, the only binary-compatibility
issue we care about is the size of struct event.  Even more fortunately,
Libevent 2.0 will let us keep binary compatiblity forever by letting us
decouple ourselves from the structs, if we like.

svn:r18014

five days old. Otherwise if Tor is off for a long time and then
starts with cached descriptors, it will try to use the onion
keys in those obsolete descriptors when building circuits. Bugfix
on 0.2.0.x. Fixes bug 887.


svn:r17993

a destroy cell from our first hop.


svn:r17991

svn:r17989

svn:r17986

svn:r17985

cell back), avoid using that OR connection anymore, and also
tell all the one-hop directory requests waiting for it that they
should fail. Bugfix on 0.2.1.3-alpha.


svn:r17984

Fixes the bug part of bug 789.

svn:r17983

svn:r17982

svn:r17980

svn:r17974

svn:r17973

svn:r17971

using the wrong onion key), we were dropping it and letting the
client time out. Now actually answer with a destroy cell. Bugfix
on 0.0.2pre8.


svn:r17970

Jan 06 13:03:57.309 [info] networkstatus_set_current_consensus(): Loaded an obsolete consensus. Discarding.
Jan 06 13:03:57.309 [warn] Couldn't load consensus networkstatus from "bridge/cached-consensus"

doesn't need a real warn.


svn:r17969

svn:r17968

svn:r17966

svn:r17963

svn:r17960

to anybody who asks, now that extrainfo docs include potentially
sensitive aggregated client geoip summaries.


svn:r17958

Make dirserv_get_routerdesc_fingerprints() treat extrainfos with send_unencrypted==0 correctly.  Irrelevant, since we will soon never send them at all.

svn:r17953

When we made bridge authorities stop serving bridge descriptors over
unencrypted links, we also broke DirPort reachability testing for
bridges. So bridges with a non-zero DirPort were printing spurious
warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.


svn:r17945

bugs fixed to keep waiting. i still need to track down bug 709
first though, since i am increasingly thinking it's a real bug.


svn:r17944

svn:r17924

descriptors shortly after startup, and then briefly resume
after a new bandwidth test and/or after publishing a new bridge
descriptor. Bridge users that try to bootstrap from them would
get a recent networkstatus but would get descriptors from up to
18 hours earlier, meaning most of the descriptors were obsolete
already. Reported by Tas; bugfix on 0.2.0.13-alpha.


svn:r17920