redundant, and is definitely confusing. we should take it out
in 0.2.2.x and see who squeaks.


svn:r18383

svn:r18299

svn:r18102

Preserve reporting of stream end reasons to the local control
port.  They were lost in the changes for Proposal 148.



svn:r17911

svn:r17888

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

Use the literal parse of an address in dns_resolve_impl if parsing the address as an ipv4 or ipv6 address _succeeded_.  Not if it failed.  Bug introduced in r17707 (post 0.2.1.8-alpha), and found by xiando.

svn:r17758

Move in-addr.arpa parsing and generation into address.c, and simplify the code that does it elsewhere.  Incidentally, this lets exit servers answer requests for ip6.arpa addresses.

svn:r17707

Replace calls to time(NULL) that occur on the order of once per read, one per write, or once per cell with calls to a function that looks at a cached value of time.  This is tricksy to benchmark, since it will only help on systems where time() is a syscall and syscalls are relatively slow.

svn:r17690

svn:r17681

svn:r17663

svn:r17662

Use ctags and a python script to find identifiers that are never used anywhere, and remove the ones that we really want gone.

svn:r17651

svn:r17643

This patch makes every RELAY_COMMAND_END cell that we send pass through one of two functions: connection_edge_end and relay_send_end_cell_from_edge.  Both of these functions check the circuit purpose, and change the reason to MISC if the circuit purpose means that it's for client use.

svn:r17612

like 'begin' relay cells.


svn:r17442

svn:r17275

Patch from rovv: send back END cell in response to connect attempts to nonexistent hidden service port.

svn:r17137

Patch from mwenge: update TrackHostExits mapping expiry times when the mappings are used, so that they expire a while after their last use, not a while after their creation.

svn:r17004

Commit fix for bug 807 from mwenge: send CLOSED controller event for reverse dns resolve, not FAILED.

svn:r16985

svn:r16983

Add patch 4 from Karsten for proposal 121, slightly modified.  Karsten should definitely re-review the bits I changed.

svn:r16955

Patch from roger for 752, but with more comments: When we get an A.B.exit:P address, and B would reject most connections to P, but we do not know whether it would allow A, then allow the connection to procede.  Bugfix, amusingly, on 0.0.9rc5.

svn:r16944

svn:r16785

svn:r16779

jake through socks4 and socks5 failure codes


svn:r16651

svn:r16474

 Fix more compile errors on BSD pf stuff. How about now?


svn:r16472

Oops.  On recent linux kernels we were not detecting the linux/netfilter_ipv4.h header properly, since we needed to have in_addr and in6_addr and __u32 defined before trying to include it.  Fix that.

svn:r16460

 Make the TransPort input code handle IPv6 addresses, I hope.  This code may not compile.  Possibly fix bug 796.


svn:r16459

 Patch from Christopher Davis: open /dev/pf before dropping privileges.  Fixes bug 782.  Backport candidate.


svn:r16450

 Initial conversion of uint32_t addr to tor_addr_t addr in connection_t and related types.  Most of the Tor wire formats using these new types are in, but the code to generate and use it is not.  This is a big patch.  Let me know what it breaks for you.


svn:r16435

 Make circid_t and streamid_t get used instead of uint16_t; it is possible we will soon want to make circid_t change to uint32_t.


svn:r16155

 In connection_edge_destroy, send a stream status control event when we have an AP connection.  Previously, we would send an event when the connection was AP and non-AP at the same time.  This didn't work so well.  Patch from Anonymous Remailer (Austria).  Backport candidate.


svn:r16143

their responses even for begin_dir conns. Now clients who only ever use
begin_dir connections still have a way to learn their IP address. Should
fix bug 737. Reported by goldy.


svn:r15571

svn:r15434

If you have more than one bridge but don't know their keys,
you would only learn a request for the descriptor of the first one
on your list. (Tor considered launching requests for the others, but
found that it already had a connection on the way for $0000...0000
so it didn't open another.)
If you have more than one bridge but don't know their keys, and the
connection to one of the bridges failed, you would cancel all
pending bridge connections. (After all, they all have the same
digest.)


svn:r15366

> ah.
> yes, i think you're right. i was thinking 3-hop, but i think it is 1-hop.


svn:r15235

reaching relays.


svn:r15116

svn:r15115