2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.0.31 - 2008-09-03
7 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8 a big bug we're seeing where in rare cases traffic from one Tor stream
9 gets mixed into another stream, and fixes a variety of smaller issues.
12 - Make sure that two circuits can never exist on the same connection
13 with the same circuit ID, even if one is marked for close. This
14 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
15 - Relays now reject risky extend cells: if the extend cell includes
16 a digest of all zeroes, or asks to extend back to the relay that
17 sent the extend cell, tear down the circuit. Ideas suggested
19 - If not enough of our entry guards are available so we add a new
20 one, we might use the new one even if it overlapped with the
21 current circuit's exit relay (or its family). Anonymity bugfix
25 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
26 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
27 - Correctly detect the presence of the linux/netfilter_ipv4.h header
28 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
29 - Pick size of default geoip filename string correctly on windows.
30 Fixes bug 806. Bugfix on 0.2.0.30.
31 - Make the autoconf script accept the obsolete --with-ssl-dir
32 option as an alias for the actually-working --with-openssl-dir
33 option. Fix the help documentation to recommend --with-openssl-dir.
34 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
35 - Disallow session resumption attempts during the renegotiation
36 stage of the v2 handshake protocol. Clients should never be trying
37 session resumption at this point, but apparently some did, in
38 ways that caused the handshake to fail. Bug found by Geoff Goodell.
39 Bugfix on 0.2.0.20-rc.
40 - When using the TransPort option on OpenBSD, and using the User
41 option to change UID and drop privileges, make sure to open
42 /dev/pf before dropping privileges. Fixes bug 782. Patch from
43 Christopher Davis. Bugfix on 0.1.2.1-alpha.
44 - Try to attach connections immediately upon receiving a RENDEZVOUS2
45 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
46 on the client side when connecting to a hidden service. Bugfix
47 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
48 - When closing an application-side connection because its circuit is
49 getting torn down, generate the stream event correctly. Bugfix on
50 0.1.2.x. Anonymous patch.
53 Changes in version 0.2.0.30 - 2008-07-15
54 This new stable release switches to a more efficient directory
55 distribution design, adds features to make connections to the Tor
56 network harder to block, allows Tor to act as a DNS proxy, adds separate
57 rate limiting for relayed traffic to make it easier for clients to
58 become relays, fixes a variety of potential anonymity problems, and
59 includes the usual huge pile of other features and bug fixes.
61 o New v3 directory design:
62 - Tor now uses a new way to learn about and distribute information
63 about the network: the directory authorities vote on a common
64 network status document rather than each publishing their own
65 opinion. Now clients and caches download only one networkstatus
66 document to bootstrap, rather than downloading one for each
67 authority. Clients only download router descriptors listed in
68 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
70 - Set up moria1, tor26, and dizum as v3 directory authorities
71 in addition to being v2 authorities. Also add three new ones:
72 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
73 dannenberg (run by CCC).
74 - Switch to multi-level keys for directory authorities: now their
75 long-term identity key can be kept offline, and they periodically
76 generate a new signing key. Clients fetch the "key certificates"
77 to keep up to date on the right keys. Add a standalone tool
78 "tor-gencert" to generate key certificates. Implements proposal 103.
79 - Add a new V3AuthUseLegacyKey config option to make it easier for
80 v3 authorities to change their identity keys if another bug like
81 Debian's OpenSSL RNG flaw appears.
82 - Authorities and caches fetch the v2 networkstatus documents
83 less often, now that v3 is recommended.
85 o Make Tor connections stand out less on the wire:
86 - Use an improved TLS handshake designed by Steven Murdoch in proposal
87 124, as revised in proposal 130. The new handshake is meant to
88 be harder for censors to fingerprint, and it adds the ability
89 to detect certain kinds of man-in-the-middle traffic analysis
90 attacks. The new handshake format includes version negotiation for
91 OR connections as described in proposal 105, which will allow us
92 to improve Tor's link protocol more safely in the future.
93 - Enable encrypted directory connections by default for non-relays,
94 so censor tools that block Tor directory connections based on their
95 plaintext patterns will no longer work. This means Tor works in
96 certain censored countries by default again.
97 - Stop including recognizeable strings in the commonname part of
98 Tor's x509 certificates.
100 o Implement bridge relays:
101 - Bridge relays (or "bridges" for short) are Tor relays that aren't
102 listed in the main Tor directory. Since there is no complete public
103 list of them, even an ISP that is filtering connections to all the
104 known Tor relays probably won't be able to block all the bridges.
105 See doc/design-paper/blocking.pdf and proposal 125 for details.
106 - New config option BridgeRelay that specifies you want to be a
107 bridge relay rather than a normal relay. When BridgeRelay is set
108 to 1, then a) you cache dir info even if your DirPort ins't on,
109 and b) the default for PublishServerDescriptor is now "bridge"
111 - New config option "UseBridges 1" for clients that want to use bridge
112 relays instead of ordinary entry guards. Clients then specify
113 bridge relays by adding "Bridge" lines to their config file. Users
114 can learn about a bridge relay either manually through word of
115 mouth, or by one of our rate-limited mechanisms for giving out
116 bridge addresses without letting an attacker easily enumerate them
117 all. See https://www.torproject.org/bridges for details.
118 - Bridge relays behave like clients with respect to time intervals
119 for downloading new v3 consensus documents -- otherwise they
120 stand out. Bridge users now wait until the end of the interval,
121 so their bridge relay will be sure to have a new consensus document.
123 o Implement bridge directory authorities:
124 - Bridge authorities are like normal directory authorities, except
125 they don't serve a list of known bridges. Therefore users that know
126 a bridge's fingerprint can fetch a relay descriptor for that bridge,
127 including fetching updates e.g. if the bridge changes IP address,
128 yet an attacker can't just fetch a list of all the bridges.
129 - Set up Tonga as the default bridge directory authority.
130 - Bridge authorities refuse to serve bridge descriptors or other
131 bridge information over unencrypted connections (that is, when
132 responding to direct DirPort requests rather than begin_dir cells.)
133 - Bridge directory authorities do reachability testing on the
134 bridges they know. They provide router status summaries to the
135 controller via "getinfo ns/purpose/bridge", and also dump summaries
136 to a file periodically, so we can keep internal stats about which
137 bridges are functioning.
138 - If bridge users set the UpdateBridgesFromAuthority config option,
139 but the digest they ask for is a 404 on the bridge authority,
140 they fall back to contacting the bridge directly.
141 - Bridges always use begin_dir to publish their server descriptor to
142 the bridge authority using an anonymous encrypted tunnel.
143 - Early work on a "bridge community" design: if bridge authorities set
144 the BridgePassword config option, they will serve a snapshot of
145 known bridge routerstatuses from their DirPort to anybody who
146 knows that password. Unset by default.
147 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
148 report sanitized aggregated summaries in their extra-info documents
149 privately to the bridge authority, listing which countries are
150 able to reach them. We hope this mechanism will let us learn when
151 certain countries start trying to block bridges.
152 - Bridge authorities write bridge descriptors to disk, so they can
153 reload them after a reboot. They can also export the descriptors
154 to other programs, so we can distribute them to blocked users via
155 the BridgeDB interface, e.g. via https://bridges.torproject.org/
156 and bridges@torproject.org.
158 o Tor can be a DNS proxy:
159 - The new client-side DNS proxy feature replaces the need for
160 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
161 for DNS requests on port 9999, use the Tor network to resolve them
162 anonymously, and send the reply back like a regular DNS server.
163 The code still only implements a subset of DNS.
164 - Add a new AutomapHostsOnResolve option: when it is enabled, any
165 resolve request for hosts matching a given pattern causes Tor to
166 generate an internal virtual address mapping for that host. This
167 allows DNSPort to work sensibly with hidden service users. By
168 default, .exit and .onion addresses are remapped; the list of
169 patterns can be reconfigured with AutomapHostsSuffixes.
170 - Add an "-F" option to tor-resolve to force a resolve for a .onion
171 address. Thanks to the AutomapHostsOnResolve option, this is no
172 longer a completely silly thing to do.
174 o Major features (relay usability):
175 - New config options RelayBandwidthRate and RelayBandwidthBurst:
176 a separate set of token buckets for relayed traffic. Right now
177 relayed traffic is defined as answers to directory requests, and
178 OR connections that don't have any local circuits on them. See
179 proposal 111 for details.
180 - Create listener connections before we setuid to the configured
181 User and Group. Now non-Windows users can choose port values
182 under 1024, start Tor as root, and have Tor bind those ports
183 before it changes to another UID. (Windows users could already
185 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
186 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
187 on "vserver" accounts. Patch from coderman.
189 o Major features (directory authorities):
190 - Directory authorities track weighted fractional uptime and weighted
191 mean-time-between failures for relays. WFU is suitable for deciding
192 whether a node is "usually up", while MTBF is suitable for deciding
193 whether a node is "likely to stay up." We need both, because
194 "usually up" is a good requirement for guards, while "likely to
195 stay up" is a good requirement for long-lived connections.
196 - Directory authorities use a new formula for selecting which relays
197 to advertise as Guards: they must be in the top 7/8 in terms of
198 how long we have known about them, and above the median of those
199 nodes in terms of weighted fractional uptime.
200 - Directory authorities use a new formula for selecting which relays
201 to advertise as Stable: when we have 4 or more days of data, use
202 median measured MTBF rather than median declared uptime. Implements
204 - Directory authorities accept and serve "extra info" documents for
205 routers. Routers now publish their bandwidth-history lines in the
206 extra-info docs rather than the main descriptor. This step saves
207 60% (!) on compressed router descriptor downloads. Servers upload
208 extra-info docs to any authority that accepts them; directory
209 authorities now allow multiple router descriptors and/or extra
210 info documents to be uploaded in a single go. Authorities, and
211 caches that have been configured to download extra-info documents,
212 download them as needed. Implements proposal 104.
213 - Authorities now list relays who have the same nickname as
214 a different named relay, but list them with a new flag:
215 "Unnamed". Now we can make use of relays that happen to pick the
216 same nickname as a server that registered two years ago and then
217 disappeared. Implements proposal 122.
218 - Store routers in a file called cached-descriptors instead of in
219 cached-routers. Initialize cached-descriptors from cached-routers
220 if the old format is around. The new format allows us to store
221 annotations along with descriptors, to record the time we received
222 each descriptor, its source, and its purpose: currently one of
223 general, controller, or bridge.
225 o Major features (other):
226 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
227 Tor can warn and/or refuse connections to ports commonly used with
228 vulnerable-plaintext protocols. Currently we warn on ports 23,
229 109, 110, and 143, but we don't reject any. Based on proposal 129
230 by Kevin Bauer and Damon McCoy.
231 - Integrate Karsten Loesing's Google Summer of Code project to publish
232 hidden service descriptors on a set of redundant relays that are a
233 function of the hidden service address. Now we don't have to rely
234 on three central hidden service authorities for publishing and
235 fetching every hidden service descriptor. Implements proposal 114.
236 - Allow tunnelled directory connections to ask for an encrypted
237 "begin_dir" connection or an anonymized "uses a full Tor circuit"
238 connection independently. Now we can make anonymized begin_dir
239 connections for (e.g.) more secure hidden service posting and
242 o Major bugfixes (crashes and assert failures):
243 - Stop imposing an arbitrary maximum on the number of file descriptors
244 used for busy servers. Bug reported by Olaf Selke; patch from
246 - Avoid possible failures when generating a directory with routers
247 with over-long versions strings, or too many flags set.
248 - Fix a rare assert error when we're closing one of our threads:
249 use a mutex to protect the list of logs, so we never write to the
250 list as it's being freed. Fixes the very rare bug 575, which is
251 kind of the revenge of bug 222.
252 - Avoid segfault in the case where a badly behaved v2 versioning
253 directory sends a signed networkstatus with missing client-versions.
254 - When we hit an EOF on a log (probably because we're shutting down),
255 don't try to remove the log from the list: just mark it as
256 unusable. (Bulletproofs against bug 222.)
258 o Major bugfixes (code security fixes):
259 - Detect size overflow in zlib code. Reported by Justin Ferguson and
261 - Rewrite directory tokenization code to never run off the end of
262 a string. Fixes bug 455. Patch from croup.
263 - Be more paranoid about overwriting sensitive memory on free(),
264 as a defensive programming tactic to ensure forward secrecy.
266 o Major bugfixes (anonymity fixes):
267 - Reject requests for reverse-dns lookup of names that are in
268 a private address space. Patch from lodger.
269 - Never report that we've used more bandwidth than we're willing to
270 relay: it leaks how much non-relay traffic we're using. Resolves
272 - As a client, do not believe any server that tells us that an
273 address maps to an internal address space.
274 - Warn about unsafe ControlPort configurations.
275 - Directory authorities now call routers Fast if their bandwidth is
276 at least 100KB/s, and consider their bandwidth adequate to be a
277 Guard if it is at least 250KB/s, no matter the medians. This fix
278 complements proposal 107.
279 - Directory authorities now never mark more than 2 servers per IP as
280 Valid and Running (or 5 on addresses shared by authorities).
281 Implements proposal 109, by Kevin Bauer and Damon McCoy.
282 - If we're a relay, avoid picking ourselves as an introduction point,
283 a rendezvous point, or as the final hop for internal circuits. Bug
284 reported by taranis and lodger.
285 - Exit relays that are used as a client can now reach themselves
286 using the .exit notation, rather than just launching an infinite
287 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
288 - Fix a bug where, when we were choosing the 'end stream reason' to
289 put in our relay end cell that we send to the exit relay, Tor
290 clients on Windows were sometimes sending the wrong 'reason'. The
291 anonymity problem is that exit relays may be able to guess whether
292 the client is running Windows, thus helping partition the anonymity
293 set. Down the road we should stop sending reasons to exit relays,
294 or otherwise prevent future versions of this bug.
295 - Only update guard status (usable / not usable) once we have
296 enough directory information. This was causing us to discard all our
297 guards on startup if we hadn't been running for a few weeks. Fixes
299 - When our directory information has been expired for a while, stop
300 being willing to build circuits using it. Fixes bug 401.
302 o Major bugfixes (peace of mind for relay operators)
303 - Non-exit relays no longer answer "resolve" relay cells, so they
304 can't be induced to do arbitrary DNS requests. (Tor clients already
305 avoid using non-exit relays for resolve cells, but now servers
306 enforce this too.) Fixes bug 619. Patch from lodger.
307 - When we setconf ClientOnly to 1, close any current OR and Dir
308 listeners. Reported by mwenge.
310 o Major bugfixes (other):
311 - If we only ever used Tor for hidden service lookups or posts, we
312 would stop building circuits and start refusing connections after
313 24 hours, since we falsely believed that Tor was dormant. Reported
315 - Add a new __HashedControlSessionPassword option for controllers
316 to use for one-off session password hashes that shouldn't get
317 saved to disk by SAVECONF --- Vidalia users were accumulating a
318 pile of HashedControlPassword lines in their torrc files, one for
319 each time they had restarted Tor and then clicked Save. Make Tor
320 automatically convert "HashedControlPassword" to this new option but
321 only when it's given on the command line. Partial fix for bug 586.
322 - Patch from "Andrew S. Lists" to catch when we contact a directory
323 mirror at IP address X and he says we look like we're coming from
324 IP address X. Otherwise this would screw up our address detection.
325 - Reject uploaded descriptors and extrainfo documents if they're
326 huge. Otherwise we'll cache them all over the network and it'll
327 clog everything up. Suggested by Aljosha Judmayer.
328 - When a hidden service was trying to establish an introduction point,
329 and Tor *did* manage to reuse one of the preemptively built
330 circuits, it didn't correctly remember which one it used,
331 so it asked for another one soon after, until there were no
332 more preemptive circuits, at which point it launched one from
333 scratch. Bugfix on 0.0.9.x.
335 o Rate limiting and load balancing improvements:
336 - When we add data to a write buffer in response to the data on that
337 write buffer getting low because of a flush, do not consider the
338 newly added data as a candidate for immediate flushing, but rather
339 make it wait until the next round of writing. Otherwise, we flush
340 and refill recursively, and a single greedy TLS connection can
341 eat all of our bandwidth.
342 - When counting the number of bytes written on a TLS connection,
343 look at the BIO actually used for writing to the network, not
344 at the BIO used (sometimes) to buffer data for the network.
345 Looking at different BIOs could result in write counts on the
346 order of ULONG_MAX. Fixes bug 614.
347 - If we change our MaxAdvertisedBandwidth and then reload torrc,
348 Tor won't realize it should publish a new relay descriptor. Fixes
349 bug 688, reported by mfr.
350 - Avoid using too little bandwidth when our clock skips a few seconds.
351 - Choose which bridge to use proportional to its advertised bandwidth,
352 rather than uniformly at random. This should speed up Tor for
353 bridge users. Also do this for people who set StrictEntryNodes.
355 o Bootstrapping faster and building circuits more intelligently:
356 - Fix bug 660 that was preventing us from knowing that we should
357 preemptively build circuits to handle expected directory requests.
358 - When we're checking if we have enough dir info for each relay
359 to begin establishing circuits, make sure that we actually have
360 the descriptor listed in the consensus, not just any descriptor.
361 - Correctly notify one-hop connections when a circuit build has
362 failed. Possible fix for bug 669. Found by lodger.
363 - Clients now hold circuitless TLS connections open for 1.5 times
364 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
365 rebuild a new circuit over them within that timeframe. Previously,
366 they held them open only for KeepalivePeriod (5 minutes).
368 o Performance improvements (memory):
369 - Add OpenBSD malloc code from "phk" as an optional malloc
370 replacement on Linux: some glibc libraries do very poorly with
371 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
372 ./configure to get the replacement malloc code.
373 - Switch our old ring buffer implementation for one more like that
374 used by free Unix kernels. The wasted space in a buffer with 1mb
375 of data will now be more like 8k than 1mb. The new implementation
376 also avoids realloc();realloc(); patterns that can contribute to
377 memory fragmentation.
378 - Change the way that Tor buffers data that it is waiting to write.
379 Instead of queueing data cells in an enormous ring buffer for each
380 client->OR or OR->OR connection, we now queue cells on a separate
381 queue for each circuit. This lets us use less slack memory, and
382 will eventually let us be smarter about prioritizing different kinds
384 - Reference-count and share copies of address policy entries; only 5%
385 of them were actually distinct.
386 - Tune parameters for cell pool allocation to minimize amount of
388 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
389 for every single inactive connection_t. Free items from the
390 4k/16k-buffer free lists when they haven't been used for a while.
391 - Make memory debugging information describe more about history
392 of cell allocation, so we can help reduce our memory use.
393 - Be even more aggressive about releasing RAM from small
394 empty buffers. Thanks to our free-list code, this shouldn't be too
395 performance-intensive.
396 - Log malloc statistics from mallinfo() on platforms where it exists.
397 - Use memory pools to allocate cells with better speed and memory
398 efficiency, especially on platforms where malloc() is inefficient.
399 - Add a --with-tcmalloc option to the configure script to link
400 against tcmalloc (if present). Does not yet search for non-system
403 o Performance improvements (socket management):
404 - Count the number of open sockets separately from the number of
405 active connection_t objects. This will let us avoid underusing
406 our allocated connection limit.
407 - We no longer use socket pairs to link an edge connection to an
408 anonymous directory connection or a DirPort test connection.
409 Instead, we track the link internally and transfer the data
410 in-process. This saves two sockets per "linked" connection (at the
411 client and at the server), and avoids the nasty Windows socketpair()
413 - We were leaking a file descriptor if Tor started with a zero-length
414 cached-descriptors file. Patch by "freddy77".
416 o Performance improvements (CPU use):
417 - Never walk through the list of logs if we know that no log target
418 is interested in a given message.
419 - Call routerlist_remove_old_routers() much less often. This should
420 speed startup, especially on directory caches.
421 - Base64 decoding was actually showing up on our profile when parsing
422 the initial descriptor file; switch to an in-process all-at-once
423 implementation that's about 3.5x times faster than calling out to
425 - Use a slightly simpler string hashing algorithm (copying Python's
426 instead of Java's) and optimize our digest hashing algorithm to take
427 advantage of 64-bit platforms and to remove some possibly-costly
429 - When implementing AES counter mode, update only the portions of the
430 counter buffer that need to change, and don't keep separate
431 network-order and host-order counters on big-endian hosts (where
433 - Add an in-place version of aes_crypt() so that we can avoid doing a
434 needless memcpy() call on each cell payload.
435 - Use Critical Sections rather than Mutexes for synchronizing threads
436 on win32; Mutexes are heavier-weight, and designed for synchronizing
439 o Performance improvements (bandwidth use):
440 - Don't try to launch new descriptor downloads quite so often when we
441 already have enough directory information to build circuits.
442 - Version 1 directories are no longer generated in full. Instead,
443 authorities generate and serve "stub" v1 directories that list
444 no servers. This will stop Tor versions 0.1.0.x and earlier from
445 working, but (for security reasons) nobody should be running those
447 - Avoid going directly to the directory authorities even if you're a
448 relay, if you haven't found yourself reachable yet or if you've
449 decided not to advertise your dirport yet. Addresses bug 556.
450 - If we've gone 12 hours since our last bandwidth check, and we
451 estimate we have less than 50KB bandwidth capacity but we could
452 handle more, do another bandwidth test.
453 - Support "If-Modified-Since" when answering HTTP requests for
454 directories, running-routers documents, and v2 and v3 networkstatus
455 documents. (There's no need to support it for router descriptors,
456 since those are downloaded by descriptor digest.)
457 - Stop fetching directory info so aggressively if your DirPort is
458 on but your ORPort is off; stop fetching v2 dir info entirely.
459 You can override these choices with the new FetchDirInfoEarly
462 o Changed config option behavior (features):
463 - Configuration files now accept C-style strings as values. This
464 helps encode characters not allowed in the current configuration
465 file format, such as newline or #. Addresses bug 557.
466 - Add hidden services and DNSPorts to the list of things that make
467 Tor accept that it has running ports. Change starting Tor with no
468 ports from a fatal error to a warning; we might change it back if
469 this turns out to confuse anybody. Fixes bug 579.
470 - Make PublishServerDescriptor default to 1, so the default doesn't
471 have to change as we invent new directory protocol versions.
472 - Allow people to say PreferTunnelledDirConns rather than
473 PreferTunneledDirConns, for those alternate-spellers out there.
474 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
475 accommodate the growing number of servers that use the default
477 - Make it possible to enable HashedControlPassword and
478 CookieAuthentication at the same time.
479 - When a TrackHostExits-chosen exit fails too many times in a row,
480 stop using it. Fixes bug 437.
482 o Changed config option behavior (bugfixes):
483 - Do not read the configuration file when we've only been told to
484 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
485 based on patch from Sebastian Hahn.
486 - Actually validate the options passed to AuthDirReject,
487 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
488 - Make "ClientOnly 1" config option disable directory ports too.
489 - Don't stop fetching descriptors when FetchUselessDescriptors is
490 set, even if we stop asking for circuits. Bug reported by tup
492 - Servers used to decline to publish their DirPort if their
493 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
494 they look only at BandwidthRate and RelayBandwidthRate.
495 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
496 minus 1 byte: the actual maximum declared bandwidth.
497 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
498 - Make the NodeFamilies config option work. (Reported by
499 lodger -- it has never actually worked, even though we added it
501 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
502 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
504 o New config options:
505 - New configuration options to override default maximum number of
506 servers allowed on a single IP address. This is important for
507 running a test network on a single host. XXX
508 - Three new config options (AlternateDirAuthority,
509 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
510 user selectively replace the default directory authorities by type,
511 rather than the all-or-nothing replacement that DirServer offers.
512 - New config options AuthDirBadDir and AuthDirListBadDirs for
513 authorities to mark certain relays as "bad directories" in the
514 networkstatus documents. Also supports the "!baddir" directive in
515 the approved-routers file.
516 - New config option V2AuthoritativeDirectory that all v2 directory
517 authorities must set. This lets v3 authorities choose not to serve
518 v2 directory information.
520 o Minor features (other):
521 - When we're not serving v2 directory information, there is no reason
522 to actually keep any around. Remove the obsolete files and directory
523 on startup if they are very old and we aren't going to serve them.
524 - When we negotiate a v2 link-layer connection (not yet implemented),
525 accept RELAY_EARLY cells and turn them into RELAY cells if we've
526 negotiated a v1 connection for their next step. Initial steps for
528 - When we have no consensus, check FallbackNetworkstatusFile (defaults
529 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
530 we can start out knowing some directory caches. We don't ship with
531 a fallback consensus by default though, because it wasn't making
532 bootstrapping take too long while we tried many down relays.
533 - Authorities send back an X-Descriptor-Not-New header in response to
534 an accepted-but-discarded descriptor upload. Partially implements
536 - If we find a cached-routers file that's been sitting around for more
537 than 28 days unmodified, then most likely it's a leftover from
538 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
540 - When we (as a cache) download a descriptor because it was listed
541 in a consensus, remember when the consensus was supposed to expire,
542 and don't expire the descriptor until then.
543 - Optionally (if built with -DEXPORTMALLINFO) export the output
544 of mallinfo via http, as tor/mallinfo.txt. Only accessible
546 - Tag every guard node in our state file with the version that
547 we believe added it, or with our own version if we add it. This way,
548 if a user temporarily runs an old version of Tor and then switches
549 back to a new one, she doesn't automatically lose her guards.
550 - When somebody requests a list of statuses or servers, and we have
551 none of those, return a 404 rather than an empty 200.
552 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
554 - Add an HSAuthorityRecordStats option that hidden service authorities
555 can use to track statistics of overall hidden service usage without
556 logging information that would be as useful to an attacker.
557 - Allow multiple HiddenServicePort directives with the same virtual
558 port; when they occur, the user is sent round-robin to one
559 of the target ports chosen at random. Partially fixes bug 393 by
560 adding limited ad-hoc round-robining.
561 - Revamp file-writing logic so we don't need to have the entire
562 contents of a file in memory at once before we write to disk. Tor,
565 o Minor bugfixes (other):
566 - Alter the code that tries to recover from unhandled write
567 errors, to not try to flush onto a socket that's given us
569 - Directory mirrors no longer include a guess at the client's IP
570 address if the connection appears to be coming from the same /24
571 network; it was producing too many wrong guesses.
572 - If we're trying to flush the last bytes on a connection (for
573 example, when answering a directory request), reset the
574 time-to-give-up timeout every time we manage to write something
576 - Reject router descriptors with out-of-range bandwidthcapacity or
577 bandwidthburst values.
578 - If we can't expand our list of entry guards (e.g. because we're
579 using bridges or we have StrictEntryNodes set), don't mark relays
580 down when they fail a directory request. Otherwise we're too quick
581 to mark all our entry points down.
582 - Authorities no longer send back "400 you're unreachable please fix
583 it" errors to Tor servers that aren't online all the time. We're
584 supposed to tolerate these servers now.
585 - Let directory authorities startup even when they can't generate
586 a descriptor immediately, e.g. because they don't know their
588 - Correctly enforce that elements of directory objects do not appear
589 more often than they are allowed to appear.
590 - Stop allowing hibernating servers to be "stable" or "fast".
591 - On Windows, we were preventing other processes from reading
592 cached-routers while Tor was running. (Reported by janbar)
593 - Check return values from pthread_mutex functions.
594 - When opening /dev/null in finish_daemonize(), do not pass the
595 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
596 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
598 o Controller features:
599 - The GETCONF command now escapes and quotes configuration values
600 that don't otherwise fit into the torrc file.
601 - The SETCONF command now handles quoted values correctly.
602 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
603 ask about source, timestamp of arrival, purpose, etc. We need
604 something like this to help Vidalia not do GeoIP lookups on bridge
606 - Allow multiple HashedControlPassword config lines, to support
607 multiple controller passwords.
608 - Accept LF instead of CRLF on controller, since some software has a
609 hard time generating real Internet newlines.
610 - Add GETINFO values for the server status events
611 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
613 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
614 GETINFO for Torstat to use until it can switch to using extrainfos.
615 - New config option CookieAuthFile to choose a new location for the
616 cookie authentication file, and config option
617 CookieAuthFileGroupReadable to make it group-readable.
618 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
619 match requests to applications. Patch from Robert Hogan.
620 - Add a RESOLVE command to launch hostname lookups. Original patch
622 - Add GETINFO status/enough-dir-info to let controllers tell whether
623 Tor has downloaded sufficient directory information. Patch from Tup.
624 - You can now use the ControlSocket option to tell Tor to listen for
625 controller connections on Unix domain sockets on systems that
626 support them. Patch from Peter Palfrader.
627 - New "GETINFO address-mappings/*" command to get address mappings
628 with expiry information. "addr-mappings/*" is now deprecated.
630 - Add a new config option __DisablePredictedCircuits designed for
631 use by the controller, when we don't want Tor to build any circuits
633 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
634 so we can exit from the middle of the circuit.
635 - Implement "getinfo status/circuit-established".
636 - Implement "getinfo status/version/..." so a controller can tell
637 whether the current version is recommended, and whether any versions
638 are good, and how many authorities agree. Patch from "shibz".
639 - Controllers should now specify cache=no or cache=yes when using
640 the +POSTDESCRIPTOR command.
641 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
642 Robert Hogan. Fixes the first part of bug 681.
643 - When reporting clock skew, and we know that the clock is _at least
644 as skewed_ as some value, but we don't know the actual value,
645 report the value as a "minimum skew."
647 o Controller bugfixes:
648 - Generate "STATUS_SERVER" events rather than misspelled
649 "STATUS_SEVER" events. Caught by mwenge.
650 - Reject controller commands over 1MB in length, so rogue
651 processes can't run us out of memory.
652 - Change the behavior of "getinfo status/good-server-descriptor"
653 so it doesn't return failure when any authority disappears.
654 - Send NAMESERVER_STATUS messages for a single failed nameserver
656 - When the DANGEROUS_VERSION controller status event told us we're
657 running an obsolete version, it used the string "OLD" to describe
658 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
659 "OBSOLETE" in both cases.
660 - Respond to INT and TERM SIGNAL commands before we execute the
661 signal, in case the signal shuts us down. We had a patch in
662 0.1.2.1-alpha that tried to do this by queueing the response on
663 the connection's buffer before shutting down, but that really
664 isn't the same thing at all. Bug located by Matt Edman.
665 - Provide DNS expiry times in GMT, not in local time. For backward
666 compatibility, ADDRMAP events only provide GMT expiry in an extended
667 field. "GETINFO address-mappings" always does the right thing.
668 - Use CRLF line endings properly in NS events.
669 - Make 'getinfo fingerprint' return a 551 error if we're not a
670 server, so we match what the control spec claims we do. Reported
672 - Fix a typo in an error message when extendcircuit fails that
673 caused us to not follow the \r\n-based delimiter protocol. Reported
675 - When tunneling an encrypted directory connection, and its first
676 circuit fails, do not leave it unattached and ask the controller
677 to deal. Fixes the second part of bug 681.
678 - Treat some 403 responses from directory servers as INFO rather than
679 WARN-severity events.
681 o Portability / building / compiling:
682 - When building with --enable-gcc-warnings, check for whether Apple's
683 warning "-Wshorten-64-to-32" is available.
684 - Support compilation to target iPhone; patch from cjacker huang.
685 To build for iPhone, pass the --enable-iphone option to configure.
686 - Detect non-ASCII platforms (if any still exist) and refuse to
687 build there: some of our code assumes that 'A' is 65 and so on.
688 - Clear up some MIPSPro compiler warnings.
689 - Make autoconf search for libevent, openssl, and zlib consistently.
690 - Update deprecated macros in configure.in.
691 - When warning about missing headers, tell the user to let us
692 know if the compile succeeds anyway, so we can downgrade the
694 - Include the current subversion revision as part of the version
695 string: either fetch it directly if we're in an SVN checkout, do
696 some magic to guess it if we're in an SVK checkout, or use
697 the last-detected version if we're building from a .tar.gz.
698 Use this version consistently in log messages.
699 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
700 - Read resolv.conf files correctly on platforms where read() returns
701 partial results on small file reads.
702 - Build without verbose warnings even on gcc 4.2 and 4.3.
703 - On Windows, correctly detect errors when listing the contents of
704 a directory. Fix from lodger.
705 - Run 'make test' as part of 'make dist', so we stop releasing so
706 many development snapshots that fail their unit tests.
707 - Add support to detect Libevent versions in the 1.4.x series
709 - Add command-line arguments to unit-test executable so that we can
710 invoke any chosen test from the command line rather than having
711 to run the whole test suite at once; and so that we can turn on
712 logging for the unit tests.
713 - Do not automatically run configure from autogen.sh. This
714 non-standard behavior tended to annoy people who have built other
716 - Fix a macro/CPP interaction that was confusing some compilers:
717 some GCCs don't like #if/#endif pairs inside macro arguments.
719 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
720 Fixes bug 704; fix from Steven Murdoch.
721 - Correctly detect transparent proxy support on Linux hosts that
722 require in.h to be included before netfilter_ipv4.h. Patch
725 o Logging improvements:
726 - When we haven't had any application requests lately, don't bother
727 logging that we have expired a bunch of descriptors.
728 - When attempting to open a logfile fails, tell us why.
729 - Only log guard node status when guard node status has changed.
730 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
731 make "INFO" 75% less verbose.
732 - When SafeLogging is disabled, log addresses along with all TLS
734 - Report TLS "zero return" case as a "clean close" and "IO error"
735 as a "close". Stop calling closes "unexpected closes": existing
736 Tors don't use SSL_close(), so having a connection close without
737 the TLS shutdown handshake is hardly unexpected.
738 - When we receive a consensus from the future, warn about skew.
739 - Make "not enough dir info yet" warnings describe *why* Tor feels
740 it doesn't have enough directory info yet.
741 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
742 consumers. (We already do this on HUP.)
743 - Give more descriptive well-formedness errors for out-of-range
744 hidden service descriptor/protocol versions.
745 - Stop recommending that every server operator send mail to tor-ops.
746 Resolves bug 597. Bugfix on 0.1.2.x.
747 - Improve skew reporting: try to give the user a better log message
748 about how skewed they are, and how much this matters.
749 - New --quiet command-line option to suppress the default console log.
750 Good in combination with --hash-password.
751 - Don't complain that "your server has not managed to confirm that its
752 ports are reachable" if we haven't been able to build any circuits
754 - Detect the reason for failing to mmap a descriptor file we just
755 wrote, and give a more useful log message. Fixes bug 533.
756 - Always prepend "Bug: " to any log message about a bug.
757 - When dumping memory usage, list bytes used in buffer memory
759 - When running with dmalloc, dump more stats on hup and on exit.
760 - Put a platform string (e.g. "Linux i686") in the startup log
761 message, so when people paste just their logs, we know if it's
762 OpenBSD or Windows or what.
763 - When logging memory usage, break down memory used in buffers by
765 - When we are reporting the DirServer line we just parsed, we were
766 logging the second stanza of the key fingerprint, not the first.
767 - Even though Windows is equally happy with / and \ as path separators,
768 try to use \ consistently on Windows and / consistently on Unix: it
769 makes the log messages nicer.
770 - On OSX, stop warning the user that kqueue support in libevent is
771 "experimental", since it seems to have worked fine for ages.
773 o Contributed scripts and tools:
774 - Update linux-tor-prio.sh script to allow QoS based on the uid of
775 the Tor process. Patch from Marco Bonetti with tweaks from Mike
777 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
778 Unix users an easy way to script their Tor process (e.g. by
779 adjusting bandwidth based on the time of the day).
780 - In the exitlist script, only consider the most recently published
781 server descriptor for each server. Also, when the user requests
782 a list of servers that _reject_ connections to a given address,
783 explicitly exclude the IPs that also have servers that accept
784 connections to that address. Resolves bug 405.
785 - Include a new contrib/tor-exit-notice.html file that exit relay
786 operators can put on their website to help reduce abuse queries.
788 o Newly deprecated features:
789 - The status/version/num-versioning and status/version/num-concurring
790 GETINFO controller options are no longer useful in the v3 directory
791 protocol: treat them as deprecated, and warn when they're used.
792 - The RedirectExits config option is now deprecated.
795 - Drop the old code to choke directory connections when the
796 corresponding OR connections got full: thanks to the cell queue
797 feature, OR conns don't get full any more.
798 - Remove the old "dns worker" server DNS code: it hasn't been default
799 since 0.1.2.2-alpha, and all the servers are using the new
801 - Remove the code to generate the oldest (v1) directory format.
802 - Remove support for the old bw_accounting file: we've been storing
803 bandwidth accounting information in the state file since
804 0.1.2.5-alpha. This may result in bandwidth accounting errors
805 if you try to upgrade from 0.1.1.x or earlier, or if you try to
806 downgrade to 0.1.1.x or earlier.
807 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
808 it, it had no AES, and it hasn't seen any security patches since
810 - Stop overloading the circuit_t.onionskin field for both "onionskin
811 from a CREATE cell that we are waiting for a cpuworker to be
812 assigned" and "onionskin from an EXTEND cell that we are going to
813 send to an OR as soon as we are connected". Might help with bug 600.
814 - Remove the tor_strpartition() function: its logic was confused,
815 and it was only used for one thing that could be implemented far
817 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
818 and TorControl.py, as they use the old v0 controller protocol,
819 and are obsoleted by TorFlow anyway.
820 - Drop support for v1 rendezvous descriptors, since we never used
821 them anyway, and the code has probably rotted by now. Based on
822 patch from Karsten Loesing.
823 - Stop allowing address masks that do not correspond to bit prefixes.
824 We have warned about these for a really long time; now it's time
825 to reject them. (Patch from croup.)
826 - Remove an optimization in the AES counter-mode code that assumed
827 that the counter never exceeded 2^68. When the counter can be set
828 arbitrarily as an IV (as it is by Karsten's new hidden services
829 code), this assumption no longer holds.
830 - Disable the SETROUTERPURPOSE controller command: it is now
834 Changes in version 0.1.2.19 - 2008-01-17
835 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
836 exit policy a little bit more conservative so it's safer to run an
837 exit relay on a home system, and fixes a variety of smaller issues.
840 - Exit policies now reject connections that are addressed to a
841 relay's public (external) IP address too, unless
842 ExitPolicyRejectPrivate is turned off. We do this because too
843 many relays are running nearby to services that trust them based
847 - When the clock jumps forward a lot, do not allow the bandwidth
848 buckets to become negative. Fixes bug 544.
849 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
850 on every successful resolve. Reported by Mike Perry.
851 - Purge old entries from the "rephist" database and the hidden
852 service descriptor database even when DirPort is zero.
853 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
854 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
855 crashing or mis-answering these requests.
856 - When we decide to send a 503 response to a request for servers, do
857 not then also send the server descriptors: this defeats the whole
858 purpose. Fixes bug 539.
861 - Changing the ExitPolicyRejectPrivate setting should cause us to
862 rebuild our server descriptor.
863 - Fix handling of hex nicknames when answering controller requests for
864 networkstatus by name, or when deciding whether to warn about
865 unknown routers in a config option. (Patch from mwenge.)
866 - Fix a couple of hard-to-trigger autoconf problems that could result
867 in really weird results on platforms whose sys/types.h files define
868 nonstandard integer types.
869 - Don't try to create the datadir when running --verify-config or
870 --hash-password. Resolves bug 540.
871 - If we were having problems getting a particular descriptor from the
872 directory caches, and then we learned about a new descriptor for
873 that router, we weren't resetting our failure count. Reported
875 - Although we fixed bug 539 (where servers would send HTTP status 503
876 responses _and_ send a body too), there are still servers out there
877 that haven't upgraded. Therefore, make clients parse such bodies
878 when they receive them.
879 - Run correctly on systems where rlim_t is larger than unsigned long.
880 This includes some 64-bit systems.
881 - Run correctly on platforms (like some versions of OS X 10.5) where
882 the real limit for number of open files is OPEN_FILES, not rlim_max
883 from getrlimit(RLIMIT_NOFILES).
884 - Avoid a spurious free on base64 failure.
885 - Avoid segfaults on certain complex invocations of
886 router_get_by_hexdigest().
887 - Fix rare bug on REDIRECTSTREAM control command when called with no
888 port set: it could erroneously report an error when none had
892 Changes in version 0.1.2.18 - 2007-10-28
893 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
894 hidden service introduction that were causing huge delays, and a big
895 bug that was causing some servers to disappear from the network status
896 lists for a few hours each day.
898 o Major bugfixes (crashes):
899 - If a connection is shut down abruptly because of something that
900 happened inside connection_flushed_some(), do not call
901 connection_finished_flushing(). Should fix bug 451:
902 "connection_stop_writing: Assertion conn->write_event failed"
903 Bugfix on 0.1.2.7-alpha.
904 - Fix possible segfaults in functions called from
905 rend_process_relay_cell().
907 o Major bugfixes (hidden services):
908 - Hidden services were choosing introduction points uniquely by
909 hexdigest, but when constructing the hidden service descriptor
910 they merely wrote the (potentially ambiguous) nickname.
911 - Clients now use the v2 intro format for hidden service
912 connections: they specify their chosen rendezvous point by identity
913 digest rather than by (potentially ambiguous) nickname. These
914 changes could speed up hidden service connections dramatically.
916 o Major bugfixes (other):
917 - Stop publishing a new server descriptor just because we get a
918 HUP signal. This led (in a roundabout way) to some servers getting
919 dropped from the networkstatus lists for a few hours each day.
920 - When looking for a circuit to cannibalize, consider family as well
921 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
922 circuit cannibalization).
923 - When a router wasn't listed in a new networkstatus, we were leaving
924 the flags for that router alone -- meaning it remained Named,
925 Running, etc -- even though absence from the networkstatus means
926 that it shouldn't be considered to exist at all anymore. Now we
927 clear all the flags for routers that fall out of the networkstatus
928 consensus. Fixes bug 529.
931 - Don't try to access (or alter) the state file when running
932 --list-fingerprint or --verify-config or --hash-password. Resolves
934 - When generating information telling us how to extend to a given
935 router, do not try to include the nickname if it is
936 absent. Resolves bug 467.
937 - Fix a user-triggerable segfault in expand_filename(). (There isn't
938 a way to trigger this remotely.)
939 - When sending a status event to the controller telling it that an
940 OR address is reachable, set the port correctly. (Previously we
941 were reporting the dir port.)
942 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
943 command. Bugfix on 0.1.2.17.
944 - When loading bandwidth history, do not believe any information in
945 the future. Fixes bug 434.
946 - When loading entry guard information, do not believe any information
948 - When we have our clock set far in the future and generate an
949 onion key, then re-set our clock to be correct, we should not stop
950 the onion key from getting rotated.
951 - On some platforms, accept() can return a broken address. Detect
952 this more quietly, and deal accordingly. Fixes bug 483.
953 - It's not actually an error to find a non-pending entry in the DNS
954 cache when canceling a pending resolve. Don't log unless stuff
955 is fishy. Resolves bug 463.
956 - Don't reset trusted dir server list when we set a configuration
957 option. Patch from Robert Hogan.
960 Changes in version 0.1.2.17 - 2007-08-30
961 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
962 X bundles. Vidalia 0.0.14 makes authentication required for the
963 ControlPort in the default configuration, which addresses important
964 security risks. Everybody who uses Vidalia (or another controller)
967 In addition, this Tor update fixes major load balancing problems with
968 path selection, which should speed things up a lot once many people
971 o Major bugfixes (security):
972 - We removed support for the old (v0) control protocol. It has been
973 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
974 become more of a headache than it's worth.
976 o Major bugfixes (load balancing):
977 - When choosing nodes for non-guard positions, weight guards
978 proportionally less, since they already have enough load. Patch
980 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
981 will allow fast Tor servers to get more attention.
982 - When we're upgrading from an old Tor version, forget our current
983 guards and pick new ones according to the new weightings. These
984 three load balancing patches could raise effective network capacity
985 by a factor of four. Thanks to Mike Perry for measurements.
987 o Major bugfixes (stream expiration):
988 - Expire not-yet-successful application streams in all cases if
989 they've been around longer than SocksTimeout. Right now there are
990 some cases where the stream will live forever, demanding a new
991 circuit every 15 seconds. Fixes bug 454; reported by lodger.
993 o Minor features (controller):
994 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
995 is valid before any authentication has been received. It tells
996 a controller what kind of authentication is expected, and what
997 protocol is spoken. Implements proposal 119.
999 o Minor bugfixes (performance):
1000 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
1001 greatly speeding up loading cached-routers from disk on startup.
1002 - Disable sentinel-based debugging for buffer code: we squashed all
1003 the bugs that this was supposed to detect a long time ago, and now
1004 its only effect is to change our buffer sizes from nice powers of
1005 two (which platform mallocs tend to like) to values slightly over
1006 powers of two (which make some platform mallocs sad).
1008 o Minor bugfixes (misc):
1009 - If exit bandwidth ever exceeds one third of total bandwidth, then
1010 use the correct formula to weight exit nodes when choosing paths.
1011 Based on patch from Mike Perry.
1012 - Choose perfectly fairly among routers when choosing by bandwidth and
1013 weighting by fraction of bandwidth provided by exits. Previously, we
1014 would choose with only approximate fairness, and correct ourselves
1015 if we ran off the end of the list.
1016 - If we require CookieAuthentication but we fail to write the
1017 cookie file, we would warn but not exit, and end up in a state
1018 where no controller could authenticate. Now we exit.
1019 - If we require CookieAuthentication, stop generating a new cookie
1020 every time we change any piece of our config.
1021 - Refuse to start with certain directory authority keys, and
1022 encourage people using them to stop.
1023 - Terminate multi-line control events properly. Original patch
1025 - Fix a minor memory leak when we fail to find enough suitable
1026 servers to choose a circuit.
1027 - Stop leaking part of the descriptor when we run into a particularly
1028 unparseable piece of it.
1031 Changes in version 0.1.2.16 - 2007-08-01
1032 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
1033 remote attacker in certain situations to rewrite the user's torrc
1034 configuration file. This can completely compromise anonymity of users
1035 in most configurations, including those running the Vidalia bundles,
1036 TorK, etc. Or worse.
1038 o Major security fixes:
1039 - Close immediately after missing authentication on control port;
1040 do not allow multiple authentication attempts.
1043 Changes in version 0.1.2.15 - 2007-07-17
1044 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
1045 problems, fixes compilation on BSD, and fixes a variety of other
1046 bugs. Everybody should upgrade.
1048 o Major bugfixes (compilation):
1049 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
1051 o Major bugfixes (crashes):
1052 - Try even harder not to dereference the first character after
1053 an mmap(). Reported by lodger.
1054 - Fix a crash bug in directory authorities when we re-number the
1055 routerlist while inserting a new router.
1056 - When the cached-routers file is an even multiple of the page size,
1057 don't run off the end and crash. (Fixes bug 455; based on idea
1059 - Fix eventdns.c behavior on Solaris: It is critical to include
1060 orconfig.h _before_ sys/types.h, so that we can get the expected
1061 definition of _FILE_OFFSET_BITS.
1063 o Major bugfixes (security):
1064 - Fix a possible buffer overrun when using BSD natd support. Bug
1066 - When sending destroy cells from a circuit's origin, don't include
1067 the reason for tearing down the circuit. The spec says we didn't,
1068 and now we actually don't. Reported by lodger.
1069 - Keep streamids from different exits on a circuit separate. This
1070 bug may have allowed other routers on a given circuit to inject
1071 cells into streams. Reported by lodger; fixes bug 446.
1072 - If there's a never-before-connected-to guard node in our list,
1073 never choose any guards past it. This way we don't expand our
1074 guard list unless we need to.
1076 o Minor bugfixes (guard nodes):
1077 - Weight guard selection by bandwidth, so that low-bandwidth nodes
1078 don't get overused as guards.
1080 o Minor bugfixes (directory):
1081 - Correctly count the number of authorities that recommend each
1082 version. Previously, we were under-counting by 1.
1083 - Fix a potential crash bug when we load many server descriptors at
1084 once and some of them make others of them obsolete. Fixes bug 458.
1086 o Minor bugfixes (hidden services):
1087 - Stop tearing down the whole circuit when the user asks for a
1088 connection to a port that the hidden service didn't configure.
1091 o Minor bugfixes (misc):
1092 - On Windows, we were preventing other processes from reading
1093 cached-routers while Tor was running. Reported by janbar.
1094 - Fix a possible (but very unlikely) bug in picking routers by
1095 bandwidth. Add a log message to confirm that it is in fact
1096 unlikely. Patch from lodger.
1097 - Backport a couple of memory leak fixes.
1098 - Backport miscellaneous cosmetic bugfixes.
1101 Changes in version 0.1.2.14 - 2007-05-25
1102 Tor 0.1.2.14 changes the addresses of two directory authorities (this
1103 change especially affects those who serve or use hidden services),
1104 and fixes several other crash- and security-related bugs.
1106 o Directory authority changes:
1107 - Two directory authorities (moria1 and moria2) just moved to new
1108 IP addresses. This change will particularly affect those who serve
1109 or use hidden services.
1111 o Major bugfixes (crashes):
1112 - If a directory server runs out of space in the connection table
1113 as it's processing a begin_dir request, it will free the exit stream
1114 but leave it attached to the circuit, leading to unpredictable
1115 behavior. (Reported by seeess, fixes bug 425.)
1116 - Fix a bug in dirserv_remove_invalid() that would cause authorities
1117 to corrupt memory under some really unlikely scenarios.
1118 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
1119 - Avoid segfaults when reading from mmaped descriptor file. (Reported
1122 o Major bugfixes (security):
1123 - When choosing an entry guard for a circuit, avoid using guards
1124 that are in the same family as the chosen exit -- not just guards
1125 that are exactly the chosen exit. (Reported by lodger.)
1127 o Major bugfixes (resource management):
1128 - If a directory authority is down, skip it when deciding where to get
1129 networkstatus objects or descriptors. Otherwise we keep asking
1130 every 10 seconds forever. Fixes bug 384.
1131 - Count it as a failure if we fetch a valid network-status but we
1132 don't want to keep it. Otherwise we'll keep fetching it and keep
1133 not wanting to keep it. Fixes part of bug 422.
1134 - If all of our dirservers have given us bad or no networkstatuses
1135 lately, then stop hammering them once per minute even when we
1136 think they're failed. Fixes another part of bug 422.
1139 - Actually set the purpose correctly for descriptors inserted with
1141 - When we have k non-v2 authorities in our DirServer config,
1142 we ignored the last k authorities in the list when updating our
1144 - Correctly back-off from requesting router descriptors that we are
1145 having a hard time downloading.
1146 - Read resolv.conf files correctly on platforms where read() returns
1147 partial results on small file reads.
1148 - Don't rebuild the entire router store every time we get 32K of
1149 routers: rebuild it when the journal gets very large, or when
1150 the gaps in the store get very large.
1153 - When routers publish SVN revisions in their router descriptors,
1154 authorities now include those versions correctly in networkstatus
1156 - Warn when using a version of libevent before 1.3b to run a server on
1157 OSX or BSD: these versions interact badly with userspace threads.
1160 Changes in version 0.1.2.13 - 2007-04-24
1161 This release features some major anonymity fixes, such as safer path
1162 selection; better client performance; faster bootstrapping, better
1163 address detection, and better DNS support for servers; write limiting as
1164 well as read limiting to make servers easier to run; and a huge pile of
1165 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
1167 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
1168 of the Freenode IRC network, remembering his patience and vision for
1169 free speech on the Internet.
1171 o Major features, client performance:
1172 - Weight directory requests by advertised bandwidth. Now we can
1173 let servers enable write limiting but still allow most clients to
1174 succeed at their directory requests. (We still ignore weights when
1175 choosing a directory authority; I hope this is a feature.)
1176 - Stop overloading exit nodes -- avoid choosing them for entry or
1177 middle hops when the total bandwidth available from non-exit nodes
1178 is much higher than the total bandwidth available from exit nodes.
1179 - Rather than waiting a fixed amount of time between retrying
1180 application connections, we wait only 10 seconds for the first,
1181 10 seconds for the second, and 15 seconds for each retry after
1182 that. Hopefully this will improve the expected user experience.
1183 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
1184 to open a stream fails; now we do in more cases. This should
1185 make clients able to find a good exit faster in some cases, since
1186 unhandleable requests will now get an error rather than timing out.
1188 o Major features, client functionality:
1189 - Implement BEGIN_DIR cells, so we can connect to a directory
1190 server via TLS to do encrypted directory requests rather than
1191 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
1192 config options if you like. For now, this feature only works if
1193 you already have a descriptor for the destination dirserver.
1194 - Add support for transparent application connections: this basically
1195 bundles the functionality of trans-proxy-tor into the Tor
1196 mainline. Now hosts with compliant pf/netfilter implementations
1197 can redirect TCP connections straight to Tor without diverting
1198 through SOCKS. (Based on patch from tup.)
1199 - Add support for using natd; this allows FreeBSDs earlier than
1200 5.1.2 to have ipfw send connections through Tor without using
1201 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
1203 o Major features, servers:
1204 - Setting up a dyndns name for your server is now optional: servers
1205 with no hostname or IP address will learn their IP address by
1206 asking the directory authorities. This code only kicks in when you
1207 would normally have exited with a "no address" error. Nothing's
1208 authenticated, so use with care.
1209 - Directory servers now spool server descriptors, v1 directories,
1210 and v2 networkstatus objects to buffers as needed rather than en
1211 masse. They also mmap the cached-routers files. These steps save
1213 - Stop requiring clients to have well-formed certificates, and stop
1214 checking nicknames in certificates. (Clients have certificates so
1215 that they can look like Tor servers, but in the future we might want
1216 to allow them to look like regular TLS clients instead. Nicknames
1217 in certificates serve no purpose other than making our protocol
1218 easier to recognize on the wire.) Implements proposal 106.
1220 o Improvements on DNS support:
1221 - Add "eventdns" asynchronous dns library originally based on code
1222 from Adam Langley. Now we can discard the old rickety dnsworker
1223 concept, and support a wider variety of DNS functions. Allows
1224 multithreaded builds on NetBSD and OpenBSD again.
1225 - Add server-side support for "reverse" DNS lookups (using PTR
1226 records so clients can determine the canonical hostname for a given
1227 IPv4 address). Only supported by servers using eventdns; servers
1228 now announce in their descriptors if they don't support eventdns.
1229 - Workaround for name servers (like Earthlink's) that hijack failing
1230 DNS requests and replace the no-such-server answer with a "helpful"
1231 redirect to an advertising-driven search portal. Also work around
1232 DNS hijackers who "helpfully" decline to hijack known-invalid
1233 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
1234 lets you turn it off.
1235 - Servers now check for the case when common DNS requests are going to
1236 wildcarded addresses (i.e. all getting the same answer), and change
1237 their exit policy to reject *:* if it's happening.
1238 - When asked to resolve a hostname, don't use non-exit servers unless
1239 requested to do so. This allows servers with broken DNS to be
1240 useful to the network.
1241 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
1242 useless IPv6 DNS resolves.
1243 - Specify and implement client-side SOCKS5 interface for reverse DNS
1244 lookups (see doc/socks-extensions.txt). Also cache them.
1245 - When we change nameservers or IP addresses, reset and re-launch
1246 our tests for DNS hijacking.
1248 o Improvements on reachability testing:
1249 - Servers send out a burst of long-range padding cells once they've
1250 established that they're reachable. Spread them over 4 circuits,
1251 so hopefully a few will be fast. This exercises bandwidth and
1252 bootstraps them into the directory more quickly.
1253 - When we find our DirPort to be reachable, publish a new descriptor
1254 so we'll tell the world (reported by pnx).
1255 - Directory authorities now only decide that routers are reachable
1256 if their identity keys are as expected.
1257 - Do DirPort reachability tests less often, since a single test
1258 chews through many circuits before giving up.
1259 - Avoid some false positives during reachability testing: don't try
1260 to test via a server that's on the same /24 network as us.
1261 - Start publishing one minute or so after we find our ORPort
1262 to be reachable. This will help reduce the number of descriptors
1263 we have for ourselves floating around, since it's quite likely
1264 other things (e.g. DirPort) will change during that minute too.
1265 - Routers no longer try to rebuild long-term connections to directory
1266 authorities, and directory authorities no longer try to rebuild
1267 long-term connections to all servers. We still don't hang up
1268 connections in these two cases though -- we need to look at it
1269 more carefully to avoid flapping, and we likely need to wait til
1270 0.1.1.x is obsolete.
1272 o Improvements on rate limiting:
1273 - Enable write limiting as well as read limiting. Now we sacrifice
1274 capacity if we're pushing out lots of directory traffic, rather
1275 than overrunning the user's intended bandwidth limits.
1276 - Include TLS overhead when counting bandwidth usage; previously, we
1277 would count only the bytes sent over TLS, but not the bytes used
1279 - Servers decline directory requests much more aggressively when
1280 they're low on bandwidth. Otherwise they end up queueing more and
1281 more directory responses, which can't be good for latency.
1282 - But never refuse directory requests from local addresses.
1283 - Be willing to read or write on local connections (e.g. controller
1284 connections) even when the global rate limiting buckets are empty.
1285 - Flush local controller connection buffers periodically as we're
1286 writing to them, so we avoid queueing 4+ megabytes of data before
1288 - Revise and clean up the torrc.sample that we ship with; add
1289 a section for BandwidthRate and BandwidthBurst.
1291 o Major features, NT services:
1292 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
1293 command-line flag so that admins can override the default by saying
1294 "tor --service install --user "SomeUser"". This will not affect
1295 existing installed services. Also, warn the user that the service
1296 will look for its configuration file in the service user's
1297 %appdata% directory. (We can't do the "hardwire the user's appdata
1298 directory" trick any more, since we may not have read access to that
1300 - Support running the Tor service with a torrc not in the same
1301 directory as tor.exe and default to using the torrc located in
1302 the %appdata%\Tor\ of the user who installed the service. Patch
1304 - Add an --ignore-missing-torrc command-line option so that we can
1305 get the "use sensible defaults if the configuration file doesn't
1306 exist" behavior even when specifying a torrc location on the
1308 - When stopping an NT service, wait up to 10 sec for it to actually
1309 stop. (Patch from Matt Edman; resolves bug 295.)
1311 o Directory authority improvements:
1312 - Stop letting hibernating or obsolete servers affect uptime and
1314 - Stop listing hibernating servers in the v1 directory.
1315 - Authorities no longer recommend exits as guards if this would shift
1316 too much load to the exit nodes.
1317 - Authorities now specify server versions in networkstatus. This adds
1318 about 2% to the size of compressed networkstatus docs, and allows
1319 clients to tell which servers support BEGIN_DIR and which don't.
1320 The implementation is forward-compatible with a proposed future
1321 protocol version scheme not tied to Tor versions.
1322 - DirServer configuration lines now have an orport= option so
1323 clients can open encrypted tunnels to the authorities without
1324 having downloaded their descriptors yet. Enabled for moria1,
1325 moria2, tor26, and lefkada now in the default configuration.
1326 - Add a BadDirectory flag to network status docs so that authorities
1327 can (eventually) tell clients about caches they believe to be
1328 broken. Not used yet.
1329 - Allow authorities to list nodes as bad exits in their
1330 approved-routers file by fingerprint or by address. If most
1331 authorities set a BadExit flag for a server, clients don't think
1332 of it as a general-purpose exit. Clients only consider authorities
1333 that advertise themselves as listing bad exits.
1334 - Patch from Steve Hildrey: Generate network status correctly on
1335 non-versioning dirservers.
1336 - Have directory authorities allow larger amounts of drift in uptime
1337 without replacing the server descriptor: previously, a server that
1338 restarted every 30 minutes could have 48 "interesting" descriptors
1340 - Reserve the nickname "Unnamed" for routers that can't pick
1341 a hostname: any router can call itself Unnamed; directory
1342 authorities will never allocate Unnamed to any particular router;
1343 clients won't believe that any router is the canonical Unnamed.
1345 o Directory mirrors and clients:
1346 - Discard any v1 directory info that's over 1 month old (for
1347 directories) or over 1 week old (for running-routers lists).
1348 - Clients track responses with status 503 from dirservers. After a
1349 dirserver has given us a 503, we try not to use it until an hour has
1350 gone by, or until we have no dirservers that haven't given us a 503.
1351 - When we get a 503 from a directory, and we're not a server, we no
1352 longer count the failure against the total number of failures
1353 allowed for the object we're trying to download.
1354 - Prepare for servers to publish descriptors less often: never
1355 discard a descriptor simply for being too old until either it is
1356 recommended by no authorities, or until we get a better one for
1357 the same router. Make caches consider retaining old recommended
1358 routers for even longer.
1359 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
1360 headers for content, so that we can work better in the presence of
1361 caching HTTP proxies.
1362 - Stop fetching descriptors if you're not a dir mirror and you
1363 haven't tried to establish any circuits lately. (This currently
1364 causes some dangerous behavior, because when you start up again
1365 you'll use your ancient server descriptors.)
1367 o Major fixes, crashes:
1368 - Stop crashing when the controller asks us to resetconf more than
1369 one config option at once. (Vidalia 0.0.11 does this.)
1370 - Fix a longstanding obscure crash bug that could occur when we run
1371 out of DNS worker processes, if we're not using eventdns. (Resolves
1373 - Fix an assert that could trigger if a controller quickly set then
1374 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
1375 - Avoid crash when telling controller about stream-status and a
1377 - Avoid sending junk to controllers or segfaulting when a controller
1378 uses EVENT_NEW_DESC with verbose nicknames.
1379 - Stop triggering asserts if the controller tries to extend hidden
1380 service circuits (reported by mwenge).
1381 - If we start a server with ClientOnly 1, then set ClientOnly to 0
1382 and hup, stop triggering an assert based on an empty onion_key.
1383 - Mask out all signals in sub-threads; only the libevent signal
1384 handler should be processing them. This should prevent some crashes
1385 on some machines using pthreads. (Patch from coderman.)
1386 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
1388 o Major fixes, anonymity/security:
1389 - Automatically avoid picking more than one node from the same
1390 /16 network when constructing a circuit. Add an
1391 "EnforceDistinctSubnets" option to let people disable it if they
1392 want to operate private test networks on a single subnet.
1393 - When generating bandwidth history, round down to the nearest
1394 1k. When storing accounting data, round up to the nearest 1k.
1395 - When we're running as a server, remember when we last rotated onion
1396 keys, so that we will rotate keys once they're a week old even if
1397 we never stay up for a week ourselves.
1398 - If a client asked for a server by name, and there's a named server
1399 in our network-status but we don't have its descriptor yet, we
1400 could return an unnamed server instead.
1401 - Reject (most) attempts to use Tor circuits with length one. (If
1402 many people start using Tor as a one-hop proxy, exit nodes become
1403 a more attractive target for compromise.)
1404 - Just because your DirPort is open doesn't mean people should be
1405 able to remotely teach you about hidden service descriptors. Now
1406 only accept rendezvous posts if you've got HSAuthoritativeDir set.
1407 - Fix a potential race condition in the rpm installer. Found by
1409 - Do not log IPs with TLS failures for incoming TLS
1410 connections. (Fixes bug 382.)
1412 o Major fixes, other:
1413 - If our system clock jumps back in time, don't publish a negative
1414 uptime in the descriptor.
1415 - When we start during an accounting interval before it's time to wake
1416 up, remember to wake up at the correct time. (May fix bug 342.)
1417 - Previously, we would cache up to 16 old networkstatus documents
1418 indefinitely, if they came from nontrusted authorities. Now we
1419 discard them if they are more than 10 days old.
1420 - When we have a state file we cannot parse, tell the user and
1421 move it aside. Now we avoid situations where the user starts
1422 Tor in 1904, Tor writes a state file with that timestamp in it,
1423 the user fixes her clock, and Tor refuses to start.
1424 - Publish a new descriptor after we hup/reload. This is important
1425 if our config has changed such that we'll want to start advertising
1426 our DirPort now, etc.
1427 - If we are using an exit enclave and we can't connect, e.g. because
1428 its webserver is misconfigured to not listen on localhost, then
1429 back off and try connecting from somewhere else before we fail.
1431 o New config options or behaviors:
1432 - When EntryNodes are configured, rebuild the guard list to contain,
1433 in order: the EntryNodes that were guards before; the rest of the
1434 EntryNodes; the nodes that were guards before.
1435 - Do not warn when individual nodes in the configuration's EntryNodes,
1436 ExitNodes, etc are down: warn only when all possible nodes
1437 are down. (Fixes bug 348.)
1438 - Put a lower-bound on MaxAdvertisedBandwidth.
1439 - Start using the state file to store bandwidth accounting data:
1440 the bw_accounting file is now obsolete. We'll keep generating it
1441 for a while for people who are still using 0.1.2.4-alpha.
1442 - Try to batch changes to the state file so that we do as few
1443 disk writes as possible while still storing important things in
1445 - The state file and the bw_accounting file get saved less often when
1446 the AvoidDiskWrites config option is set.
1447 - Make PIDFile work on Windows.
1448 - Add internal descriptions for a bunch of configuration options:
1449 accessible via controller interface and in comments in saved
1451 - Reject *:563 (NNTPS) in the default exit policy. We already reject
1452 NNTP by default, so this seems like a sensible addition.
1453 - Clients now reject hostnames with invalid characters. This should
1454 avoid some inadvertent info leaks. Add an option
1455 AllowNonRFC953Hostnames to disable this behavior, in case somebody
1456 is running a private network with hosts called @, !, and #.
1457 - Check for addresses with invalid characters at the exit as well,
1458 and warn less verbosely when they fail. You can override this by
1459 setting ServerDNSAllowNonRFC953Addresses to 1.
1460 - Remove some options that have been deprecated since at least
1461 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
1462 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
1463 to set log options. Mark PathlenCoinWeight as obsolete.
1464 - Stop accepting certain malformed ports in configured exit policies.
1465 - When the user uses bad syntax in the Log config line, stop
1466 suggesting other bad syntax as a replacement.
1467 - Add new config option "ResolvConf" to let the server operator
1468 choose an alternate resolve.conf file when using eventdns.
1469 - If one of our entry guards is on the ExcludeNodes list, or the
1470 directory authorities don't think it's a good guard, treat it as
1471 if it were unlisted: stop using it as a guard, and throw it off
1472 the guards list if it stays that way for a long time.
1473 - Allow directory authorities to be marked separately as authorities
1474 for the v1 directory protocol, the v2 directory protocol, and
1475 as hidden service directories, to make it easier to retire old
1476 authorities. V1 authorities should set "HSAuthoritativeDir 1"
1477 to continue being hidden service authorities too.
1478 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
1479 - Make TrackExitHosts case-insensitive, and fix the behavior of
1480 ".suffix" TrackExitHosts items to avoid matching in the middle of
1482 - New DirPort behavior: if you have your dirport set, you download
1483 descriptors aggressively like a directory mirror, whether or not
1487 - Create a new file ReleaseNotes which was the old ChangeLog. The
1488 new ChangeLog file now includes the notes for all development
1490 - Add a new address-spec.txt document to describe our special-case
1491 addresses: .exit, .onion, and .noconnnect.
1492 - Fork the v1 directory protocol into its own spec document,
1493 and mark dir-spec.txt as the currently correct (v2) spec.
1495 o Packaging, porting, and contrib
1496 - "tor --verify-config" now exits with -1(255) or 0 depending on
1497 whether the config options are bad or good.
1498 - The Debian package now uses --verify-config when (re)starting,
1499 to distinguish configuration errors from other errors.
1500 - Adapt a patch from goodell to let the contrib/exitlist script
1501 take arguments rather than require direct editing.
1502 - Prevent the contrib/exitlist script from printing the same
1503 result more than once.
1504 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
1505 - In the hidden service example in torrc.sample, stop recommending
1506 esoteric and discouraged hidden service options.
1507 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
1508 values before failing, and always enables eventdns.
1509 - Try to detect Windows correctly when cross-compiling.
1510 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
1511 Try to fix this in configure.in by checking for most functions
1512 before we check for libevent.
1513 - Update RPMs to require libevent 1.2.
1514 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
1515 or later. Log when we are doing this, so we can diagnose it when
1516 it fails. (Also, recommend libevent 1.1b for kqueue and
1517 win32 methods; deprecate libevent 1.0b harder; make libevent
1518 recommendation system saner.)
1519 - Build with recent (1.3+) libevents on platforms that do not
1520 define the nonstandard types "u_int8_t" and friends.
1521 - Remove architecture from OS X builds. The official builds are
1522 now universal binaries.
1523 - Run correctly on OS X platforms with case-sensitive filesystems.
1524 - Correctly set maximum connection limit on Cygwin. (This time
1526 - Start compiling on MinGW on Windows (patches from Mike Chiussi
1528 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
1529 - Finally fix the openssl warnings from newer gccs that believe that
1530 ignoring a return value is okay, but casting a return value and
1531 then ignoring it is a sign of madness.
1532 - On architectures where sizeof(int)>4, still clamp declarable
1533 bandwidth to INT32_MAX.
1535 o Minor features, controller:
1536 - Warn the user when an application uses the obsolete binary v0
1537 control protocol. We're planning to remove support for it during
1538 the next development series, so it's good to give people some
1540 - Add STREAM_BW events to report per-entry-stream bandwidth
1541 use. (Patch from Robert Hogan.)
1542 - Rate-limit SIGNEWNYM signals in response to controllers that
1543 impolitely generate them for every single stream. (Patch from
1544 mwenge; closes bug 394.)
1545 - Add a REMAP status to stream events to note that a stream's
1546 address has changed because of a cached address or a MapAddress
1548 - Make REMAP stream events have a SOURCE (cache or exit), and
1549 make them generated in every case where we get a successful
1550 connected or resolved cell.
1551 - Track reasons for OR connection failure; make these reasons
1552 available via the controller interface. (Patch from Mike Perry.)
1553 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
1554 can learn when clients are sending malformed hostnames to Tor.
1555 - Specify and implement some of the controller status events.
1556 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
1557 - Reimplement GETINFO so that info/names stays in sync with the
1559 - Implement "GETINFO fingerprint".
1560 - Implement "SETEVENTS GUARD" so controllers can get updates on
1561 entry guard status as it changes.
1562 - Make all connections to addresses of the form ".noconnect"
1563 immediately get closed. This lets application/controller combos
1564 successfully test whether they're talking to the same Tor by
1565 watching for STREAM events.
1566 - Add a REASON field to CIRC events; for backward compatibility, this
1567 field is sent only to controllers that have enabled the extended
1568 event format. Also, add additional reason codes to explain why
1569 a given circuit has been destroyed or truncated. (Patches from
1571 - Add a REMOTE_REASON field to extended CIRC events to tell the
1572 controller why a remote OR told us to close a circuit.
1573 - Stream events also now have REASON and REMOTE_REASON fields,
1574 working much like those for circuit events.
1575 - There's now a GETINFO ns/... field so that controllers can ask Tor
1576 about the current status of a router.
1577 - A new event type "NS" to inform a controller when our opinion of
1578 a router's status has changed.
1579 - Add a GETINFO events/names and GETINFO features/names so controllers
1580 can tell which events and features are supported.
1581 - A new CLEARDNSCACHE signal to allow controllers to clear the
1582 client-side DNS cache without expiring circuits.
1583 - Fix CIRC controller events so that controllers can learn the
1584 identity digests of non-Named servers used in circuit paths.
1585 - Let controllers ask for more useful identifiers for servers. Instead
1586 of learning identity digests for un-Named servers and nicknames
1587 for Named servers, the new identifiers include digest, nickname,
1588 and indication of Named status. Off by default; see control-spec.txt
1589 for more information.
1590 - Add a "getinfo address" controller command so it can display Tor's
1591 best guess to the user.
1592 - New controller event to alert the controller when our server
1593 descriptor has changed.
1594 - Give more meaningful errors on controller authentication failure.
1595 - Export the default exit policy via the control port, so controllers
1596 don't need to guess what it is / will be later.
1598 o Minor bugfixes, controller:
1599 - When creating a circuit via the controller, send a 'launched'
1600 event when we're done, so we follow the spec better.
1601 - Correct the control spec to match how the code actually responds
1602 to 'getinfo addr-mappings/*'. Reported by daejees.
1603 - The control spec described a GUARDS event, but the code
1604 implemented a GUARD event. Standardize on GUARD, but let people
1605 ask for GUARDS too. Reported by daejees.
1606 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
1607 clear the corresponding on_circuit variable, and remember later
1608 that we don't need to send a redundant CLOSED event. (Resolves part
1610 - Report events where a resolve succeeded or where we got a socks
1611 protocol error correctly, rather than calling both of them
1613 - Change reported stream target addresses to IP consistently when
1614 we finally get the IP from an exit node.
1615 - Send log messages to the controller even if they happen to be very
1617 - Flush ERR-level controller status events just like we currently
1618 flush ERR-level log events, so that a Tor shutdown doesn't prevent
1619 the controller from learning about current events.
1620 - Report the circuit number correctly in STREAM CLOSED events. Bug
1621 reported by Mike Perry.
1622 - Do not report bizarre values for results of accounting GETINFOs
1623 when the last second's write or read exceeds the allotted bandwidth.
1624 - Report "unrecognized key" rather than an empty string when the
1625 controller tries to fetch a networkstatus that doesn't exist.
1626 - When the controller does a "GETINFO network-status", tell it
1627 about even those routers whose descriptors are very old, and use
1628 long nicknames where appropriate.
1629 - Fix handling of verbose nicknames with ORCONN controller events:
1630 make them show up exactly when requested, rather than exactly when
1632 - Controller signals now work on non-Unix platforms that don't define
1633 SIGUSR1 and SIGUSR2 the way we expect.
1634 - Respond to SIGNAL command before we execute the signal, in case
1635 the signal shuts us down. Suggested by Karsten Loesing.
1636 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
1638 o Minor features, code performance:
1639 - Major performance improvement on inserting descriptors: change
1640 algorithm from O(n^2) to O(n).
1641 - Do not rotate onion key immediately after setting it for the first
1643 - Call router_have_min_dir_info half as often. (This is showing up in
1644 some profiles, but not others.)
1645 - When using GCC, make log_debug never get called at all, and its
1646 arguments never get evaluated, when no debug logs are configured.
1647 (This is showing up in some profiles, but not others.)
1648 - Statistics dumped by -USR2 now include a breakdown of public key
1649 operations, for profiling.
1650 - Make the common memory allocation path faster on machines where
1651 malloc(0) returns a pointer.
1652 - Split circuit_t into origin_circuit_t and or_circuit_t, and
1653 split connection_t into edge, or, dir, control, and base structs.
1654 These will save quite a bit of memory on busy servers, and they'll
1655 also help us track down bugs in the code and bugs in the spec.
1656 - Use OpenSSL's AES implementation on platforms where it's faster.
1657 This could save us as much as 10% CPU usage.
1659 o Minor features, descriptors and descriptor handling:
1660 - Avoid duplicate entries on MyFamily line in server descriptor.
1661 - When Tor receives a router descriptor that it asked for, but
1662 no longer wants (because it has received fresh networkstatuses
1663 in the meantime), do not warn the user. Cache the descriptor if
1664 we're a cache; drop it if we aren't.
1665 - Servers no longer ever list themselves in their "family" line,
1666 even if configured to do so. This makes it easier to configure
1667 family lists conveniently.
1669 o Minor fixes, confusing/misleading log messages:
1670 - Display correct results when reporting which versions are
1671 recommended, and how recommended they are. (Resolves bug 383.)
1672 - Inform the server operator when we decide not to advertise a
1673 DirPort due to AccountingMax enabled or a low BandwidthRate.
1674 - Only include function names in log messages for info/debug messages.
1675 For notice/warn/err, the content of the message should be clear on
1676 its own, and printing the function name only confuses users.
1677 - Remove even more protocol-related warnings from Tor server logs,
1678 such as bad TLS handshakes and malformed begin cells.
1679 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
1680 when the IP address is mapped through MapAddress to a hostname.
1681 - Fix misleading log messages: an entry guard that is "unlisted",
1682 as well as not known to be "down" (because we've never heard
1683 of it), is not therefore "up".
1685 o Minor fixes, old/obsolete behavior:
1686 - Start assuming we can use a create_fast cell if we don't know
1687 what version a router is running.
1688 - We no longer look for identity and onion keys in "identity.key" and
1689 "onion.key" -- these were replaced by secret_id_key and
1690 secret_onion_key in 0.0.8pre1.
1691 - We no longer require unrecognized directory entries to be
1693 - Drop compatibility with obsolete Tors that permit create cells
1694 to have the wrong circ_id_type.
1695 - Remove code to special-case "-cvs" ending, since it has not
1696 actually mattered since 0.0.9.
1697 - Don't re-write the fingerprint file every restart, unless it has
1700 o Minor fixes, misc client-side behavior:
1701 - Always remove expired routers and networkstatus docs before checking
1702 whether we have enough information to build circuits. (Fixes
1704 - When computing clock skew from directory HTTP headers, consider what
1705 time it was when we finished asking for the directory, not what
1707 - Make our socks5 handling more robust to broken socks clients:
1708 throw out everything waiting on the buffer in between socks
1709 handshake phases, since they can't possibly (so the theory
1710 goes) have predicted what we plan to respond to them.
1711 - Expire socks connections if they spend too long waiting for the
1712 handshake to finish. Previously we would let them sit around for
1713 days, if the connecting application didn't close them either.
1714 - And if the socks handshake hasn't started, don't send a
1715 "DNS resolve socks failed" handshake reply; just close it.
1716 - If the user asks to use invalid exit nodes, be willing to use
1718 - Track unreachable entry guards correctly: don't conflate
1719 'unreachable by us right now' with 'listed as down by the directory
1720 authorities'. With the old code, if a guard was unreachable by us
1721 but listed as running, it would clog our guard list forever.
1722 - Behave correctly in case we ever have a network with more than
1723 2GB/s total advertised capacity.
1724 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
1725 - Fix a memory leak when we ask for "all" networkstatuses and we
1726 get one we don't recognize.
1729 Changes in version 0.1.1.26 - 2006-12-14
1730 o Security bugfixes:
1731 - Stop sending the HttpProxyAuthenticator string to directory
1732 servers when directory connections are tunnelled through Tor.
1733 - Clients no longer store bandwidth history in the state file.
1734 - Do not log introduction points for hidden services if SafeLogging
1738 - Fix an assert failure when a directory authority sets
1739 AuthDirRejectUnlisted and then receives a descriptor from an
1740 unlisted router (reported by seeess).
1743 Changes in version 0.1.1.25 - 2006-11-04
1745 - When a client asks us to resolve (rather than connect to)
1746 an address, and we have a cached answer, give them the cached
1747 answer. Previously, we would give them no answer at all.
1748 - We were building exactly the wrong circuits when we predict
1749 hidden service requirements, meaning Tor would have to build all
1750 its circuits on demand.
1751 - If none of our live entry guards have a high uptime, but we
1752 require a guard with a high uptime, try adding a new guard before
1753 we give up on the requirement. This patch should make long-lived
1754 connections more stable on average.
1755 - When testing reachability of our DirPort, don't launch new
1756 tests when there's already one in progress -- unreachable
1757 servers were stacking up dozens of testing streams.
1759 o Security bugfixes:
1760 - When the user sends a NEWNYM signal, clear the client-side DNS
1761 cache too. Otherwise we continue to act on previous information.
1764 - Avoid a memory corruption bug when creating a hash table for
1766 - Avoid possibility of controller-triggered crash when misusing
1767 certain commands from a v0 controller on platforms that do not
1768 handle printf("%s",NULL) gracefully.
1769 - Avoid infinite loop on unexpected controller input.
1770 - Don't log spurious warnings when we see a circuit close reason we
1771 don't recognize; it's probably just from a newer version of Tor.
1772 - Add Vidalia to the OS X uninstaller script, so when we uninstall
1773 Tor/Privoxy we also uninstall Vidalia.
1776 Changes in version 0.1.1.24 - 2006-09-29
1778 - Allow really slow clients to not hang up five minutes into their
1779 directory downloads (suggested by Adam J. Richter).
1780 - Fix major performance regression from 0.1.0.x: instead of checking
1781 whether we have enough directory information every time we want to
1782 do something, only check when the directory information has changed.
1783 This should improve client CPU usage by 25-50%.
1784 - Don't crash if, after a server has been running for a while,
1785 it can't resolve its hostname.
1786 - When a client asks us to resolve (not connect to) an address,
1787 and we have a cached answer, give them the cached answer.
1788 Previously, we would give them no answer at all.
1791 - Allow Tor to start when RunAsDaemon is set but no logs are set.
1792 - Don't crash when the controller receives a third argument to an
1793 "extendcircuit" request.
1794 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
1795 response; fix error code when "getinfo dir/status/" fails.
1796 - Fix configure.in to not produce broken configure files with
1797 more recent versions of autoconf. Thanks to Clint for his auto*
1799 - Fix security bug on NetBSD that could allow someone to force
1800 uninitialized RAM to be sent to a server's DNS resolver. This
1801 only affects NetBSD and other platforms that do not bounds-check
1803 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
1804 methods: these are known to be buggy.
1805 - If we're a directory mirror and we ask for "all" network status
1806 documents, we would discard status documents from authorities
1810 Changes in version 0.1.1.23 - 2006-07-30
1812 - Fast Tor servers, especially exit nodes, were triggering asserts
1813 due to a bug in handling the list of pending DNS resolves. Some
1814 bugs still remain here; we're hunting them.
1815 - Entry guards could crash clients by sending unexpected input.
1816 - More fixes on reachability testing: if you find yourself reachable,
1817 then don't ever make any client requests (so you stop predicting
1818 circuits), then hup or have your clock jump, then later your IP
1819 changes, you won't think circuits are working, so you won't try to
1820 test reachability, so you won't publish.
1823 - Avoid a crash if the controller does a resetconf firewallports
1824 and then a setconf fascistfirewall=1.
1825 - Avoid an integer underflow when the dir authority decides whether
1826 a router is stable: we might wrongly label it stable, and compute
1827 a slightly wrong median stability, when a descriptor is published
1829 - Fix a place where we might trigger an assert if we can't build our
1830 own server descriptor yet.
1833 Changes in version 0.1.1.22 - 2006-07-05
1835 - Fix a big bug that was causing servers to not find themselves
1836 reachable if they changed IP addresses. Since only 0.1.1.22+
1837 servers can do reachability testing correctly, now we automatically
1838 make sure to test via one of these.
1839 - Fix to allow clients and mirrors to learn directory info from
1840 descriptor downloads that get cut off partway through.
1841 - Directory authorities had a bug in deciding if a newly published
1842 descriptor was novel enough to make everybody want a copy -- a few
1843 servers seem to be publishing new descriptors many times a minute.
1845 - Fix a rare bug that was causing some servers to complain about
1846 "closing wedged cpuworkers" and skip some circuit create requests.
1847 - Make the Exit flag in directory status documents actually work.
1850 Changes in version 0.1.1.21 - 2006-06-10
1851 o Crash and assert fixes from 0.1.1.20:
1852 - Fix a rare crash on Tor servers that have enabled hibernation.
1853 - Fix a seg fault on startup for Tor networks that use only one
1854 directory authority.
1855 - Fix an assert from a race condition that occurs on Tor servers
1856 while exiting, where various threads are trying to log that they're
1857 exiting, and delete the logs, at the same time.
1858 - Make our unit tests pass again on certain obscure platforms.
1861 - Add support for building SUSE RPM packages.
1862 - Speed up initial bootstrapping for clients: if we are making our
1863 first ever connection to any entry guard, then don't mark it down
1865 - When only one Tor server in the network is labelled as a guard,
1866 and we've already picked him, we would cycle endlessly picking him
1867 again, being unhappy about it, etc. Now we specifically exclude
1868 current guards when picking a new guard.
1869 - Servers send create cells more reliably after the TLS connection
1870 is established: we were sometimes forgetting to send half of them
1871 when we had more than one pending.
1872 - If we get a create cell that asks us to extend somewhere, but the
1873 Tor server there doesn't match the expected digest, we now send
1874 a destroy cell back, rather than silently doing nothing.
1875 - Make options->RedirectExit work again.
1876 - Make cookie authentication for the controller work again.
1877 - Stop being picky about unusual characters in the arguments to
1878 mapaddress. It's none of our business.
1879 - Add a new config option "TestVia" that lets you specify preferred
1880 middle hops to use for test circuits. Perhaps this will let me
1881 debug the reachability problems better.
1883 o Log / documentation fixes:
1884 - If we're a server and some peer has a broken TLS certificate, don't
1885 log about it unless ProtocolWarnings is set, i.e., we want to hear
1886 about protocol violations by others.
1887 - Fix spelling of VirtualAddrNetwork in man page.
1888 - Add a better explanation at the top of the autogenerated torrc file
1889 about what happened to our old torrc.
1892 Changes in version 0.1.1.20 - 2006-05-23
1893 o Crash and assert fixes from 0.1.0.17:
1894 - Fix assert bug in close_logs() on exit: when we close and delete
1895 logs, remove them all from the global "logfiles" list.
1896 - Fix an assert error when we're out of space in the connection_list
1897 and we try to post a hidden service descriptor (reported by Peter
1899 - Fix a rare assert error when we've tried all intro points for
1900 a hidden service and we try fetching the service descriptor again:
1901 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
1902 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
1903 out and refuse the setconf if it would fail.
1904 - If you specify a relative torrc path and you set RunAsDaemon in
1905 your torrc, then it chdir()'s to the new directory. If you then
1906 HUP, it tries to load the new torrc location, fails, and exits.
1907 The fix: no longer allow a relative path to torrc when using -f.
1908 - Check for integer overflows in more places, when adding elements
1909 to smartlists. This could possibly prevent a buffer overflow
1910 on malicious huge inputs.
1912 o Security fixes, major:
1913 - When we're printing strings from the network, don't try to print
1914 non-printable characters. Now we're safer against shell escape
1915 sequence exploits, and also against attacks to fool users into
1916 misreading their logs.
1917 - Implement entry guards: automatically choose a handful of entry
1918 nodes and stick with them for all circuits. Only pick new guards
1919 when the ones you have are unsuitable, and if the old guards
1920 become suitable again, switch back. This will increase security
1921 dramatically against certain end-point attacks. The EntryNodes
1922 config option now provides some hints about which entry guards you
1923 want to use most; and StrictEntryNodes means to only use those.
1924 Fixes CVE-2006-0414.
1925 - Implement exit enclaves: if we know an IP address for the
1926 destination, and there's a running Tor server at that address
1927 which allows exit to the destination, then extend the circuit to
1928 that exit first. This provides end-to-end encryption and end-to-end
1929 authentication. Also, if the user wants a .exit address or enclave,
1930 use 4 hops rather than 3, and cannibalize a general circ for it
1932 - Obey our firewall options more faithfully:
1933 . If we can't get to a dirserver directly, try going via Tor.
1934 . Don't ever try to connect (as a client) to a place our
1935 firewall options forbid.
1936 . If we specify a proxy and also firewall options, obey the
1937 firewall options even when we're using the proxy: some proxies
1938 can only proxy to certain destinations.
1939 - Make clients regenerate their keys when their IP address changes.
1940 - For the OS X package's modified privoxy config file, comment
1941 out the "logfile" line so we don't log everything passed
1943 - Our TLS handshakes were generating a single public/private
1944 keypair for the TLS context, rather than making a new one for
1945 each new connection. Oops. (But we were still rotating them
1946 periodically, so it's not so bad.)
1947 - When we were cannibalizing a circuit with a particular exit
1948 node in mind, we weren't checking to see if that exit node was
1949 already present earlier in the circuit. Now we are.
1950 - Require server descriptors to list IPv4 addresses -- hostnames
1951 are no longer allowed. This also fixes potential vulnerabilities
1952 to servers providing hostnames as their address and then
1953 preferentially resolving them so they can partition users.
1954 - Our logic to decide if the OR we connected to was the right guy
1955 was brittle and maybe open to a mitm for invalid routers.
1957 o Security fixes, minor:
1958 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
1959 Ian Goldberg can prove things about our handshake protocol more
1961 - Make directory authorities generate a separate "guard" flag to
1962 mean "would make a good entry guard". Clients now honor the
1963 is_guard flag rather than looking at is_fast or is_stable.
1964 - Try to list MyFamily elements by key, not by nickname, and warn
1965 if we've not heard of a server.
1966 - Start using RAND_bytes rather than RAND_pseudo_bytes from
1967 OpenSSL. Also, reseed our entropy every hour, not just at
1968 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
1969 - Refuse server descriptors where the fingerprint line doesn't match
1970 the included identity key. Tor doesn't care, but other apps (and
1971 humans) might actually be trusting the fingerprint line.
1972 - We used to kill the circuit when we receive a relay command we
1973 don't recognize. Now we just drop that cell.
1974 - Fix a bug found by Lasse Overlier: when we were making internal
1975 circuits (intended to be cannibalized later for rendezvous and
1976 introduction circuits), we were picking them so that they had
1977 useful exit nodes. There was no need for this, and it actually
1978 aids some statistical attacks.
1979 - Start treating internal circuits and exit circuits separately.
1980 It's important to keep them separate because internal circuits
1981 have their last hops picked like middle hops, rather than like
1982 exit hops. So exiting on them will break the user's expectations.
1983 - Fix a possible way to DoS dirservers.
1984 - When the client asked for a rendezvous port that the hidden
1985 service didn't want to provide, we were sending an IP address
1986 back along with the end cell. Fortunately, it was zero. But stop
1989 o Packaging improvements:
1990 - Implement --with-libevent-dir option to ./configure. Improve
1991 search techniques to find libevent, and use those for openssl too.
1992 - Fix a couple of bugs in OpenSSL detection. Deal better when
1993 there are multiple SSLs installed with different versions.
1994 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
1995 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
1997 - Make unit tests (and other invocations that aren't the real Tor)
1998 run without launching listeners, creating subdirectories, and so on.
1999 - The OS X installer was adding a symlink for tor_resolve but
2000 the binary was called tor-resolve (reported by Thomas Hardly).
2001 - Now we can target arch and OS in rpm builds (contributed by
2002 Phobos). Also make the resulting dist-rpm filename match the
2004 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
2005 if you log to syslog and want something other than LOG_DAEMON.
2006 - Fix the torify (tsocks) config file to not use Tor for localhost
2008 - Start shipping socks-extensions.txt, tor-doc-unix.html,
2009 tor-doc-server.html, and stylesheet.css in the tarball.
2010 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
2011 They are useless now.
2012 - Add Peter Palfrader's contributed check-tor script. It lets you
2013 easily check whether a given server (referenced by nickname)
2014 is reachable by you.
2015 - Add BSD-style contributed startup script "rc.subr" from Peter
2018 o Directory improvements -- new directory protocol:
2019 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
2020 - Authorities and caches publish individual descriptors (by
2021 digest, by fingerprint, by "all", and by "tell me yours").
2022 - Clients don't download or use the old directory anymore. Now they
2023 download network-statuses from the directory authorities, and
2024 fetch individual server descriptors as needed from mirrors.
2025 - Clients don't download descriptors of non-running servers.
2026 - Download descriptors by digest, not by fingerprint. Caches try to
2027 download all listed digests from authorities; clients try to
2028 download "best" digests from caches. This avoids partitioning
2029 and isolating attacks better.
2030 - Only upload a new server descriptor when options change, 18
2031 hours have passed, uptime is reset, or bandwidth changes a lot.
2032 - Directory authorities silently throw away new descriptors that
2033 haven't changed much if the timestamps are similar. We do this to
2034 tolerate older Tor servers that upload a new descriptor every 15
2035 minutes. (It seemed like a good idea at the time.)
2036 - Clients choose directory servers from the network status lists,
2037 not from their internal list of router descriptors. Now they can
2038 go to caches directly rather than needing to go to authorities
2039 to bootstrap the first set of descriptors.
2040 - When picking a random directory, prefer non-authorities if any
2042 - Add a new flag to network-status indicating whether the server
2043 can answer v2 directory requests too.
2044 - Directory mirrors now cache up to 16 unrecognized network-status
2045 docs, so new directory authorities will be cached too.
2046 - Stop parsing, storing, or using running-routers output (but
2047 mirrors still cache and serve it).
2048 - Clients consider a threshold of "versioning" directory authorities
2049 before deciding whether to warn the user that he's obsolete.
2050 - Authorities publish separate sorted lists of recommended versions
2051 for clients and for servers.
2052 - Change DirServers config line to note which dirs are v1 authorities.
2053 - Put nicknames on the DirServer line, so we can refer to them
2054 without requiring all our users to memorize their IP addresses.
2055 - Remove option when getting directory cache to see whether they
2056 support running-routers; they all do now. Replace it with one
2057 to see whether caches support v2 stuff.
2058 - Stop listing down or invalid nodes in the v1 directory. This
2059 reduces its bulk by about 1/3, and reduces load on mirrors.
2060 - Mirrors no longer cache the v1 directory as often.
2061 - If we as a directory mirror don't know of any v1 directory
2062 authorities, then don't try to cache any v1 directories.
2064 o Other directory improvements:
2065 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
2066 fifth authoritative directory servers.
2067 - Directory authorities no longer require an open connection from
2068 a server to consider him "reachable". We need this change because
2069 when we add new directory authorities, old servers won't know not
2071 - Dir authorities now do their own external reachability testing
2072 of each server, and only list as running the ones they found to
2073 be reachable. We also send back warnings to the server's logs if
2074 it uploads a descriptor that we already believe is unreachable.
2075 - Spread the directory authorities' reachability testing over the
2076 entire testing interval, so we don't try to do 500 TLS's at once
2078 - Make the "stable" router flag in network-status be the median of
2079 the uptimes of running valid servers, and make clients pay
2080 attention to the network-status flags. Thus the cutoff adapts
2081 to the stability of the network as a whole, making IRC, IM, etc
2082 connections more reliable.
2083 - Make the v2 dir's "Fast" flag based on relative capacity, just
2084 like "Stable" is based on median uptime. Name everything in the
2085 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
2086 - Retry directory requests if we fail to get an answer we like
2087 from a given dirserver (we were retrying before, but only if
2088 we fail to connect).
2089 - Return a robots.txt on our dirport to discourage google indexing.
2091 o Controller protocol improvements:
2092 - Revised controller protocol (version 1) that uses ascii rather
2093 than binary: tor/doc/control-spec.txt. Add supporting libraries
2094 in python and java and c# so you can use the controller from your
2095 applications without caring how our protocol works.
2096 - Allow the DEBUG controller event to work again. Mark certain log
2097 entries as "don't tell this to controllers", so we avoid cycles.
2098 - New controller function "getinfo accounting", to ask how
2099 many bytes we've used in this time period.
2100 - Add a "resetconf" command so you can set config options like
2101 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
2102 a config option in the torrc with no value, then it clears it
2103 entirely (rather than setting it to its default).
2104 - Add a "getinfo config-file" to tell us where torrc is. Also
2105 expose guard nodes, config options/names.
2106 - Add a "quit" command (when when using the controller manually).
2107 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
2108 stop using any currently-dirty circuits for new streams, so we
2109 don't link new actions to old actions. This also occurs on HUP
2111 - If we would close a stream early (e.g. it asks for a .exit that
2112 we know would refuse it) but the LeaveStreamsUnattached config
2113 option is set by the controller, then don't close it.
2114 - Add a new controller event type "authdir_newdescs" that allows
2115 controllers to get all server descriptors that were uploaded to
2116 a router in its role as directory authority.
2117 - New controller option "getinfo desc/all-recent" to fetch the
2118 latest server descriptor for every router that Tor knows about.
2119 - Fix the controller's "attachstream 0" command to treat conn like
2120 it just connected, doing address remapping, handling .exit and
2121 .onion idioms, and so on. Now we're more uniform in making sure
2122 that the controller hears about new and closing connections.
2123 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
2124 the controller. Also, rotate dns and cpu workers if the controller
2125 changes options that will affect them; and initialize the dns
2126 worker cache tree whether or not we start out as a server.
2127 - Add a new circuit purpose 'controller' to let the controller ask
2128 for a circuit that Tor won't try to use. Extend the "extendcircuit"
2129 controller command to let you specify the purpose if you're starting
2130 a new circuit. Add a new "setcircuitpurpose" controller command to
2131 let you change a circuit's purpose after it's been created.
2132 - Let the controller ask for "getinfo dir/server/foo" so it can ask
2133 directly rather than connecting to the dir port. "getinfo
2134 dir/status/foo" also works, but currently only if your DirPort
2136 - Let the controller tell us about certain router descriptors
2137 that it doesn't want Tor to use in circuits. Implement
2138 "setrouterpurpose" and modify "+postdescriptor" to do this.
2139 - If the controller's *setconf commands fail, collect an error
2140 message in a string and hand it back to the controller -- don't
2141 just tell them to go read their logs.
2143 o Scalability, resource management, and performance:
2144 - Fix a major load balance bug: we were round-robin reading in 16 KB
2145 chunks, and servers with bandwidthrate of 20 KB, while downloading
2146 a 600 KB directory, would starve their other connections. Now we
2147 try to be a bit more fair.
2148 - Be more conservative about whether to advertise our DirPort.
2149 The main change is to not advertise if we're running at capacity
2150 and either a) we could hibernate ever or b) our capacity is low
2151 and we're using a default DirPort.
2152 - We weren't cannibalizing circuits correctly for
2153 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
2154 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
2155 build those from scratch. This should make hidden services faster.
2156 - Predict required circuits better, with an eye toward making hidden
2157 services faster on the service end.
2158 - Compress exit policies even more: look for duplicate lines and
2160 - Generate 18.0.0.0/8 address policy format in descs when we can;
2161 warn when the mask is not reducible to a bit-prefix.
2162 - There used to be two ways to specify your listening ports in a
2163 server descriptor: on the "router" line and with a separate "ports"
2164 line. Remove support for the "ports" line.
2165 - Reduce memory requirements in our structs by changing the order
2166 of fields. Replace balanced trees with hash tables. Inline
2167 bottleneck smartlist functions. Add a "Map from digest to void*"
2168 abstraction so we can do less hex encoding/decoding, and use it
2169 in router_get_by_digest(). Many other CPU and memory improvements.
2170 - Allow tor_gzip_uncompress to extract as much as possible from
2171 truncated compressed data. Try to extract as many
2172 descriptors as possible from truncated http responses (when
2173 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
2174 - Make circ->onionskin a pointer, not a static array. moria2 was using
2175 125000 circuit_t's after it had been up for a few weeks, which
2176 translates to 20+ megs of wasted space.
2177 - The private half of our EDH handshake keys are now chosen out
2178 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
2179 - Stop doing the complex voodoo overkill checking for insecure
2180 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
2181 - Do round-robin writes for TLS of at most 16 kB per write. This
2182 might be more fair on loaded Tor servers.
2183 - Do not use unaligned memory access on alpha, mips, or mipsel.
2184 It *works*, but is very slow, so we treat them as if it doesn't.
2186 o Other bugfixes and improvements:
2187 - Start storing useful information to $DATADIR/state, so we can
2188 remember things across invocations of Tor. Retain unrecognized
2189 lines so we can be forward-compatible, and write a TorVersion line
2190 so we can be backward-compatible.
2191 - If ORPort is set, Address is not explicitly set, and our hostname
2192 resolves to a private IP address, try to use an interface address
2193 if it has a public address. Now Windows machines that think of
2194 themselves as localhost can guess their address.
2195 - Regenerate our local descriptor if it's dirty and we try to use
2196 it locally (e.g. if it changes during reachability detection).
2197 This was causing some Tor servers to keep publishing the same
2198 initial descriptor forever.
2199 - Tor servers with dynamic IP addresses were needing to wait 18
2200 hours before they could start doing reachability testing using
2201 the new IP address and ports. This is because they were using
2202 the internal descriptor to learn what to test, yet they were only
2203 rebuilding the descriptor once they decided they were reachable.
2204 - It turns out we couldn't bootstrap a network since we added
2205 reachability detection in 0.1.0.1-rc. Good thing the Tor network
2206 has never gone down. Add an AssumeReachable config option to let
2207 servers and authorities bootstrap. When we're trying to build a
2208 high-uptime or high-bandwidth circuit but there aren't enough
2209 suitable servers, try being less picky rather than simply failing.
2210 - Newly bootstrapped Tor networks couldn't establish hidden service
2211 circuits until they had nodes with high uptime. Be more tolerant.
2212 - Really busy servers were keeping enough circuits open on stable
2213 connections that they were wrapping around the circuit_id
2214 space. (It's only two bytes.) This exposed a bug where we would
2215 feel free to reuse a circuit_id even if it still exists but has
2216 been marked for close. Try to fix this bug. Some bug remains.
2217 - When we fail to bind or listen on an incoming or outgoing
2218 socket, we now close it before refusing, rather than just
2219 leaking it. (Thanks to Peter Palfrader for finding.)
2220 - Fix a file descriptor leak in start_daemon().
2221 - On Windows, you can't always reopen a port right after you've
2222 closed it. So change retry_listeners() to only close and re-open
2223 ports that have changed.
2224 - Workaround a problem with some http proxies that refuse GET
2225 requests that specify "Content-Length: 0". Reported by Adrian.
2226 - Recover better from TCP connections to Tor servers that are
2227 broken but don't tell you (it happens!); and rotate TLS
2228 connections once a week.
2229 - Fix a scary-looking but apparently harmless bug where circuits
2230 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
2231 servers, and never switch to state CIRCUIT_STATE_OPEN.
2232 - Check for even more Windows version flags when writing the platform
2233 string in server descriptors, and note any we don't recognize.
2234 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
2235 get a better idea of why their circuits failed. Not used yet.
2236 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
2237 We don't use them yet, but maybe one day our DNS resolver will be
2238 able to discover them.
2239 - Let people type "tor --install" as well as "tor -install" when they
2240 want to make it an NT service.
2241 - Looks like we were never delivering deflated (i.e. compressed)
2242 running-routers lists, even when asked. Oops.
2243 - We were leaking some memory every time the client changed IPs.
2244 - Clean up more of the OpenSSL memory when exiting, so we can detect
2245 memory leaks better.
2246 - Never call free() on tor_malloc()d memory. This will help us
2247 use dmalloc to detect memory leaks.
2248 - Some Tor servers process billions of cells per day. These
2249 statistics are now uint64_t's.
2250 - Check [X-]Forwarded-For headers in HTTP requests when generating
2251 log messages. This lets people run dirservers (and caches) behind
2252 Apache but still know which IP addresses are causing warnings.
2253 - Fix minor integer overflow in calculating when we expect to use up
2254 our bandwidth allocation before hibernating.
2255 - Lower the minimum required number of file descriptors to 1000,
2256 so we can have some overhead for Valgrind on Linux, where the
2257 default ulimit -n is 1024.
2258 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
2259 and its existence is confusing some users.
2261 o Config option fixes:
2262 - Add a new config option ExitPolicyRejectPrivate which defaults
2263 to on. Now all exit policies will begin with rejecting private
2264 addresses, unless the server operator explicitly turns it off.
2265 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
2266 - Add new ReachableORAddresses and ReachableDirAddresses options
2267 that understand address policies. FascistFirewall is now a synonym
2268 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
2269 - Start calling it FooListenAddress rather than FooBindAddress,
2270 since few of our users know what it means to bind an address
2272 - If the user gave Tor an odd number of command-line arguments,
2273 we were silently ignoring the last one. Now we complain and fail.
2274 This wins the oldest-bug prize -- this bug has been present since
2275 November 2002, as released in Tor 0.0.0.
2276 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
2277 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
2278 it would silently ignore the 6668.
2279 - If we get a linelist or linelist_s config option from the torrc,
2280 e.g. ExitPolicy, and it has no value, warn and skip rather than
2281 silently resetting it to its default.
2282 - Setconf was appending items to linelists, not clearing them.
2283 - Add MyFamily to torrc.sample in the server section, so operators
2284 will be more likely to learn that it exists.
2285 - Make ContactInfo mandatory for authoritative directory servers.
2286 - MaxConn has been obsolete for a while now. Document the ConnLimit
2287 config option, which is a *minimum* number of file descriptors
2288 that must be available else Tor refuses to start.
2289 - Get rid of IgnoreVersion undocumented config option, and make us
2290 only warn, never exit, when we're running an obsolete version.
2291 - Make MonthlyAccountingStart config option truly obsolete now.
2292 - Correct the man page entry on TrackHostExitsExpire.
2293 - Let directory authorities start even if they don't specify an
2294 Address config option.
2295 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
2296 reflect the updated flags in our v2 dir protocol.
2298 o Config option features:
2299 - Add a new config option FastFirstHopPK (on by default) so clients
2300 do a trivial crypto handshake for their first hop, since TLS has
2301 already taken care of confidentiality and authentication.
2302 - Let the user set ControlListenAddress in the torrc. This can be
2303 dangerous, but there are some cases (like a secured LAN) where it
2305 - New config options to help controllers: FetchServerDescriptors
2306 and FetchHidServDescriptors for whether to fetch server
2307 info and hidserv info or let the controller do it, and
2308 PublishServerDescriptor and PublishHidServDescriptors.
2309 - Also let the controller set the __AllDirActionsPrivate config
2310 option if you want all directory fetches/publishes to happen via
2311 Tor (it assumes your controller bootstraps your circuits).
2312 - Add "HardwareAccel" config option: support for crypto hardware
2313 accelerators via OpenSSL. Off by default, until we find somebody
2314 smart who can test it for us. (It appears to produce seg faults
2315 in at least some cases.)
2316 - New config option "AuthDirRejectUnlisted" for directory authorities
2317 as a panic button: if we get flooded with unusable servers we can
2318 revert to only listing servers in the approved-routers file.
2319 - Directory authorities can now reject/invalidate by key and IP,
2320 with the config options "AuthDirInvalid" and "AuthDirReject", or
2321 by marking a fingerprint as "!reject" or "!invalid" (as its
2322 nickname) in the approved-routers file. This is useful since
2323 currently we automatically list servers as running and usable
2324 even if we know they're jerks.
2325 - Add a new config option TestSocks so people can see whether their
2326 applications are using socks4, socks4a, socks5-with-ip, or
2327 socks5-with-fqdn. This way they don't have to keep mucking
2328 with tcpdump and wondering if something got cached somewhere.
2329 - Add "private:*" as an alias in configuration for policies. Now
2330 you can simplify your exit policy rather than needing to list
2331 every single internal or nonroutable network space.
2332 - Accept "private:*" in routerdesc exit policies; not generated yet
2333 because older Tors do not understand it.
2334 - Add configuration option "V1AuthoritativeDirectory 1" which
2335 moria1, moria2, and tor26 have set.
2336 - Implement an option, VirtualAddrMask, to set which addresses
2337 get handed out in response to mapaddress requests. This works
2338 around a bug in tsocks where 127.0.0.0/8 is never socksified.
2339 - Add a new config option FetchUselessDescriptors, off by default,
2340 for when you plan to run "exitlist" on your client and you want
2341 to know about even the non-running descriptors.
2342 - SocksTimeout: How long do we let a socks connection wait
2343 unattached before we fail it?
2344 - CircuitBuildTimeout: Cull non-open circuits that were born
2345 at least this many seconds ago.
2346 - CircuitIdleTimeout: Cull open clean circuits that were born
2347 at least this many seconds ago.
2348 - New config option SafeSocks to reject all application connections
2349 using unsafe socks protocols. Defaults to off.
2351 o Improved and clearer log messages:
2352 - Reduce clutter in server logs. We're going to try to make
2353 them actually usable now. New config option ProtocolWarnings that
2354 lets you hear about how _other Tors_ are breaking the protocol. Off
2356 - Divide log messages into logging domains. Once we put some sort
2357 of interface on this, it will let people looking at more verbose
2358 log levels specify the topics they want to hear more about.
2359 - Log server fingerprint on startup, so new server operators don't
2360 have to go hunting around their filesystem for it.
2361 - Provide dire warnings to any users who set DirServer manually;
2362 move it out of torrc.sample and into torrc.complete.
2363 - Make the log message less scary when all the dirservers are
2364 temporarily unreachable.
2365 - When tor_socketpair() fails in Windows, give a reasonable
2366 Windows-style errno back.
2367 - Improve tor_gettimeofday() granularity on windows.
2368 - We were printing the number of idle dns workers incorrectly when
2370 - Handle duplicate lines in approved-routers files without warning.
2371 - We were whining about using socks4 or socks5-with-local-lookup
2372 even when it's an IP address in the "virtual" range we designed
2373 exactly for this case.
2374 - Check for named servers when looking them up by nickname;
2375 warn when we're calling a non-named server by its nickname;
2376 don't warn twice about the same name.
2377 - Downgrade the dirserver log messages when whining about
2379 - Correct "your server is reachable" log entries to indicate that
2380 it was self-testing that told us so.
2381 - If we're trying to be a Tor server and running Windows 95/98/ME
2382 as a server, explain that we'll likely crash.
2383 - Provide a more useful warn message when our onion queue gets full:
2384 the CPU is too slow or the exit policy is too liberal.
2385 - Don't warn when we receive a 503 from a dirserver/cache -- this
2386 will pave the way for them being able to refuse if they're busy.
2387 - When we fail to bind a listener, try to provide a more useful
2388 log message: e.g., "Is Tor already running?"
2389 - Only start testing reachability once we've established a
2390 circuit. This will make startup on dir authorities less noisy.
2391 - Don't try to upload hidden service descriptors until we have
2392 established a circuit.
2393 - Tor didn't warn when it failed to open a log file.
2394 - Warn when listening on a public address for socks. We suspect a
2395 lot of people are setting themselves up as open socks proxies,
2396 and they have no idea that jerks on the Internet are using them,
2397 since they simply proxy the traffic into the Tor network.
2398 - Give a useful message when people run Tor as the wrong user,
2399 rather than telling them to start chowning random directories.
2400 - Fix a harmless bug that was causing Tor servers to log
2401 "Got an end because of misc error, but we're not an AP. Closing."
2402 - Fix wrong log message when you add a "HiddenServiceNodes" config
2403 line without any HiddenServiceDir line (reported by Chris Thomas).
2404 - Directory authorities now stop whining so loudly about bad
2405 descriptors that they fetch from other dirservers. So when there's
2406 a log complaint, it's for sure from a freshly uploaded descriptor.
2407 - When logging via syslog, include the pid whenever we provide
2408 a log entry. Suggested by Todd Fries.
2409 - When we're shutting down and we do something like try to post a
2410 server descriptor or rendezvous descriptor, don't complain that
2411 we seem to be unreachable. Of course we are, we're shutting down.
2412 - Change log line for unreachability to explicitly suggest /etc/hosts
2413 as the culprit. Also make it clearer what IP address and ports we're
2414 testing for reachability.
2415 - Put quotes around user-supplied strings when logging so users are
2416 more likely to realize if they add bad characters (like quotes)
2418 - NT service patch from Matt Edman to improve error messages on Win32.
2421 Changes in version 0.1.0.17 - 2006-02-17
2422 o Crash bugfixes on 0.1.0.x:
2423 - When servers with a non-zero DirPort came out of hibernation,
2424 sometimes they would trigger an assert.
2426 o Other important bugfixes:
2427 - On platforms that don't have getrlimit (like Windows), we were
2428 artificially constraining ourselves to a max of 1024
2429 connections. Now just assume that we can handle as many as 15000
2430 connections. Hopefully this won't cause other problems.
2432 o Backported features:
2433 - When we're a server, a client asks for an old-style directory,
2434 and our write bucket is empty, don't give it to him. This way
2435 small servers can continue to serve the directory *sometimes*,
2436 without getting overloaded.
2437 - Whenever you get a 503 in response to a directory fetch, try
2438 once more. This will become important once servers start sending
2439 503's whenever they feel busy.
2440 - Fetch a new directory every 120 minutes, not every 40 minutes.
2441 Now that we have hundreds of thousands of users running the old
2442 directory algorithm, it's starting to hurt a lot.
2443 - Bump up the period for forcing a hidden service descriptor upload
2444 from 20 minutes to 1 hour.
2447 Changes in version 0.1.0.16 - 2006-01-02
2448 o Crash bugfixes on 0.1.0.x:
2449 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
2450 corrupting the heap, losing FDs, or crashing when we need to resize
2451 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
2452 - It turns out sparc64 platforms crash on unaligned memory access
2453 too -- so detect and avoid this.
2454 - Handle truncated compressed data correctly (by detecting it and
2456 - Fix possible-but-unlikely free(NULL) in control.c.
2457 - When we were closing connections, there was a rare case that
2458 stomped on memory, triggering seg faults and asserts.
2459 - Avoid potential infinite recursion when building a descriptor. (We
2460 don't know that it ever happened, but better to fix it anyway.)
2461 - We were neglecting to unlink marked circuits from soon-to-close OR
2462 connections, which caused some rare scribbling on freed memory.
2463 - Fix a memory stomping race bug when closing the joining point of two
2464 rendezvous circuits.
2465 - Fix an assert in time parsing found by Steven Murdoch.
2467 o Other bugfixes on 0.1.0.x:
2468 - When we're doing reachability testing, provide more useful log
2469 messages so the operator knows what to expect.
2470 - Do not check whether DirPort is reachable when we are suppressing
2471 advertising it because of hibernation.
2472 - When building with -static or on Solaris, we sometimes needed -ldl.
2473 - One of the dirservers (tor26) changed its IP address.
2474 - When we're deciding whether a stream has enough circuits around
2475 that can handle it, count the freshly dirty ones and not the ones
2476 that are so dirty they won't be able to handle it.
2477 - When we're expiring old circuits, we had a logic error that caused
2478 us to close new rendezvous circuits rather than old ones.
2479 - Give a more helpful log message when you try to change ORPort via
2480 the controller: you should upgrade Tor if you want that to work.
2481 - We were failing to parse Tor versions that start with "Tor ".
2482 - Tolerate faulty streams better: when a stream fails for reason
2483 exitpolicy, stop assuming that the router is lying about his exit
2484 policy. When a stream fails for reason misc, allow it to retry just
2485 as if it was resolvefailed. When a stream has failed three times,
2486 reset its failure count so we can try again and get all three tries.
2489 Changes in version 0.1.0.15 - 2005-09-23
2490 o Bugfixes on 0.1.0.x:
2491 - Reject ports 465 and 587 (spam targets) in default exit policy.
2492 - Don't crash when we don't have any spare file descriptors and we
2493 try to spawn a dns or cpu worker.
2494 - Get rid of IgnoreVersion undocumented config option, and make us
2495 only warn, never exit, when we're running an obsolete version.
2496 - Don't try to print a null string when your server finds itself to
2497 be unreachable and the Address config option is empty.
2498 - Make the numbers in read-history and write-history into uint64s,
2499 so they don't overflow and publish negatives in the descriptor.
2500 - Fix a minor memory leak in smartlist_string_remove().
2501 - We were only allowing ourselves to upload a server descriptor at
2502 most every 20 minutes, even if it changed earlier than that.
2503 - Clean up log entries that pointed to old URLs.
2506 Changes in version 0.1.0.14 - 2005-08-08
2507 o Bugfixes on 0.1.0.x:
2508 - Fix the other half of the bug with crypto handshakes
2510 - Fix an assert trigger if you send a 'signal term' via the
2511 controller when it's listening for 'event info' messages.
2514 Changes in version 0.1.0.13 - 2005-08-04
2515 o Bugfixes on 0.1.0.x:
2516 - Fix a critical bug in the security of our crypto handshakes.
2517 - Fix a size_t underflow in smartlist_join_strings2() that made
2518 it do bad things when you hand it an empty smartlist.
2519 - Fix Windows installer to ship Tor license (thanks to Aphex for
2520 pointing out this oversight) and put a link to the doc directory
2522 - Explicitly set no-unaligned-access for sparc: it turns out the
2523 new gcc's let you compile broken code, but that doesn't make it
2527 Changes in version 0.1.0.12 - 2005-07-18
2528 o New directory servers:
2529 - tor26 has changed IP address.
2531 o Bugfixes on 0.1.0.x:
2532 - Fix a possible double-free in tor_gzip_uncompress().
2533 - When --disable-threads is set, do not search for or link against
2535 - Don't trigger an assert if an authoritative directory server
2536 claims its dirport is 0.
2537 - Fix bug with removing Tor as an NT service: some people were
2538 getting "The service did not return an error." Thanks to Matt
2542 Changes in version 0.1.0.11 - 2005-06-30
2543 o Bugfixes on 0.1.0.x:
2544 - Fix major security bug: servers were disregarding their
2545 exit policies if clients behaved unexpectedly.
2546 - Make OS X init script check for missing argument, so we don't
2547 confuse users who invoke it incorrectly.
2548 - Fix a seg fault in "tor --hash-password foo".
2549 - The MAPADDRESS control command was broken.
2552 Changes in version 0.1.0.10 - 2005-06-14
2554 - Make NT services work and start on startup on Win32 (based on
2555 patch by Matt Edman). See the FAQ entry for details.
2556 - Make 'platform' string in descriptor more accurate for Win32
2557 servers, so it's not just "unknown platform".
2558 - REUSEADDR on normal platforms means you can rebind to the port
2559 right after somebody else has let it go. But REUSEADDR on Win32
2560 means you can bind to the port _even when somebody else already
2561 has it bound_! So, don't do that on Win32.
2562 - Clean up the log messages when starting on Win32 with no config
2564 - Allow seeding the RNG on Win32 even when you're not running as
2565 Administrator. If seeding the RNG on Win32 fails, quit.
2567 o Assert / crash bugs:
2568 - Refuse relay cells that claim to have a length larger than the
2569 maximum allowed. This prevents a potential attack that could read
2570 arbitrary memory (e.g. keys) from an exit server's process
2572 - If unofficial Tor clients connect and send weird TLS certs, our
2573 Tor server triggers an assert. Stop asserting, and start handling
2574 TLS errors better in other situations too.
2575 - Fix a race condition that can trigger an assert when we have a
2576 pending create cell and an OR connection attempt fails.
2579 - Use pthreads for worker processes rather than forking. This was
2580 forced because when we forked, we ended up wasting a lot of
2581 duplicate ram over time.
2582 - Also switch to foo_r versions of some library calls to allow
2583 reentry and threadsafeness.
2584 - Implement --disable-threads configure option. Disable threads on
2585 netbsd and openbsd by default, because they have no reentrant
2586 resolver functions (!), and on solaris since it has other
2588 - Fix possible bug on threading platforms (e.g. win32) which was
2589 leaking a file descriptor whenever a cpuworker or dnsworker died.
2590 - Fix a minor memory leak when somebody establishes an introduction
2591 point at your Tor server.
2592 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
2594 - Add ./configure --with-dmalloc option, to track memory leaks.
2595 - And try to free all memory on closing, so we can detect what
2598 o Protocol correctness:
2599 - When we've connected to an OR and handshaked but didn't like
2600 the result, we were closing the conn without sending destroy
2601 cells back for pending circuits. Now send those destroys.
2602 - Start sending 'truncated' cells back rather than destroy cells
2603 if the circuit closes in front of you. This means we won't have
2604 to abandon partially built circuits.
2605 - Handle changed router status correctly when dirserver reloads
2606 fingerprint file. We used to be dropping all unverified descriptors
2607 right then. The bug was hidden because we would immediately
2608 fetch a directory from another dirserver, which would include the
2609 descriptors we just dropped.
2610 - Revise tor-spec to add more/better stream end reasons.
2611 - Revise all calls to connection_edge_end to avoid sending 'misc',
2612 and to take errno into account where possible.
2613 - Client now retries when streams end early for 'hibernating' or
2614 'resource limit' reasons, rather than failing them.
2615 - Try to be more zealous about calling connection_edge_end when
2616 things go bad with edge conns in connection.c.
2618 o Robustness improvements:
2619 - Better handling for heterogeneous / unreliable nodes:
2620 - Annotate circuits with whether they aim to contain high uptime
2621 nodes and/or high capacity nodes. When building circuits, choose
2623 - This means that every single node in an intro rend circuit,
2624 not just the last one, will have a minimum uptime.
2625 - New config option LongLivedPorts to indicate application streams
2626 that will want high uptime circuits.
2627 - Servers reset uptime when a dir fetch entirely fails. This
2628 hopefully reflects stability of the server's network connectivity.
2629 - If somebody starts his tor server in Jan 2004 and then fixes his
2630 clock, don't make his published uptime be a year.
2631 - Reset published uptime when we wake up from hibernation.
2632 - Introduce a notion of 'internal' circs, which are chosen without
2633 regard to the exit policy of the last hop. Intro and rendezvous
2634 circs must be internal circs, to avoid leaking information. Resolve
2635 and connect streams can use internal circs if they want.
2636 - New circuit pooling algorithm: keep track of what destination ports
2637 we've used recently (start out assuming we'll want to use 80), and
2638 make sure to have enough circs around to satisfy these ports. Also
2639 make sure to have 2 internal circs around if we've required internal
2640 circs lately (and with high uptime if we've seen that lately too).
2641 - Turn addr_policy_compare from a tristate to a quadstate; this should
2642 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
2643 for google.com" problem.
2644 - When a client asks us for a dir mirror and we don't have one,
2645 launch an attempt to get a fresh one.
2646 - First cut at support for "create-fast" cells. Clients can use
2647 these when extending to their first hop, since the TLS already
2648 provides forward secrecy and authentication. Not enabled on
2651 o Reachability testing.
2652 - Your Tor server will automatically try to see if its ORPort and
2653 DirPort are reachable from the outside, and it won't upload its
2654 descriptor until it decides at least ORPort is reachable (when
2655 DirPort is not yet found reachable, publish it as zero).
2656 - When building testing circs for ORPort testing, use only
2657 high-bandwidth nodes, so fewer circuits fail.
2658 - Notice when our IP changes, and reset stats/uptime/reachability.
2659 - Authdirservers don't do ORPort reachability detection, since
2660 they're in clique mode, so it will be rare to find a server not
2661 already connected to them.
2662 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
2666 - Now we allow two unverified servers with the same nickname
2667 but different keys. But if a nickname is verified, only that
2668 nickname+key are allowed.
2669 - If you're an authdirserver connecting to an address:port,
2670 and it's not the OR you were expecting, forget about that
2671 descriptor. If he *was* the one you were expecting, then forget
2672 about all other descriptors for that address:port.
2673 - Allow servers to publish descriptors from 12 hours in the future.
2674 Corollary: only whine about clock skew from the dirserver if
2675 he's a trusted dirserver (since now even verified servers could
2676 have quite wrong clocks).
2677 - Require servers that use the default dirservers to have public IP
2678 addresses. We have too many servers that are configured with private
2679 IPs and their admins never notice the log entries complaining that
2680 their descriptors are being rejected.
2682 o Efficiency improvements:
2683 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
2684 and /dev/poll), and hopefully work better on Windows too.
2685 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
2686 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
2687 - Find libevent even if it's hiding in /usr/local/ and your
2688 CFLAGS and LDFLAGS don't tell you to look there.
2689 - Be able to link with libevent as a shared library (the default
2690 after 1.0d), even if it's hiding in /usr/local/lib and even
2691 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
2692 assuming you're running gcc. Otherwise fail and give a useful
2694 - Switch to a new buffer management algorithm, which tries to avoid
2695 reallocing and copying quite as much. In first tests it looks like
2696 it uses *more* memory on average, but less cpu.
2697 - Switch our internal buffers implementation to use a ring buffer,
2698 to hopefully improve performance for fast servers a lot.
2699 - Reenable the part of the code that tries to flush as soon as an
2700 OR outbuf has a full TLS record available. Perhaps this will make
2701 OR outbufs not grow as huge except in rare cases, thus saving lots
2702 of CPU time plus memory.
2703 - Improve performance for dirservers: stop re-parsing the whole
2704 directory every time you regenerate it.
2705 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
2706 it much faster to look up a circuit for each relay cell.
2707 - Remove most calls to assert_all_pending_dns_resolves_ok(),
2708 since they're eating our cpu on exit nodes.
2709 - Stop wasting time doing a case insensitive comparison for every
2710 dns name every time we do any lookup. Canonicalize the names to
2711 lowercase when you first see them.
2714 - Handle unavailable hidden services better. Handle slow or busy
2715 hidden services better.
2716 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
2717 circ as necessary, if there are any completed ones lying around
2718 when we try to launch one.
2719 - Make hidden services try to establish a rendezvous for 30 seconds
2720 after fetching the descriptor, rather than for n (where n=3)
2721 attempts to build a circuit.
2722 - Adjust maximum skew and age for rendezvous descriptors: let skew
2723 be 48 hours rather than 90 minutes.
2724 - Reject malformed .onion addresses rather then passing them on as
2725 normal web requests.
2728 - More Tor controller support. See
2729 http://tor.eff.org/doc/control-spec.txt for all the new features,
2730 including signals to emulate unix signals from any platform;
2731 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
2732 closestream; closecircuit; etc.
2733 - Encode hashed controller passwords in hex instead of base64,
2734 to make it easier to write controllers.
2735 - Revise control spec and implementation to allow all log messages to
2736 be sent to controller with their severities intact (suggested by
2737 Matt Edman). Disable debug-level logs while delivering a debug-level
2738 log to the controller, to prevent loop. Update TorControl to handle
2739 new log event types.
2741 o New config options/defaults:
2742 - Begin scrubbing sensitive strings from logs by default. Turn off
2743 the config option SafeLogging if you need to do debugging.
2744 - New exit policy: accept most low-numbered ports, rather than
2745 rejecting most low-numbered ports.
2746 - Put a note in the torrc about abuse potential with the default
2748 - Add support for CONNECTing through https proxies, with "HttpsProxy"
2750 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
2751 based on patch from Adam Langley (basic auth only).
2752 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
2753 the fast servers that have been joining lately. (Clients are now
2754 willing to load balance over up to 2 MB of advertised bandwidth
2756 - New config option MaxAdvertisedBandwidth which lets you advertise
2757 a low bandwidthrate (to not attract as many circuits) while still
2758 allowing a higher bandwidthrate in reality.
2759 - Require BandwidthRate to be at least 20kB/s for servers.
2760 - Add a NoPublish config option, so you can be a server (e.g. for
2761 testing running Tor servers in other Tor networks) without
2762 publishing your descriptor to the primary dirservers.
2763 - Add a new AddressMap config directive to rewrite incoming socks
2764 addresses. This lets you, for example, declare an implicit
2765 required exit node for certain sites.
2766 - Add a new TrackHostExits config directive to trigger addressmaps
2767 for certain incoming socks addresses -- for sites that break when
2768 your exit keeps changing (based on patch from Mike Perry).
2769 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
2770 which describes how often we retry making new circuits if current
2771 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
2772 how long we're willing to make use of an already-dirty circuit.
2773 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
2774 a config option "ShutdownWaitLength" (when using kill -INT on
2776 - Fix an edge case in parsing config options: if they say "--"
2777 on the commandline, it's not a config option (thanks weasel).
2778 - New config option DirAllowPrivateAddresses for authdirservers.
2779 Now by default they refuse router descriptors that have non-IP or
2780 private-IP addresses.
2781 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
2782 smart" default value: low for servers and high for clients.
2783 - Some people were putting "Address " in their torrc, and they had
2784 a buggy resolver that resolved " " to 0.0.0.0. Oops.
2785 - If DataDir is ~/.tor, and that expands to /.tor, then default to
2786 LOCALSTATEDIR/tor instead.
2787 - Implement --verify-config command-line option to check if your torrc
2788 is valid without actually launching Tor.
2790 o Logging improvements:
2791 - When dirservers refuse a server descriptor, we now log its
2792 contactinfo, platform, and the poster's IP address.
2793 - Only warn once per nickname from add_nickname_list_to_smartlist()
2794 per failure, so an entrynode or exitnode choice that's down won't
2796 - When we're connecting to an OR and he's got a different nickname/key
2797 than we were expecting, only complain loudly if we're an OP or a
2798 dirserver. Complaining loudly to the OR admins just confuses them.
2799 - Whine at you if you're a server and you don't set your contactinfo.
2800 - Warn when exit policy implicitly allows local addresses.
2801 - Give a better warning when some other server advertises an
2802 ORPort that is actually an apache running ssl.
2803 - If we get an incredibly skewed timestamp from a dirserver mirror
2804 that isn't a verified OR, don't warn -- it's probably him that's
2806 - When a dirserver causes you to give a warn, mention which dirserver
2808 - Initialize libevent later in the startup process, so the logs are
2809 already established by the time we start logging libevent warns.
2810 - Use correct errno on win32 if libevent fails.
2811 - Check and warn about known-bad/slow libevent versions.
2812 - Stop warning about sigpipes in the logs. We're going to
2813 pretend that getting these occassionally is normal and fine.
2815 o New contrib scripts:
2816 - New experimental script tor/contrib/exitlist: a simple python
2817 script to parse directories and find Tor nodes that exit to listed
2819 - New experimental script tor/contrib/ExerciseServer.py (needs more
2820 work) that uses the controller interface to build circuits and
2821 fetch pages over them. This will help us bootstrap servers that
2822 have lots of capacity but haven't noticed it yet.
2823 - New experimental script tor/contrib/PathDemo.py (needs more work)
2824 that uses the controller interface to let you choose whole paths
2826 "<hostname>.<path,separated by dots>.<length of path>.path"
2827 - New contributed script "privoxy-tor-toggle" to toggle whether
2828 Privoxy uses Tor. Seems to be configured for Debian by default.
2829 - Have torctl.in/tor.sh.in check for location of su binary (needed
2833 - chdir() to your datadirectory at the *end* of the daemonize process,
2834 not the beginning. This was a problem because the first time you
2835 run tor, if your datadir isn't there, and you have runasdaemon set
2836 to 1, it will try to chdir to it before it tries to create it. Oops.
2837 - Fix several double-mark-for-close bugs, e.g. where we were finding
2838 a conn for a cell even if that conn is already marked for close.
2839 - Stop most cases of hanging up on a socks connection without sending
2841 - Fix a bug in the RPM package: set home directory for _tor to
2842 something more reasonable when first installing.
2843 - Stop putting nodename in the Platform string in server descriptors.
2844 It doesn't actually help, and it is confusing/upsetting some people.
2845 - When using preferred entry or exit nodes, ignore whether the
2846 circuit wants uptime or capacity. They asked for the nodes, they
2848 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
2849 artificially capped at 500kB.
2850 - Cache local dns resolves correctly even when they're .exit
2852 - If we're hibernating and we get a SIGINT, exit immediately.
2853 - tor-resolve requests were ignoring .exit if there was a working circuit
2854 they could use instead.
2855 - Pay more attention to the ClientOnly config option.
2856 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
2857 installer screens; and don't put stuff into StartupItems unless
2858 the user asks you to.
2861 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
2862 rather than just rejecting it.
2863 - If our clock jumps forward by 100 seconds or more, assume something
2864 has gone wrong with our network and abandon all not-yet-used circs.
2865 - When an application is using socks5, give him the whole variety of
2866 potential socks5 responses (connect refused, host unreachable, etc),
2867 rather than just "success" or "failure".
2868 - A more sane version numbering system. See
2869 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
2870 - Change version parsing logic: a version is "obsolete" if it is not
2871 recommended and (1) there is a newer recommended version in the
2872 same series, or (2) there are no recommended versions in the same
2873 series, but there are some recommended versions in a newer series.
2874 A version is "new" if it is newer than any recommended version in
2876 - Report HTTP reasons to client when getting a response from directory
2877 servers -- so you can actually know what went wrong.
2878 - Reject odd-looking addresses at the client (e.g. addresses that
2879 contain a colon), rather than having the server drop them because
2881 - Stop publishing socksport in the directory, since it's not
2882 actually meant to be public. For compatibility, publish a 0 there
2884 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
2885 cookies to disk and doesn't log each web request to disk. (Thanks
2886 to Brett Carrington for pointing this out.)
2887 - Add OSX uninstall instructions. An actual uninstall script will
2889 - Add "opt hibernating 1" to server descriptor to make it clearer
2890 whether the server is hibernating.
2893 Changes in version 0.0.9.10 - 2005-06-16
2894 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
2895 - Refuse relay cells that claim to have a length larger than the
2896 maximum allowed. This prevents a potential attack that could read
2897 arbitrary memory (e.g. keys) from an exit server's process
2901 Changes in version 0.0.9.9 - 2005-04-23
2902 o Bugfixes on 0.0.9.x:
2903 - If unofficial Tor clients connect and send weird TLS certs, our
2904 Tor server triggers an assert. This release contains a minimal
2905 backport from the broader fix that we put into 0.1.0.4-rc.
2908 Changes in version 0.0.9.8 - 2005-04-07
2909 o Bugfixes on 0.0.9.x:
2910 - We have a bug that I haven't found yet. Sometimes, very rarely,
2911 cpuworkers get stuck in the 'busy' state, even though the cpuworker
2912 thinks of itself as idle. This meant that no new circuits ever got
2913 established. Here's a workaround to kill any cpuworker that's been
2914 busy for more than 100 seconds.
2917 Changes in version 0.0.9.7 - 2005-04-01
2918 o Bugfixes on 0.0.9.x:
2919 - Fix another race crash bug (thanks to Glenn Fink for reporting).
2920 - Compare identity to identity, not to nickname, when extending to
2921 a router not already in the directory. This was preventing us from
2922 extending to unknown routers. Oops.
2923 - Make sure to create OS X Tor user in <500 range, so we aren't
2924 creating actual system users.
2925 - Note where connection-that-hasn't-sent-end was marked, and fix
2926 a few really loud instances of this harmless bug (it's fixed more
2930 Changes in version 0.0.9.6 - 2005-03-24
2931 o Bugfixes on 0.0.9.x (crashes and asserts):
2932 - Add new end stream reasons to maintainance branch. Fix bug where
2933 reason (8) could trigger an assert. Prevent bug from recurring.
2934 - Apparently win32 stat wants paths to not end with a slash.
2935 - Fix assert triggers in assert_cpath_layer_ok(), where we were
2936 blowing away the circuit that conn->cpath_layer points to, then
2937 checking to see if the circ is well-formed. Backport check to make
2938 sure we dont use the cpath on a closed connection.
2939 - Prevent circuit_resume_edge_reading_helper() from trying to package
2940 inbufs for marked-for-close streams.
2941 - Don't crash on hup if your options->address has become unresolvable.
2942 - Some systems (like OS X) sometimes accept() a connection and tell
2943 you the remote host is 0.0.0.0:0. If this happens, due to some
2944 other mis-features, we get confused; so refuse the conn for now.
2946 o Bugfixes on 0.0.9.x (other):
2947 - Fix harmless but scary "Unrecognized content encoding" warn message.
2948 - Add new stream error reason: TORPROTOCOL reason means "you are not
2949 speaking a version of Tor I understand; say bye-bye to your stream."
2950 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
2951 into the future, now that we are more tolerant of skew. This
2952 resolves a bug where a Tor server would refuse to cache a directory
2953 because all the directories it gets are too far in the future;
2954 yet the Tor server never logs any complaints about clock skew.
2955 - Mac packaging magic: make man pages useable, and do not overwrite
2956 existing torrc files.
2957 - Make OS X log happily to /var/log/tor/tor.log
2960 Changes in version 0.0.9.5 - 2005-02-22
2961 o Bugfixes on 0.0.9.x:
2962 - Fix an assert race at exit nodes when resolve requests fail.
2963 - Stop picking unverified dir mirrors--it only leads to misery.
2964 - Patch from Matt Edman to make NT services work better. Service
2965 support is still not compiled into the executable by default.
2966 - Patch from Dmitri Bely so the Tor service runs better under
2967 the win32 SYSTEM account.
2968 - Make tor-resolve actually work (?) on Win32.
2969 - Fix a sign bug when getrlimit claims to have 4+ billion
2970 file descriptors available.
2971 - Stop refusing to start when bandwidthburst == bandwidthrate.
2972 - When create cells have been on the onion queue more than five
2973 seconds, just send back a destroy and take them off the list.
2976 Changes in version 0.0.9.4 - 2005-02-03
2977 o Bugfixes on 0.0.9:
2978 - Fix an assert bug that took down most of our servers: when
2979 a server claims to have 1 GB of bandwidthburst, don't
2981 - Don't crash as badly if we have spawned the max allowed number
2982 of dnsworkers, or we're out of file descriptors.
2983 - Block more file-sharing ports in the default exit policy.
2984 - MaxConn is now automatically set to the hard limit of max
2985 file descriptors we're allowed (ulimit -n), minus a few for
2987 - Give a clearer message when servers need to raise their
2988 ulimit -n when they start running out of file descriptors.
2989 - SGI Compatibility patches from Jan Schaumann.
2990 - Tolerate a corrupt cached directory better.
2991 - When a dirserver hasn't approved your server, list which one.
2992 - Go into soft hibernation after 95% of the bandwidth is used,
2993 not 99%. This is especially important for daily hibernators who
2994 have a small accounting max. Hopefully it will result in fewer
2995 cut connections when the hard hibernation starts.
2996 - Load-balance better when using servers that claim more than
2997 800kB/s of capacity.
2998 - Make NT services work (experimental, only used if compiled in).
3001 Changes in version 0.0.9.3 - 2005-01-21
3002 o Bugfixes on 0.0.9:
3003 - Backport the cpu use fixes from main branch, so busy servers won't
3004 need as much processor time.
3005 - Work better when we go offline and then come back, or when we
3006 run Tor at boot before the network is up. We do this by
3007 optimistically trying to fetch a new directory whenever an
3008 application request comes in and we think we're offline -- the
3009 human is hopefully a good measure of when the network is back.
3010 - Backport some minimal hidserv bugfixes: keep rend circuits open as
3011 long as you keep using them; actually publish hidserv descriptors
3012 shortly after they change, rather than waiting 20-40 minutes.
3013 - Enable Mac startup script by default.
3014 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
3015 - When you update AllowUnverifiedNodes or FirewallPorts via the
3016 controller's setconf feature, we were always appending, never
3018 - When you update HiddenServiceDir via setconf, it was screwing up
3019 the order of reading the lines, making it fail.
3020 - Do not rewrite a cached directory back to the cache; otherwise we
3021 will think it is recent and not fetch a newer one on startup.
3022 - Workaround for webservers that lie about Content-Encoding: Tor
3023 now tries to autodetect compressed directories and compression
3024 itself. This lets us Proxypass dir fetches through apache.
3027 Changes in version 0.0.9.2 - 2005-01-04
3028 o Bugfixes on 0.0.9 (crashes and asserts):
3029 - Fix an assert on startup when the disk is full and you're logging
3031 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
3032 style address, then we'd crash.
3033 - Fix an assert trigger when the running-routers string we get from
3034 a dirserver is broken.
3035 - Make worker threads start and run on win32. Now win32 servers
3037 - Bandaid (not actually fix, but now it doesn't crash) an assert
3038 where the dns worker dies mysteriously and the main Tor process
3039 doesn't remember anything about the address it was resolving.
3041 o Bugfixes on 0.0.9 (Win32):
3042 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
3043 name out of the warning/assert messages.
3044 - Fix a superficial "unhandled error on read" bug on win32.
3045 - The win32 installer no longer requires a click-through for our
3046 license, since our Free Software license grants rights but does not
3048 - Win32: When connecting to a dirserver fails, try another one
3049 immediately. (This was already working for non-win32 Tors.)
3050 - Stop trying to parse $HOME on win32 when hunting for default
3052 - Make tor-resolve.c work on win32 by calling network_init().
3054 o Bugfixes on 0.0.9 (other):
3055 - Make 0.0.9.x build on Solaris again.
3056 - Due to a fencepost error, we were blowing away the \n when reporting
3057 confvalue items in the controller. So asking for multiple config
3058 values at once couldn't work.
3059 - When listing circuits that are pending on an opening OR connection,
3060 if we're an OR we were listing circuits that *end* at us as
3061 being pending on every listener, dns/cpu worker, etc. Stop that.
3062 - Dirservers were failing to create 'running-routers' or 'directory'
3063 strings if we had more than some threshold of routers. Fix them so
3064 they can handle any number of routers.
3065 - Fix a superficial "Duplicate mark for close" bug.
3066 - Stop checking for clock skew for OR connections, even for servers.
3067 - Fix a fencepost error that was chopping off the last letter of any
3068 nickname that is the maximum allowed nickname length.
3069 - Update URLs in log messages so they point to the new website.
3070 - Fix a potential problem in mangling server private keys while
3071 writing to disk (not triggered yet, as far as we know).
3072 - Include the licenses for other free software we include in Tor,
3073 now that we're shipping binary distributions more regularly.
3076 Changes in version 0.0.9.1 - 2004-12-15
3077 o Bugfixes on 0.0.9:
3078 - Make hibernation actually work.
3079 - Make HashedControlPassword config option work.
3080 - When we're reporting event circuit status to a controller,
3081 don't use the stream status code.
3084 Changes in version 0.0.9 - 2004-12-12
3085 o Bugfixes on 0.0.8.1 (Crashes and asserts):
3086 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
3087 write() call will fail and we handle it there.
3088 - When we run out of disk space, or other log writing error, don't
3089 crash. Just stop logging to that log and continue.
3090 - Fix isspace() and friends so they still make Solaris happy
3091 but also so they don't trigger asserts on win32.
3092 - Fix assert failure on malformed socks4a requests.
3093 - Fix an assert bug where a hidden service provider would fail if
3094 the first hop of his rendezvous circuit was down.
3095 - Better handling of size_t vs int, so we're more robust on 64
3098 o Bugfixes on 0.0.8.1 (Win32):
3099 - Make windows sockets actually non-blocking (oops), and handle
3100 win32 socket errors better.
3101 - Fix parse_iso_time on platforms without strptime (eg win32).
3102 - win32: when being multithreaded, leave parent fdarray open.
3103 - Better handling of winsock includes on non-MSV win32 compilers.
3104 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
3106 - Make unit tests work on win32.
3108 o Bugfixes on 0.0.8.1 (Path selection and streams):
3109 - Calculate timeout for waiting for a connected cell from the time
3110 we sent the begin cell, not from the time the stream started. If
3111 it took a long time to establish the circuit, we would time out
3112 right after sending the begin cell.
3113 - Fix router_compare_addr_to_addr_policy: it was not treating a port
3114 of * as always matching, so we were picking reject *:* nodes as
3115 exit nodes too. Oops.
3116 - When read() failed on a stream, we would close it without sending
3117 back an end. So 'connection refused' would simply be ignored and
3118 the user would get no response.
3119 - Stop a sigpipe: when an 'end' cell races with eof from the app,
3120 we shouldn't hold-open-until-flush if the eof arrived first.
3121 - Let resolve conns retry/expire also, rather than sticking around
3123 - Fix more dns related bugs: send back resolve_failed and end cells
3124 more reliably when the resolve fails, rather than closing the
3125 circuit and then trying to send the cell. Also attach dummy resolve
3126 connections to a circuit *before* calling dns_resolve(), to fix
3127 a bug where cached answers would never be sent in RESOLVED cells.
3129 o Bugfixes on 0.0.8.1 (Circuits):
3130 - Finally fix a bug that's been plaguing us for a year:
3131 With high load, circuit package window was reaching 0. Whenever
3132 we got a circuit-level sendme, we were reading a lot on each
3133 socket, but only writing out a bit. So we would eventually reach
3134 eof. This would be noticed and acted on even when there were still
3135 bytes sitting in the inbuf.
3136 - Use identity comparison, not nickname comparison, to choose which
3137 half of circuit-ID-space each side gets to use. This is needed
3138 because sometimes we think of a router as a nickname, and sometimes
3139 as a hex ID, and we can't predict what the other side will do.
3141 o Bugfixes on 0.0.8.1 (Other):
3142 - Fix a whole slew of memory leaks.
3143 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
3144 - If we are using select, make sure we stay within FD_SETSIZE.
3145 - When poll() is interrupted, we shouldn't believe the revents values.
3146 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
3147 and smartlist_len, which are two major profiling offenders.
3148 - If do_hup fails, actually notice.
3149 - Flush the log file descriptor after we print "Tor opening log file",
3150 so we don't see those messages days later.
3151 - Hidden service operators now correctly handle version 1 style
3152 INTRODUCE1 cells (nobody generates them still, so not a critical
3154 - Handle more errnos from accept() without closing the listener.
3155 Some OpenBSD machines were closing their listeners because
3156 they ran out of file descriptors.
3157 - Some people had wrapped their tor client/server in a script
3158 that would restart it whenever it died. This did not play well
3159 with our "shut down if your version is obsolete" code. Now people
3160 don't fetch a new directory if their local cached version is
3162 - Make our autogen.sh work on ksh as well as bash.
3163 - Better torrc example lines for dirbindaddress and orbindaddress.
3164 - Improved bounds checking on parsed ints (e.g. config options and
3165 the ones we find in directories.)
3166 - Stop using separate defaults for no-config-file and
3167 empty-config-file. Now you have to explicitly turn off SocksPort,
3168 if you don't want it open.
3169 - We were starting to daemonize before we opened our logs, so if
3170 there were any problems opening logs, we would complain to stderr,
3171 which wouldn't work, and then mysteriously exit.
3172 - If a verified OR connects to us before he's uploaded his descriptor,
3173 or we verify him and hup but he still has the original TLS
3174 connection, then conn->nickname is still set like he's unverified.
3176 o Code security improvements, inspired by Ilja:
3177 - tor_snprintf wrapper over snprintf with consistent (though not C99)
3179 - Replace sprintf with tor_snprintf. (I think they were all safe, but
3181 - Replace strcpy/strncpy with strlcpy in more places.
3182 - Avoid strcat; use tor_snprintf or strlcat instead.
3184 o Features (circuits and streams):
3185 - New circuit building strategy: keep a list of ports that we've
3186 used in the past 6 hours, and always try to have 2 circuits open
3187 or on the way that will handle each such port. Seed us with port
3188 80 so web users won't complain that Tor is "slow to start up".
3189 - Make kill -USR1 dump more useful stats about circuits.
3190 - When warning about retrying or giving up, print the address, so
3191 the user knows which one it's talking about.
3192 - If you haven't used a clean circuit in an hour, throw it away,
3193 just to be on the safe side. (This means after 6 hours a totally
3194 unused Tor client will have no circuits open.)
3195 - Support "foo.nickname.exit" addresses, to let Alice request the
3196 address "foo" as viewed by exit node "nickname". Based on a patch
3198 - If your requested entry or exit node has advertised bandwidth 0,
3200 - Be more greedy about filling up relay cells -- we try reading again
3201 once we've processed the stuff we read, in case enough has arrived
3202 to fill the last cell completely.
3203 - Refuse application socks connections to port 0.
3204 - Use only 0.0.9pre1 and later servers for resolve cells.
3206 o Features (bandwidth):
3207 - Hibernation: New config option "AccountingMax" lets you
3208 set how many bytes per month (in each direction) you want to
3209 allow your server to consume. Rather than spreading those
3210 bytes out evenly over the month, we instead hibernate for some
3211 of the month and pop up at a deterministic time, work until
3212 the bytes are consumed, then hibernate again. Config option
3213 "MonthlyAccountingStart" lets you specify which day of the month
3214 your billing cycle starts on.
3215 - Implement weekly/monthly/daily accounting: now you specify your
3216 hibernation properties by
3217 AccountingMax N bytes|KB|MB|GB|TB
3218 AccountingStart day|week|month [day] HH:MM
3219 Defaults to "month 1 0:00".
3220 - Let bandwidth and interval config options be specified as 5 bytes,
3221 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
3223 o Features (directories):
3224 - New "router-status" line in directory, to better bind each verified
3225 nickname to its identity key.
3226 - Clients can ask dirservers for /dir.z to get a compressed version
3227 of the directory. Only works for servers running 0.0.9, of course.
3228 - Make clients cache directories and use them to seed their router
3229 lists at startup. This means clients have a datadir again.
3230 - Respond to content-encoding headers by trying to uncompress as
3232 - Clients and servers now fetch running-routers; cache
3233 running-routers; compress running-routers; serve compressed
3235 - Make moria2 advertise a dirport of 80, so people behind firewalls
3236 will be able to get a directory.
3237 - Http proxy support
3238 - Dirservers translate requests for http://%s:%d/x to /x
3239 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
3240 be routed through this host.
3241 - Clients ask for /tor/x rather than /x for new enough dirservers.
3242 This way we can one day coexist peacefully with apache.
3243 - Clients specify a "Host: %s%d" http header, to be compatible
3244 with more proxies, and so running squid on an exit node can work.
3245 - Protect dirservers from overzealous descriptor uploading -- wait
3246 10 seconds after directory gets dirty, before regenerating.
3248 o Features (packages and install):
3249 - Add NSI installer contributed by J Doe.
3250 - Apply NT service patch from Osamu Fujino. Still needs more work.
3251 - Commit VC6 and VC7 workspace/project files.
3252 - Commit a tor.spec for making RPM files, with help from jbash.
3253 - Add contrib/torctl.in contributed by Glenn Fink.
3254 - Make expand_filename handle ~ and ~username.
3255 - Use autoconf to enable largefile support where necessary. Use
3256 ftello where available, since ftell can fail at 2GB.
3257 - Ship src/win32/ in the tarball, so people can use it to build.
3258 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
3261 o Features (ui controller):
3262 - Control interface: a separate program can now talk to your
3263 client/server over a socket, and get/set config options, receive
3264 notifications of circuits and streams starting/finishing/dying,
3265 bandwidth used, etc. The next step is to get some GUIs working.
3266 Let us know if you want to help out. See doc/control-spec.txt .
3267 - Ship a contrib/tor-control.py as an example script to interact
3268 with the control port.
3269 - "tor --hash-password zzyxz" will output a salted password for
3270 use in authenticating to the control interface.
3271 - Implement the control-spec's SAVECONF command, to write your
3272 configuration to torrc.
3273 - Get cookie authentication for the controller closer to working.
3274 - When set_conf changes our server descriptor, upload a new copy.
3275 But don't upload it too often if there are frequent changes.
3277 o Features (config and command-line):
3278 - Deprecate unofficial config option abbreviations, and abbreviations
3279 not on the command line.
3280 - Configuration infrastructure support for warning on obsolete
3282 - Give a slightly more useful output for "tor -h".
3283 - Break DirFetchPostPeriod into:
3284 - DirFetchPeriod for fetching full directory,
3285 - StatusFetchPeriod for fetching running-routers,
3286 - DirPostPeriod for posting server descriptor,
3287 - RendPostPeriod for posting hidden service descriptors.
3288 - New log format in config:
3289 "Log minsev[-maxsev] stdout|stderr|syslog" or
3290 "Log minsev[-maxsev] file /var/foo"
3291 - DirPolicy config option, to let people reject incoming addresses
3292 from their dirserver.
3293 - "tor --list-fingerprint" will list your identity key fingerprint
3295 - Make tor --version --version dump the cvs Id of every file.
3296 - New 'MyFamily nick1,...' config option for a server to
3297 specify other servers that shouldn't be used in the same circuit
3298 with it. Only believed if nick1 also specifies us.
3299 - New 'NodeFamily nick1,nick2,...' config option for a client to
3300 specify nodes that it doesn't want to use in the same circuit.
3301 - New 'Redirectexit pattern address:port' config option for a
3302 server to redirect exit connections, e.g. to a local squid.
3303 - Add "pass" target for RedirectExit, to make it easier to break
3304 out of a sequence of RedirectExit rules.
3305 - Make the dirservers file obsolete.
3306 - Include a dir-signing-key token in directories to tell the
3307 parsing entity which key is being used to sign.
3308 - Remove the built-in bulky default dirservers string.
3309 - New config option "Dirserver %s:%d [fingerprint]", which can be
3310 repeated as many times as needed. If no dirservers specified,
3311 default to moria1,moria2,tor26.
3312 - Make 'Routerfile' config option obsolete.
3313 - Discourage people from setting their dirfetchpostperiod more often
3314 than once per minute.
3317 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
3318 get back to normal.)
3319 - Accept *:706 (silc) in default exit policy.
3320 - Implement new versioning format for post 0.1.
3321 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
3322 log more informatively.
3323 - Check clock skew for verified servers, but allow unverified
3324 servers and clients to have any clock skew.
3325 - Make sure the hidden service descriptors are at a random offset
3326 from each other, to hinder linkability.
3327 - Clients now generate a TLS cert too, in preparation for having
3328 them act more like real nodes.
3329 - Add a pure-C tor-resolve implementation.
3330 - Use getrlimit and friends to ensure we can reach MaxConn (currently
3331 1024) file descriptors.
3332 - Raise the max dns workers from 50 to 100.
3335 Changes in version 0.0.8.1 - 2004-10-13
3337 - Fix a seg fault that can be triggered remotely for Tor
3338 clients/servers with an open dirport.
3339 - Fix a rare assert trigger, where routerinfos for entries in
3340 our cpath would expire while we're building the path.
3341 - Fix a bug in OutboundBindAddress so it (hopefully) works.
3342 - Fix a rare seg fault for people running hidden services on
3343 intermittent connections.
3344 - Fix a bug in parsing opt keywords with objects.
3345 - Fix a stale pointer assert bug when a stream detaches and
3347 - Fix a string format vulnerability (probably not exploitable)
3348 in reporting stats locally.
3349 - Fix an assert trigger: sometimes launching circuits can fail
3350 immediately, e.g. because too many circuits have failed recently.
3351 - Fix a compile warning on 64 bit platforms.
3354 Changes in version 0.0.8 - 2004-08-25
3356 - Made our unit tests compile again on OpenBSD 3.5, and tor
3357 itself compile again on OpenBSD on a sparc64.
3358 - We were neglecting milliseconds when logging on win32, so
3359 everything appeared to happen at the beginning of each second.
3360 - Check directory signature _before_ you decide whether you're
3361 you're running an obsolete version and should exit.
3362 - Check directory signature _before_ you parse the running-routers
3363 list to decide who's running.
3364 - Check return value of fclose while writing to disk, so we don't
3365 end up with broken files when servers run out of disk space.
3366 - Port it to SunOS 5.9 / Athena
3367 - Fix two bugs in saving onion keys to disk when rotating, so
3368 hopefully we'll get fewer people using old onion keys.
3369 - Remove our mostly unused -- and broken -- hex_encode()
3370 function. Use base16_encode() instead. (Thanks to Timo Lindfors
3371 for pointing out this bug.)
3372 - Only pick and establish intro points after we've gotten a
3374 - Fix assert triggers: if the other side returns an address 0.0.0.0,
3375 don't put it into the client dns cache.
3376 - If a begin failed due to exit policy, but we believe the IP
3377 address should have been allowed, switch that router to exitpolicy
3378 reject *:* until we get our next directory.
3381 - 'Extend' relay cell payloads now include the digest of the
3382 intended next hop's identity key. Now we can verify that we're
3383 extending to the right router, and also extend to routers we
3384 hadn't heard of before.
3387 - Tor nodes can now act as relays (with an advertised ORPort)
3388 without being manually verified by the dirserver operators.
3389 - Uploaded descriptors of unverified routers are now accepted
3390 by the dirservers, and included in the directory.
3391 - Verified routers are listed by nickname in the running-routers
3392 list; unverified routers are listed as "$<fingerprint>".
3393 - We now use hash-of-identity-key in most places rather than
3394 nickname or addr:port, for improved security/flexibility.
3395 - AllowUnverifiedNodes config option to let circuits choose no-name
3396 routers in entry,middle,exit,introduction,rendezvous positions.
3397 Allow middle and rendezvous positions by default.
3398 - When picking unverified routers, skip those with low uptime and/or
3399 low bandwidth, depending on what properties you care about.
3400 - ClientOnly option for nodes that never want to become servers.
3401 - Directory caching.
3402 - "AuthoritativeDir 1" option for the official dirservers.
3403 - Now other nodes (clients and servers) will cache the latest
3404 directory they've pulled down.
3405 - They can enable their DirPort to serve it to others.
3406 - Clients will pull down a directory from any node with an open
3407 DirPort, and check the signature/timestamp correctly.
3408 - Authoritative dirservers now fetch directories from other
3409 authdirservers, to stay better synced.
3410 - Running-routers list tells who's down also, along with noting
3411 if they're verified (listed by nickname) or unverified (listed
3413 - Allow dirservers to serve running-router list separately.
3414 This isn't used yet.
3415 - You can now fetch $DIRURL/running-routers to get just the
3416 running-routers line, not the whole descriptor list. (But
3417 clients don't use this yet.)
3418 - Clients choose nodes proportional to advertised bandwidth.
3419 - Clients avoid using nodes with low uptime as introduction points.
3420 - Handle servers with dynamic IP addresses: don't just replace
3421 options->Address with the resolved one at startup, and
3422 detect our address right before we make a routerinfo each time.
3423 - 'FascistFirewall' option to pick dirservers and ORs on specific
3424 ports; plus 'FirewallPorts' config option to tell FascistFirewall
3425 which ports are open. (Defaults to 80,443)
3426 - Try other dirservers immediately if the one you try is down. This
3427 should tolerate down dirservers better now.
3428 - ORs connect-on-demand to other ORs
3429 - If you get an extend cell to an OR you're not connected to,
3430 connect, handshake, and forward the create cell.
3431 - The authoritative dirservers stay connected to everybody,
3432 and everybody stays connected to 0.0.7 servers, but otherwise
3433 clients/servers expire unused connections after 5 minutes.
3434 - When servers get a sigint, they delay 30 seconds (refusing new
3435 connections) then exit. A second sigint causes immediate exit.
3436 - File and name management:
3437 - Look for .torrc if no CONFDIR "torrc" is found.
3438 - If no datadir is defined, then choose, make, and secure ~/.tor
3440 - If torrc not found, exitpolicy reject *:*.
3441 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
3442 - If no nickname is defined, derive default from hostname.
3443 - Rename secret key files, e.g. identity.key -> secret_id_key,
3444 to discourage people from mailing their identity key to tor-ops.
3445 - Refuse to build a circuit before the directory has arrived --
3446 it won't work anyway, since you won't know the right onion keys
3448 - Parse tor version numbers so we can do an is-newer-than check
3449 rather than an is-in-the-list check.
3450 - New socks command 'resolve', to let us shim gethostbyname()
3452 - A 'tor_resolve' script to access the socks resolve functionality.
3453 - A new socks-extensions.txt doc file to describe our
3454 interpretation and extensions to the socks protocols.
3455 - Add a ContactInfo option, which gets published in descriptor.
3456 - Write tor version at the top of each log file
3457 - New docs in the tarball:
3459 - Document that you should proxy your SSL traffic too.
3460 - Log a warning if the user uses an unsafe socks variant, so people
3461 are more likely to learn about privoxy or socat.
3462 - Log a warning if you're running an unverified server, to let you
3463 know you might want to get it verified.
3464 - Change the default exit policy to reject the default edonkey,
3465 kazaa, gnutella ports.
3466 - Add replace_file() to util.[ch] to handle win32's rename().
3467 - Publish OR uptime in descriptor (and thus in directory) too.
3468 - Remember used bandwidth (both in and out), and publish 15-minute
3469 snapshots for the past day into our descriptor.
3470 - Be more aggressive about trying to make circuits when the network
3471 has changed (e.g. when you unsuspend your laptop).
3472 - Check for time skew on http headers; report date in response to
3474 - If the entrynode config line has only one node, don't pick it as
3476 - Add strict{entry|exit}nodes config options. If set to 1, then
3477 we refuse to build circuits that don't include the specified entry
3479 - OutboundBindAddress config option, to bind to a specific
3480 IP address for outgoing connect()s.
3481 - End truncated log entries (e.g. directories) with "[truncated]".
3484 Changes in version 0.0.7.3 - 2004-08-12
3485 o Stop dnsworkers from triggering an assert failure when you
3486 ask them to resolve the host "".
3489 Changes in version 0.0.7.2 - 2004-07-07
3490 o A better fix for the 0.0.0.0 problem, that will hopefully
3491 eliminate the remaining related assertion failures.
3494 Changes in version 0.0.7.1 - 2004-07-04
3495 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
3496 since internally we use 0.0.0.0 to signify "not yet resolved".
3499 Changes in version 0.0.7 - 2004-06-07
3500 o Fixes for crashes and other obnoxious bugs:
3501 - Fix an epipe bug: sometimes when directory connections failed
3502 to connect, we would give them a chance to flush before closing
3504 - When we detached from a circuit because of resolvefailed, we
3505 would immediately try the same circuit twice more, and then
3506 give up on the resolve thinking we'd tried three different
3508 - Limit the number of intro circuits we'll attempt to build for a
3509 hidden service per 15-minute period.
3510 - Check recommended-software string *early*, before actually parsing
3511 the directory. Thus we can detect an obsolete version and exit,
3512 even if the new directory format doesn't parse.
3513 o Fixes for security bugs:
3514 - Remember which nodes are dirservers when you startup, and if a
3515 random OR enables his dirport, don't automatically assume he's
3516 a trusted dirserver.
3518 - Directory connections were asking the wrong poll socket to
3519 start writing, and not asking themselves to start writing.
3520 - When we detached from a circuit because we sent a begin but
3521 didn't get a connected, we would use it again the first time;
3522 but after that we would correctly switch to a different one.
3523 - Stop warning when the first onion decrypt attempt fails; they
3524 will sometimes legitimately fail now that we rotate keys.
3525 - Override unaligned-access-ok check when $host_cpu is ia64 or
3526 arm. Apparently they allow it but the kernel whines.
3527 - Dirservers try to reconnect periodically too, in case connections
3529 - Fix some memory leaks in directory servers.
3530 - Allow backslash in Win32 filenames.
3531 - Made Tor build complain-free on FreeBSD, hopefully without
3532 breaking other BSD builds. We'll see.
3533 - Check directory signatures based on name of signer, not on whom
3534 we got the directory from. This will let us cache directories more
3536 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
3539 - Doxygen markup on all functions and global variables.
3540 - Make directory functions update routerlist, not replace it. So
3541 now directory disagreements are not so critical a problem.
3542 - Remove the upper limit on number of descriptors in a dirserver's
3543 directory (not that we were anywhere close).
3544 - Allow multiple logfiles at different severity ranges.
3545 - Allow *BindAddress to specify ":port" rather than setting *Port
3546 separately. Allow multiple instances of each BindAddress config
3547 option, so you can bind to multiple interfaces if you want.
3548 - Allow multiple exit policy lines, which are processed in order.
3549 Now we don't need that huge line with all the commas in it.
3550 - Enable accept/reject policies on SOCKS connections, so you can bind
3551 to 0.0.0.0 but still control who can use your OP.
3552 - Updated the man page to reflect these features.
3555 Changes in version 0.0.6.2 - 2004-05-16
3556 o Our integrity-checking digest was checking only the most recent cell,
3557 not the previous cells like we'd thought.
3558 Thanks to Stefan Mark for finding the flaw!
3561 Changes in version 0.0.6.1 - 2004-05-06
3562 o Fix two bugs in our AES counter-mode implementation (this affected
3563 onion-level stream encryption, but not TLS-level). It turns
3564 out we were doing something much more akin to a 16-character
3565 polyalphabetic cipher. Oops.
3566 Thanks to Stefan Mark for finding the flaw!
3567 o Retire moria3 as a directory server, and add tor26 as a directory
3571 Changes in version 0.0.6 - 2004-05-02
3573 - Hidden services and rendezvous points are implemented. Go to
3574 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
3575 hidden services. (This only works via a socks4a proxy such as
3576 Privoxy, and currently it's quite slow.)
3577 - We now rotate link (tls context) keys and onion keys.
3578 - CREATE cells now include oaep padding, so you can tell
3579 if you decrypted them correctly.
3580 - Retry stream correctly when we fail to connect because of
3581 exit-policy-reject (should try another) or can't-resolve-address.
3582 - When we hup a dirserver and we've *removed* a server from the
3583 approved-routers list, now we remove that server from the
3584 in-memory directories too.
3585 - Add bandwidthburst to server descriptor.
3586 - Directories now say which dirserver signed them.
3587 - Use a tor_assert macro that logs failed assertions too.
3588 - Since we don't support truncateds much, don't bother sending them;
3589 just close the circ.
3590 - Fetch randomness from /dev/urandom better (not via fopen/fread)
3591 - Better debugging for tls errors
3592 - Set Content-Type on the directory and hidserv descriptor.
3593 - Remove IVs from cipher code, since AES-ctr has none.
3595 - Fix an assert trigger for exit nodes that's been plaguing us since
3596 the days of 0.0.2prexx (thanks weasel!)
3597 - Fix a bug where we were closing tls connections intermittently.
3598 It turns out openssl keeps its errors around -- so if an error
3599 happens, and you don't ask about it, and then another openssl
3600 operation happens and succeeds, and you ask if there was an error,
3601 it tells you about the first error.
3602 - Fix a bug that's been lurking since 27 may 03 (!)
3603 When passing back a destroy cell, we would use the wrong circ id.
3604 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
3605 - Some versions of openssl have an SSL_pending function that erroneously
3606 returns bytes when there is a non-application record pending.
3607 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
3608 o We were using an array of length zero in a few places.
3609 o Win32's gethostbyname can't resolve an IP to an IP.
3610 o Win32's close can't close a socket.
3611 o Handle windows socket errors correctly.
3613 - check for <sys/limits.h> so we build on FreeBSD again, and
3614 <machine/limits.h> for NetBSD.
3617 Changes in version 0.0.5 - 2004-03-30
3618 o Install torrc as torrc.sample -- we no longer clobber your
3620 o Fix mangled-state bug in directory fetching (was causing sigpipes).
3621 o Only build circuits after we've fetched the directory: clients were
3622 using only the directory servers before they'd fetched a directory.
3623 This also means longer startup time; so it goes.
3624 o Fix an assert trigger where an OP would fail to handshake, and we'd
3625 expect it to have a nickname.
3626 o Work around a tsocks bug: do a socks reject when AP connection dies
3627 early, else tsocks goes into an infinite loop.
3628 o Hold socks connection open until reply is flushed (if possible)
3629 o Make exit nodes resolve IPs to IPs immediately, rather than asking
3630 the dns farm to do it.
3631 o Fix c99 aliasing warnings in rephist.c
3632 o Don't include server descriptors that are older than 24 hours in the
3634 o Give socks 'reject' replies their whole 15s to attempt to flush,
3635 rather than seeing the 60s timeout and assuming the flush had failed.
3636 o Clean automake droppings from the cvs repository
3637 o Add in a 'notice' log level for things the operator should hear
3638 but that aren't warnings
3641 Changes in version 0.0.4 - 2004-03-26
3642 o When connecting to a dirserver or OR and the network is down,
3646 Changes in version 0.0.3 - 2004-03-26
3647 o Warn and fail if server chose a nickname with illegal characters
3648 o Port to Solaris and Sparc:
3649 - include missing header fcntl.h
3650 - have autoconf find -lsocket -lnsl automatically
3651 - deal with hardware word alignment
3652 - make uname() work (solaris has a different return convention)
3653 - switch from using signal() to sigaction()
3654 o Preliminary work on reputation system:
3655 - Keep statistics on success/fail of connect attempts; they're published
3656 by kill -USR1 currently.
3657 - Add a RunTesting option to try to learn link state by creating test
3658 circuits, even when SocksPort is off.
3659 - Remove unused open circuits when there are too many.
3662 Changes in version 0.0.2 - 2004-03-19
3663 - Include strlcpy and strlcat for safer string ops
3664 - define INADDR_NONE so we compile (but still not run) on solaris
3667 Changes in version 0.0.2pre27 - 2004-03-14
3669 - Allow internal tor networks (we were rejecting internal IPs,
3670 now we allow them if they're set explicitly).
3671 - And fix a few endian issues.
3674 Changes in version 0.0.2pre26 - 2004-03-14
3676 - If a stream times out after 15s without a connected cell, don't
3677 try that circuit again: try a new one.
3678 - Retry streams at most 4 times. Then give up.
3679 - When a dirserver gets a descriptor from an unknown router, it
3680 logs its fingerprint (so the dirserver operator can choose to
3681 accept it even without mail from the server operator).
3682 - Inform unapproved servers when we reject their descriptors.
3683 - Make tor build on Windows again. It works as a client, who knows
3685 - Clearer instructions in the torrc for how to set up a server.
3686 - Be more efficient about reading fd's when our global token bucket
3687 (used for rate limiting) becomes empty.
3689 - Stop asserting that computers always go forward in time. It's
3691 - When we sent a cell (e.g. destroy) and then marked an OR connection
3692 expired, we might close it before finishing a flush if the other
3693 side isn't reading right then.
3694 - Don't allow dirservers to start if they haven't defined
3696 - We were caching transient dns failures. Oops.
3697 - Prevent servers from publishing an internal IP as their address.
3698 - Address a strcat vulnerability in circuit.c
3701 Changes in version 0.0.2pre25 - 2004-03-04
3703 - Put the OR's IP in its router descriptor, not its fqdn. That way
3704 we'll stop being stalled by gethostbyname for nodes with flaky dns,
3707 - If the user typed in an address that didn't resolve, the server
3711 Changes in version 0.0.2pre24 - 2004-03-03
3713 - Fix an assertion failure in dns.c, where we were trying to dequeue
3714 a pending dns resolve even if it wasn't pending
3715 - Fix a spurious socks5 warning about still trying to write after the
3716 connection is finished.
3717 - Hold certain marked_for_close connections open until they're finished
3718 flushing, rather than losing bytes by closing them too early.
3719 - Correctly report the reason for ending a stream
3720 - Remove some duplicate calls to connection_mark_for_close
3721 - Put switch_id and start_daemon earlier in the boot sequence, so it
3722 will actually try to chdir() to options.DataDirectory
3723 - Make 'make test' exit(1) if a test fails; fix some unit tests
3724 - Make tor fail when you use a config option it doesn't know about,
3725 rather than warn and continue.
3726 - Make --version work
3727 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
3730 Changes in version 0.0.2pre23 - 2004-02-29
3732 - Print a statement when the first circ is finished, so the user
3734 - If a relay cell is unrecognized at the end of the circuit,
3735 send back a destroy. (So attacks to mutate cells are more
3737 - New config option 'excludenodes' to avoid certain nodes for circuits.
3738 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
3739 so you can collect coredumps there.
3741 - Fix a bug in tls flushing where sometimes data got wedged and
3742 didn't flush until more data got sent. Hopefully this bug was
3743 a big factor in the random delays we were seeing.
3744 - Make 'connected' cells include the resolved IP, so the client
3745 dns cache actually gets populated.
3746 - Disallow changing from ORPort=0 to ORPort>0 on hup.
3747 - When we time-out on a stream and detach from the circuit, send an
3748 end cell down it first.
3749 - Only warn about an unknown router (in exitnodes, entrynodes,
3750 excludenodes) after we've fetched a directory.
3753 Changes in version 0.0.2pre22 - 2004-02-26
3755 - Servers publish less revealing uname information in descriptors.
3756 - More memory tracking and assertions, to crash more usefully when
3758 - If the default torrc isn't there, just use some default defaults.
3759 Plus provide an internal dirservers file if they don't have one.
3760 - When the user tries to use Tor as an http proxy, give them an http
3761 501 failure explaining that we're a socks proxy.
3762 - Dump a new router.desc on hup, to help confused people who change
3763 their exit policies and then wonder why router.desc doesn't reflect
3765 - Clean up the generic tor.sh init script that we ship with.
3767 - If the exit stream is pending on the resolve, and a destroy arrives,
3768 then the stream wasn't getting removed from the pending list. I
3769 think this was the one causing recent server crashes.
3770 - Use a more robust poll on OSX 10.3, since their poll is flaky.
3771 - When it couldn't resolve any dirservers, it was useless from then on.
3772 Now it reloads the RouterFile (or default dirservers) if it has no
3774 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
3775 many users don't even *have* a /usr/local/sbin/.
3778 Changes in version 0.0.2pre21 - 2004-02-18
3780 - There's a ChangeLog file that actually reflects the changelog.
3781 - There's a 'torify' wrapper script, with an accompanying
3782 tor-tsocks.conf, that simplifies the process of using tsocks for
3783 tor. It even has a man page.
3784 - The tor binary gets installed to sbin rather than bin now.
3785 - Retry streams where the connected cell hasn't arrived in 15 seconds
3786 - Clean up exit policy handling -- get the default out of the torrc,
3787 so we can update it without forcing each server operator to fix
3789 - Allow imaps and pop3s in default exit policy
3791 - Prevent picking middleman nodes as the last node in the circuit
3794 Changes in version 0.0.2pre20 - 2004-01-30
3796 - We now have a deb package, and it's in debian unstable. Go to
3798 - I've split the TotalBandwidth option into BandwidthRate (how many
3799 bytes per second you want to allow, long-term) and
3800 BandwidthBurst (how many bytes you will allow at once before the cap
3801 kicks in). This better token bucket approach lets you, say, set
3802 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
3803 performance while not exceeding your monthly bandwidth quota.
3804 - Push out a tls record's worth of data once you've got it, rather
3805 than waiting until you've read everything waiting to be read. This
3806 may improve performance by pipelining better. We'll see.
3807 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
3808 from failed circuits (if they haven't been connected yet) and attach
3810 - Expire old streams that haven't managed to connect. Some day we'll
3811 have them reattach to new circuits instead.
3814 - Fix several memory leaks that were causing servers to become bloated
3816 - Fix a few very rare assert triggers. A few more remain.
3817 - Setuid to User _before_ complaining about running as root.
3820 Changes in version 0.0.2pre19 - 2004-01-07
3822 - Fix deadlock condition in dns farm. We were telling a child to die by
3823 closing the parent's file descriptor to him. But newer children were
3824 inheriting the open file descriptor from the parent, and since they
3825 weren't closing it, the socket never closed, so the child never read
3826 eof, so he never knew to exit. Similarly, dns workers were holding
3827 open other sockets, leading to all sorts of chaos.
3828 - New cleaner daemon() code for forking and backgrounding.
3829 - If you log to a file, it now prints an entry at the top of the
3830 logfile so you know it's working.
3831 - The onionskin challenge length was 30 bytes longer than necessary.
3832 - Started to patch up the spec so it's not quite so out of date.
3835 Changes in version 0.0.2pre18 - 2004-01-02
3837 - Fix endian issues with the 'integrity' field in the relay header.
3838 - Fix a potential bug where connections in state
3839 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
3842 Changes in version 0.0.2pre17 - 2003-12-30
3844 - Made --debuglogfile (or any second log file, actually) work.
3845 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
3846 adversary could force us into an infinite loop.
3849 - Each onionskin handshake now includes a hash of the computed key,
3850 to prove the server's identity and help perfect forward secrecy.
3851 - Changed cell size from 256 to 512 bytes (working toward compatibility
3853 - Changed cell length to 2 bytes, and moved it to the relay header.
3854 - Implemented end-to-end integrity checking for the payloads of
3856 - Separated streamid from 'recognized' (otherwise circuits will get
3857 messed up when we try to have streams exit from the middle). We
3858 use the integrity-checking to confirm that a cell is addressed to
3860 - Randomize the initial circid and streamid values, so an adversary who
3861 breaks into a node can't learn how many circuits or streams have
3865 Changes in version 0.0.2pre16 - 2003-12-14
3867 - Fixed a bug that made HUP trigger an assert
3868 - Fixed a bug where a circuit that immediately failed wasn't being
3869 counted as a failed circuit in counting retries.
3872 - Now we close the circuit when we get a truncated cell: otherwise we're
3873 open to an anonymity attack where a bad node in the path truncates
3874 the circuit and then we open streams at him.
3875 - Add port ranges to exit policies
3876 - Add a conservative default exit policy
3877 - Warn if you're running tor as root
3878 - on HUP, retry OR connections and close/rebind listeners
3879 - options.EntryNodes: try these nodes first when picking the first node
3880 - options.ExitNodes: if your best choices happen to include any of
3881 your preferred exit nodes, you choose among just those preferred
3883 - options.ExcludedNodes: nodes that are never picked in path building
3886 Changes in version 0.0.2pre15 - 2003-12-03
3887 o Robustness and bugfixes:
3888 - Sometimes clients would cache incorrect DNS resolves, which would
3889 really screw things up.
3890 - An OP that goes offline would slowly leak all its sockets and stop
3892 - A wide variety of bugfixes in exit node selection, exit policy
3893 handling, and processing pending streams when a new circuit is
3895 - Pick nodes for a path only from those the directory says are up
3896 - Choose randomly from all running dirservers, not always the first one
3897 - Increase allowed http header size for directory fetch.
3898 - Stop writing to stderr (if we're daemonized it will be closed).
3899 - Enable -g always, so cores will be more useful to me.
3900 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
3903 - Wrote a man page. It lists commonly used options.
3906 - Change default loglevel to warn.
3907 - Make PidFile default to null rather than littering in your CWD.
3908 - OnionRouter config option is now obsolete. Instead it just checks
3910 - Moved to a single unified torrc file for both clients and servers.
3913 Changes in version 0.0.2pre14 - 2003-11-29
3914 o Robustness and bugfixes:
3915 - Force the admin to make the DataDirectory himself
3916 - to get ownership/permissions right
3917 - so clients no longer make a DataDirectory and then never use it
3918 - fix bug where a client who was offline for 45 minutes would never
3919 pull down a directory again
3920 - fix (or at least hide really well) the dns assert bug that was
3921 causing server crashes
3922 - warnings and improved robustness wrt clockskew for certs
3923 - use the native daemon(3) to daemonize, when available
3924 - exit if bind() fails
3925 - exit if neither socksport nor orport is defined
3926 - include our own tor_timegm (Win32 doesn't have its own)
3927 - bugfix for win32 with lots of connections
3928 - fix minor bias in PRNG
3929 - make dirserver more robust to corrupt cached directory
3932 - Wrote the design document (woo)
3934 o Circuit building and exit policies:
3935 - Circuits no longer try to use nodes that the directory has told them
3937 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
3938 bitcounts (18.0.0.0/8).
3939 - Make AP connections standby for a circuit if no suitable circuit
3940 exists, rather than failing
3941 - Circuits choose exit node based on addr/port, exit policies, and
3942 which AP connections are standing by
3943 - Bump min pathlen from 2 to 3
3944 - Relay end cells have a payload to describe why the stream ended.
3945 - If the stream failed because of exit policy, try again with a new
3947 - Clients have a dns cache to remember resolved addresses.
3948 - Notice more quickly when we have no working circuits
3951 - APPort is now called SocksPort
3952 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
3954 - RecommendedVersions is now a config variable rather than
3955 hardcoded (for dirservers)
3956 - Reloads config on HUP
3957 - Usage info on -h or --help
3958 - If you set User and Group config vars, it'll setu/gid to them.
3960 Changes in version 0.0.2pre13 - 2003-10-19
3961 o General stability:
3962 - SSL_write no longer fails when it returns WANTWRITE and the number
3963 of bytes in the buf has changed by the next SSL_write call.
3964 - Fix segfault fetching directory when network is down
3965 - Fix a variety of minor memory leaks
3966 - Dirservers reload the fingerprints file on HUP, so I don't have
3967 to take down the network when I approve a new router
3968 - Default server config file has explicit Address line to specify fqdn
3971 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
3972 - Make listener connections not ever alloc bufs
3974 o Autoconf improvements:
3975 - don't clobber an external CFLAGS in ./configure
3976 - Make install now works
3977 - create var/lib/tor on make install
3978 - autocreate a tor.sh initscript to help distribs
3979 - autocreate the torrc and sample-server-torrc with correct paths
3981 o Log files and Daemonizing now work:
3982 - If --DebugLogFile is specified, log to it at -l debug
3983 - If --LogFile is specified, use it instead of commandline
3984 - If --RunAsDaemon is set, tor forks and backgrounds on startup