Anonymous Living

From OR-Talk,

0.1.2.18 is getting close to ready; please test it
From: Roger Dingledine
To: or-talk
Date: 2007-10-16 06:32

Hi folks,

We’re getting close to having 0.1.2.18 ready. I’ve put snapshots at

 https://tor.eff.org/dist/tor-0.1.2.17-de…
 https://tor.eff.org/dist/tor-0.1.2.17-de…

 https://tor.eff.org/dist/vidalia-bundles…
 https://tor.eff.org/dist/vidalia-bundles…

 https://tor.eff.org/dist/vidalia-bundles…
 https://tor.eff.org/dist/vidalia-bundles…

 https://tor.eff.org/dist/win32/tor-0.1.2…
 https://tor.eff.org/dist/win32/tor-0.1.2…

 https://tor.eff.org/dist/osx/Tor-0.1.2.1…
 https://tor.eff.org/dist/osx/Tor-0.1.2.1…

Please grab it, try it out, and let us know whether we broke anything.

Thanks,
–Roger

Partial list of changes in version 0.1.2.18 - 2007-10-??

• Major bugfixes (crashes):
  •     - If a connection is shut down abruptly because of something that
  •       happened inside connection_flushed_some(), do not call
  •       connection_finished_flushing(). Should fix bug 451:
  •       “connection_stop_writing: Assertion conn->write_event failed”
  •       Bugfix on 0.1.2.7-alpha.
  •     - Fix possible segfaults in functions called from
  •       rend_process_relay_cell().
•   o Major bugfixes (other):
  •     - Stop publishing a new server descriptor just because we get a
  •       HUP signal. This led (in a roundabout way) to some servers getting
  •       dropped from the networkstatus lists for a few hours each day.
  •     - Hidden services were choosing introduction points uniquely by
  •       hexdigest, but when constructing the hidden service descriptor
  •       they merely wrote the (potentially ambiguous) nickname.
  •     - Clients now use the v2 intro format for hidden service
  •       connections: they specify their chosen rendezvous point by identity
  •       digest rather than by (potentially ambiguous) nickname. These
  •       changes could speed up hidden service connections dramatically.
  •     - When looking for a circuit to cannibalize, consider family as well
  •       as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
  •       circuit cannibalization).
• Minor bugfixes:
  • Don’t try to access (or alter) the state file when running –list-fingerprint or –verify-config or –hash-password. (Resolves bug 499.)
  • When generating information telling us how to extend to a given router, do not try to include the nickname if it is absent. (Resolves bug 467.)
  • Fix a user-triggerable segfault in expand_filename(). (There isn’t a way to trigger this remotely.)
  • When sending a status event to the controller telling it that an OR address is readable, set the port correctly. (Previously we were reporting the dir port.)
  • Fix a minor memory leak whenever a controller sends the PROTOCOLINFO command. Bugfix on 0.1.2.17.
  • When loading bandwidth history, do not believe any information in the future. Fixes bug 434.
  • When loading entry guard information, do not believe any information in the future.
  • When we have our clock set far in the future and generate an onion key, then re-set our clock to be correct, we should not stop the onion key from getting rotated.
  • On some platforms, accept() can return a broken address. Detect this more quietly, and deal accordingly. Fixes bug 483.
  • It’s not actually an error to find a non-pending entry in the DNS cache when canceling a pending resolve. Don’t log unless stuff is fishy. Resolves bug 463.