Here is a quick update to tor.
Changes in version 0.1.0.16 - 2006-01-02
o Crash bugfixes on 0.1.0.x:
- On Windows, build with a libevent patch from "I-M Weasel" to avoid
corrupting the heap, losing FDs, or crashing when we need to
resize
the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
- It turns out sparc64 platforms crash on unaligned memory access
too -- so detect and avoid this.
- Handle truncated compressed data correctly (by detecting it and
giving an error).
- Fix possible-but-unlikely free(NULL) in control.c.
- When we were closing connections, there was a rare case that
stomped on memory, triggering seg faults and asserts.
- Avoid potential infinite recursion when building a descriptor. (We
don't know that it ever happened, but better to fix it anyway.)
- We were neglecting to unlink marked circuits from soon-to-close OR
connections, which caused some rare scribbling on freed memory.
- Fix a memory stomping race bug when closing the joining point of
two
rendezvous circuits.
- Fix an assert in time parsing found by Steven Murdoch.
o Other bugfixes on 0.1.0.x:
- When we're doing reachability testing, provide more useful log
messages so the operator knows what to expect.
- Do not check whether DirPort is reachable when we are suppressing
advertising it because of hibernation.
- When building with -static or on Solaris, we sometimes needed
-ldl.
- One of the dirservers (tor26) changed its IP address.
- When we're deciding whether a stream has enough circuits around
that can handle it, count the freshly dirty ones and not the ones
that are so dirty they won't be able to handle it.
- When we're expiring old circuits, we had a logic error that caused
us to close new rendezvous circuits rather than old ones.
- Give a more helpful log message when you try to change ORPort via
the controller: you should upgrade Tor if you want that to work.
- We were failing to parse Tor versions that start with "Tor ".
- Tolerate faulty streams better: when a stream fails for reason
exitpolicy, stop assuming that the router is lying about his exit
policy. When a stream fails for reason misc, allow it to retry
just
as if it was resolvefailed. When a stream has failed three times,
reset its failure count so we can try again and get all three
tries.
o
Thanks to Thomas Sjgren for prompting me to get this out.
jon
Index: tor//Makefile
===================================================================
RCS file: /cvs/ports/net/tor/Makefile,v
retrieving revision 1.17
diff -r1.17 Makefile
5c5
< DISTNAME= tor-0.1.0.15
---
> DISTNAME= tor-0.1.0.16
Index: tor//distinfo
===================================================================
RCS file: /cvs/ports/net/tor/distinfo,v
retrieving revision 1.15
diff -r1.15 distinfo
1,4c1,4
< MD5 (tor-0.1.0.15.tar.gz) = b2f1002da96ebfbfac7edf2272733967
< RMD160 (tor-0.1.0.15.tar.gz) = e7af128a5eedac98d3212a2cb694a257f415de9f
< SHA1 (tor-0.1.0.15.tar.gz) = d985a5f9ac0d1fc3121e8b79e196f76cfa462982
< SIZE (tor-0.1.0.15.tar.gz) = 632080
---
> MD5 (tor-0.1.0.16.tar.gz) = 13631507b8eeee5d6e8fd245dc3eef4f
> RMD160 (tor-0.1.0.16.tar.gz) = f932433aa3687d5366d10f60315bf4e580a020b4
> SHA1 (tor-0.1.0.16.tar.gz) = 567fd02d5d22c571c452bc354f1c902cfb37d3f4
> SIZE (tor-0.1.0.16.tar.gz) = 633340
