svn:r3095

svn:r3094

svn:r3093

More win32 fixes: 1) tolerate extra "readable" events better. 2) when being multithreaded, leave parent fdarray open.


svn:r3092

svn:r3091

svn:r3089

svn:r3088

svn:r3087

svn:r3086

if we're asked to resolve an IP.foo.exit.


svn:r3085

svn:r3084

than just chopping them off


svn:r3083

we remove the .foo.exit part of the address.


svn:r3082

svn:r3081

svn:r3080

svn:r3079

New circuit building strategy: keep a list of ports that we've used in                     the past 6 hours, and always try to have 2 circuits open or on the way
that will handle each such port. (We can extend this to include addresses
if exit policies shift to require that.) Seed us with port 80 so web
browsers won't complain that Tor is "slow to start up".

This was necessary because our old circuit building strategy just involved
counting circuits, and as time went by we would build up a big pile of
circuits that had peculiar exit policies (e.g. only exit to 9001-9100)
which would take up space in the circuit pile but never get used.

Fix router_compare_addr_to_addr_policy: it was not treating a port of *
as always matching, so we were picking reject *:* nodes as exit nodes too.

If you haven't used a clean circuit in an hour, throw it away, just to
be on the safe side.

This means after 6 hours a totally unused Tor client will have no
circuits open.


svn:r3078

svn:r3077

svn:r3076

sometimes picking middleman nodes as our last hop, which wasn't
very useful.


svn:r3075

close, if we're planning to wait to flush it.

This is important because we were sending a socks reject back if we're
closing and hadn't already sent one, but it wasn't actually getting
written since the conn was already marked-for-close.


svn:r3074

Stop keeping track of num_retries for apconns, since they expire
after 60 seconds anyway.

When warning about retrying or giving up, print the address, so
the user knows which one it's talking about.


svn:r3073

waiting for its connected cell, we were calculating time from when the
ap_conn was created. So if it waited say 20 seconds before being attached,
then we would immediately decide that the circuit had timed out.

Also, make circuit_dump_by_conn() display actual circuit progress,
including circuits that haven't been attached to the conn yet but
hope to when it finishes connecting.


svn:r3072

just because it says snprintf doesn't mean it's a noop


svn:r3071

svn:r3070

darn these bugs


svn:r3069

svn:r3068

svn:r3067

svn:r3066

svn:r3065

Be more proactive about noticing underflows: size_t values greater than 0x800...00 are likely to be trouble.


svn:r3064

svn:r3063

svn:r3062

* Add a few 'date' calls in debian/rules, so I can see how long building the docs takes on autobuilders.


svn:r3060

svn:r3058

svn:r3057

svn:r3056

svn:r3055

svn:r3054

svn:r3053