The subversion $Id$ fields made every commit force a rebuild of
whatever file got committed.  They were not actually useful for
telling the version of Tor files in the wild.

svn:r17867

svn:r17866

svn:r17863

svn:r17862

svn:r17851

svn:r17850

Try harder to make sure we zero-out the extraneous sockaddr fields and that we set sockaddr_len.  Conceivably a backport candidate, though nothing has yet been sen to break.

svn:r17849

svn:r17836

svn:r17835

use the same download mechanism as other places.

i had to make an ugly hack around "IMPOSSIBLE_TO_DOWNLOAD+1".
we should unhack that sometime.


svn:r17834

downloading forever" thing with bridge descriptor downloads.


svn:r17833

svn:r17831

svn:r17828

svn:r17827

svn:r17826

svn:r17825

the 0.2.1.3-alpha changelog. put it back.


svn:r17824

svn:r17823

svn:r17822

svn:r17821

svn:r17820

Explain why the XXXX021 in connection_or.c was there, and explain why it doesn' actually need to get fixed in 0.2.1, I think.

svn:r17819

Replace kludgy assert with something a little less awful, and avoid needless strlcpy in rend descriptor encoding.

svn:r17818

svn:r17817

Document RELAY_EARLY cells in tor-spec.txt: proposal 110 is mostly implemented, and the rest of it will need to wait until all current Tor 0.2.0.x clients are obsolete to close.

svn:r17816

svn:r17815

svn:r17814

Extact parse-the-token-arguments to its own function, and change it to a single-pass algorithm.  This simplifies the parsing code and speeds it up a little.

svn:r17812

svn:r17811

svn:r17810

coverity thinks it's dumb to check networkstatus_v2_list in one place and not another.  Coverity has a point, even though the check may be redundant. CID 361.

svn:r17809

More compilation tweaks on Android: fix two clear errors in our code that apparently the compiler cares about there.

svn:r17808

svn:r17806

Use a consistent naming standard for header file guard macros, taking care not to collide with any system headers.  This tripped us up on Android.

svn:r17805

svn:r17804

Switch address comparisons in policies to be exact rather than semantic.  Until we do ipv6 exit policies and until we know whether we even allow ::ffff:0:0/96 addresses, there is no point in doing "semantic" comparisons.  This was also showing up on oprofile.

svn:r17803

Specifically, split compare_tor_addr_to_addr_policy() from a loop with a bunch
of complicated ifs inside into some ifs, each with a simple loop.  Rearrange
router_find_exact_exit_enclave() to run a little faster.  Bizarrely,
router_policy_rejects_all() shows up on oprofile, so precalculate it per
routerinfo.

svn:r17802

Fix bug in recent address.c patch: actually set the value of address * to 0.0.0.0 as we did before.  This makes CMP_EXACT comparisons with bitmask 0 work on address * again.

svn:r17801

svn:r17800

svn:r17799