Tor 0.3.3.6 is released: a new stable series!
Hello, everyone!
After months of work, we have a new stable release series! If you build Tor from source, you can download the source code for 0.3.3.6 on the website. Packages should be available within the next several weeks, with a new Tor Browser by some time in June.
Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It backports several important fixes from the 0.3.4.1-alpha.
The Tor 0.3.3 series includes controller support and other improvements for v3 onion services, official support for embedding Tor within other applications, and our first non-trivial module written in the Rust programming language. (Rust is still not enabled by default when building Tor.) And as usual, there are numerous other smaller bugfixes, features, and improvements.
Below are the changes since 0.3.2.10. For a list of only the changes since 0.3.3.5-rc, see the ChangeLog file.
Changes in version 0.3.3.6 - 2018-05-22
- New system requirements:
- When built with Rust, Tor now depends on version 0.2.39 of the libc crate. Closes tickets 25310 and 25664.
- Major features (embedding):
- There is now a documented stable API for programs that need to embed Tor. See tor_api.h for full documentation and known bugs. Closes ticket 23684.
- Tor now has support for restarting in the same process. Controllers that run Tor using the "tor_api.h" interface can now restart Tor after Tor has exited. This support is incomplete, however: we fixed crash bugs that prevented it from working at all, but many bugs probably remain, including a possibility of security issues. Implements ticket 24581.
- Major features (IPv6, directory documents):
- Add consensus method 27, which adds IPv6 ORPorts to the microdesc consensus. This information makes it easier for IPv6 clients to bootstrap and choose reachable entry guards. Implements ticket 23826.
- Add consensus method 28, which removes IPv6 ORPorts from microdescriptors. Now that the consensus contains IPv6 ORPorts, they are redundant in microdescs. This change will be used by Tor clients on 0.2.8.x and later. (That is to say, with all Tor clients that have IPv6 bootstrap and guard support.) Implements ticket 23828.
- Expand the documentation for AuthDirHasIPv6Connectivity when it is set by different numbers of authorities. Fixes 23870 on 0.2.4.1-alpha.
- Major features (onion service v3, control port):
- The control port now supports commands and events for v3 onion services. It is now possible to create ephemeral v3 services using ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT, CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and DEL_ONION) have been extended to support v3 onion services. Closes ticket 20699; implements proposal 284.
- Major features (onion services):
- Provide torrc options to pin the second and third hops of onion service circuits to a list of nodes. The option HSLayer2Guards pins the second hop, and the option HSLayer3Guards pins the third hop. These options are for use in conjunction with experiments with "vanguards" for preventing guard enumeration attacks. Closes ticket 13837.
- When v3 onion service clients send introduce cells, they now include the IPv6 address of the rendezvous point, if it has one. Current v3 onion services running 0.3.2 ignore IPv6 addresses, but in future Tor versions, IPv6-only v3 single onion services will be able to use IPv6 addresses to connect directly to the rendezvous point. Closes ticket 23577. Patch by Neel Chauhan.
- Major features (relay):
- Implement an option, ReducedExitPolicy, to allow an Tor exit relay operator to use a more reasonable ("reduced") exit policy, rather than the default one. If you want to run an exit node without thinking too hard about which ports to allow, this one is for you. Closes ticket 13605. Patch from Neel Chauhan.
- Major features (rust, portability, experimental):
- Tor now ships with an optional implementation of one of its smaller modules (protover.c) in the Rust programming language. To try it out, install a Rust build environment, and configure Tor with "--enable-rust --enable-cargo-online-mode". This should not cause any user-visible changes, but should help us gain more experience with Rust, and plan future Rust integration work. Implementation by Chelsea Komlo. Closes ticket 22840.
- Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
- When directory authorities read a zero-byte bandwidth file, they would previously log a warning with the contents of an uninitialised buffer. They now log a warning about the empty file instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
- Major bugfixes (security, directory authority, denial-of-service):
- Fix a bug that could have allowed an attacker to force a directory authority to use up all its RAM by passing it a maliciously crafted protocol versions string. Fixes bug 25517; bugfix on 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
- Major bugfixes (crash, backport from 0.3.4.1-alpha):
- Avoid a rare assertion failure in the circuit build timeout code if we fail to allow any circuits to actually complete. Fixes bug 25733; bugfix on 0.2.2.2-alpha.
- Major bugfixes (netflow padding):
- Stop adding unneeded channel padding right after we finish flushing to a connection that has been trying to flush for many seconds. Instead, treat all partial or complete flushes as activity on the channel, which will defer the time until we need to add padding. This fix should resolve confusing and scary log messages like "Channel padding timeout scheduled 221453ms in the past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
- Major bugfixes (networking):
- Tor will no longer reject IPv6 address strings from Tor Browser when they are passed as hostnames in SOCKS5 requests. Fixes bug 25036, bugfix on Tor 0.3.1.2.
- Major bugfixes (onion service, backport from 0.3.4.1-alpha):
- Correctly detect when onion services get disabled after HUP. Fixes bug 25761; bugfix on 0.3.2.1.
- Major bugfixes (performance, load balancing):
- Directory authorities no longer vote in favor of the Guard flag for relays without directory support. Starting in Tor 0.3.0.1-alpha, clients have been avoiding using such relays in the Guard position, leading to increasingly broken load balancing for the 5%-or-so of Guards that don't advertise directory support. Fixes bug 22310; bugfix on 0.3.0.6.
- Major bugfixes (relay):
- If we have failed to connect to a relay and received a connection refused, timeout, or similar error (at the TCP level), do not try that same address/port again for 60 seconds after the failure has occurred. Fixes bug 24767; bugfix on 0.0.6.
- Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
- Impose a limit on circuit cell queue size. The limit can be controlled by a consensus parameter. Fixes bug 25226; bugfix on 0.2.4.14-alpha.
- Minor features (cleanup):
- Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile when it stops. Closes ticket 23271.
- Minor features (compatibility, backport from 0.3.4.1-alpha):
- Avoid some compilation warnings with recent versions of LibreSSL. Closes ticket 26006.
- Minor features (config options):
- Change the way the default value for MaxMemInQueues is calculated. We now use 40% of the hardware RAM if the system has 8 GB RAM or more. Otherwise we use the former value of 75%. Closes ticket 24782.
- Minor features (continuous integration):
- Update the Travis CI configuration to use the stable Rust channel, now that we have decided to require that. Closes ticket 25714.
- Minor features (continuous integration, backport from 0.3.4.1-alpha):
- Minor features (defensive programming):
- Most of the functions in Tor that free objects have been replaced with macros that free the objects and set the corresponding pointers to NULL. This change should help prevent a large class of dangling pointer bugs. Closes ticket 24337.
- Where possible, the tor_free() macro now only evaluates its input once. Part of ticket 24337.
- Check that microdesc ed25519 ids are non-zero in node_get_ed25519_id() before returning them. Implements ticket 24001, patch by "aruna1234".
- Minor features (directory authority):
- When directory authorities are unable to add signatures to a pending consensus, log the reason why. Closes ticket 24849.
- Minor features (embedding):
- Tor can now start with a preauthenticated control connection created by the process that launched it. This feature is meant for use by programs that want to launch and manage a Tor process without allowing other programs to manage it as well. For more information, see the __OwningControllerFD option documented in control-spec.txt. Closes ticket 23900.
- On most errors that would cause Tor to exit, it now tries to return from the tor_main() function, rather than calling the system exit() function. Most users won't notice a difference here, but it should be significant for programs that run Tor inside a separate thread: they should now be able to survive Tor's exit conditions rather than having Tor shut down the entire process. Closes ticket 23848.
- Applications that want to embed Tor can now tell Tor not to register any of its own POSIX signal handlers, using the __DisableSignalHandlers option. Closes ticket 24588.
- Minor features (fallback directory list):
- Avoid selecting fallbacks that change their IP addresses too often. Select more fallbacks by ignoring the Guard flag, and allowing lower cutoffs for the Running and V2Dir flags. Also allow a lower bandwidth, and a higher number of fallbacks per operator (5% of the list). Implements ticket 24785.
- Update the fallback whitelist and blacklist based on opt-ins and relay changes. Closes tickets 22321, 24678, 22527, 24135, and 24695.
- Minor features (fallback directory mirror configuration):
- Add a nickname to each fallback in a C comment. This makes it easier for operators to find their relays, and allows stem to use nicknames to identify fallbacks. Implements ticket 24600.
- Add a type and version header to the fallback directory mirror file. Also add a delimiter to the end of each fallback entry. This helps external parsers like stem and Relay Search. Implements ticket 24725.
- Add an extrainfo cache flag for each fallback in a C comment. This allows stem to use fallbacks to fetch extra-info documents, rather than using authorities. Implements ticket 22759.
- Add the generateFallbackDirLine.py script for automatically generating fallback directory mirror lines from relay fingerprints. No more typos! Add the lookupFallbackDirContact.py script for automatically looking up operator contact info from relay fingerprints. Implements ticket 24706, patch by teor and atagar.
- Reject any fallback directory mirror that serves an expired consensus. Implements ticket 20942, patch by "minik".
- Remove commas and equals signs from external string inputs to the fallback list. This avoids format confusion attacks. Implements ticket 24726.
- Remove the "weight=10" line from fallback directory mirror entries. Ticket 24681 will maintain the current fallback weights by changing Tor's default fallback weight to 10. Implements ticket 24679.
- Stop logging excessive information about fallback netblocks. Implements ticket 24791.
- Minor features (forward-compatibility):
- If a relay supports some link authentication protocol that we do not recognize, then include that relay's ed25519 key when telling other relays to extend to it. Previously, we treated future versions as if they were too old to support ed25519 link authentication. Closes ticket 20895.
- Minor features (geoip):
- Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country database. Closes ticket 26104.
- Minor features (heartbeat):
- Add onion service information to our heartbeat logs, displaying stats about the activity of configured onion services. Closes ticket 24896.
- Minor features (instrumentation, development):
- Add the MainloopStats option to allow developers to get instrumentation information from the main event loop via the heartbeat messages. We hope to use this to improve Tor's behavior when it's trying to sleep. Closes ticket 24605.
- Minor features (IPv6):
- Make IPv6-only clients wait for microdescs for relays, even if we were previously using descriptors (or were using them as a bridge) and have a cached descriptor for them. Implements ticket 23827.
- When a consensus has IPv6 ORPorts, make IPv6-only clients use them, rather than waiting to download microdescriptors. Implements ticket 23827.
- Minor features (log messages):
- Improve log message in the out-of-memory handler to include information about memory usage from the different compression backends. Closes ticket 25372.
- Improve a warning message that happens when we fail to re-parse an old router because of an expired certificate. Closes ticket 20020.
- Make the log more quantitative when we hit MaxMemInQueues threshold exposing some values. Closes ticket 24501.
- Minor features (logging):
- Minor features (performance):
- Minor features (performance, 32-bit):
- Improve performance on 32-bit systems by avoiding 64-bit division when calculating the timestamp in milliseconds for channel padding computations. Implements ticket 24613.
- Improve performance on 32-bit systems by avoiding 64-bit division when timestamping cells and buffer chunks for OOM calculations. Implements ticket 24374.
- Minor features (performance, OSX, iOS):
- Use the mach_approximate_time() function (when available) to implement coarse monotonic time. Having a coarse time function should avoid a large number of system calls, and improve performance slightly, especially under load. Closes ticket 24427.
- Minor features (performance, windows):
- Improve performance on Windows Vista and Windows 7 by adjusting TCP send window size according to the recommendation from SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch from Vort.
- Minor features (sandbox):
- Explicitly permit the poll() system call when the Linux seccomp2-based sandbox is enabled: apparently, some versions of libc use poll() when calling getpwnam(). Closes ticket 25313.
- Minor features (storage, configuration):
- Users can store cached directory documents somewhere other than the DataDirectory by using the CacheDirectory option. Similarly, the storage location for relay's keys can be overridden with the KeyDirectory option. Closes ticket 22703.
- Minor features (testing):
- Add a "make test-rust" target to run the rust tests only. Closes ticket 25071.
- Minor features (testing, debugging, embedding):
- For development purposes, Tor now has a mode in which it runs for a few seconds, then stops, and starts again without exiting the process. This mode is meant to help us debug various issues with ticket 23847. To use this feature, compile with --enable-restart-debugging, and set the TOR_DEBUG_RESTART environment variable. This is expected to crash a lot, and is really meant for developers only. It will likely be removed in a future release. Implements ticket 24583.
- Minor bugfixes (build, rust):
- Fix output of autoconf checks to display success messages for Rust dependencies and a suitable rustc compiler version. Fixes bug 24612; bugfix on 0.3.1.3-alpha.
- Don't pass the --quiet option to cargo: it seems to suppress some errors, which is not what we want to do when building. Fixes bug 24518; bugfix on 0.3.1.7.
- Build correctly when building from outside Tor's source tree with the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix on 0.3.1.7.
- Minor bugfixes (C correctness):
- Fix a very unlikely (impossible, we believe) null pointer dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by Coverity; this is CID 1430932.
- Minor bugfixes (channel, client):
- Better identify client connection when reporting to the geoip client cache. Fixes bug 24904; bugfix on 0.3.1.7.
- Minor bugfixes (circuit, cannibalization):
- Don't cannibalize preemptively-built circuits if we no longer recognize their first hop. This situation can happen if our Guard relay went off the consensus after the circuit was created. Fixes bug 24469; bugfix on 0.0.6.
- Minor bugfixes (client, backport from 0.3.4.1-alpha):
- Don't consider Tor running as a client if the ControlPort is open, but no actual client ports are open. Fixes bug 26062; bugfix on 0.2.9.4-alpha.
- Minor bugfixes (compilation):
- Fix a C99 compliance issue in our configuration script that caused compilation issues when compiling Tor with certain versions of xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
- Minor bugfixes (controller):
- Restore the correct operation of the RESOLVE command, which had been broken since we added the ability to enable/disable DNS on specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
- Avoid a (nonfatal) assertion failure when extending a one-hop circuit from the controller to become a multihop circuit. Fixes bug 24903; bugfix on 0.2.5.2-alpha.
- Minor bugfixes (correctness):
- Remove a nonworking, unnecessary check to see whether a circuit hop's identity digest was set when the circuit failed. Fixes bug 24927; bugfix on 0.2.4.4-alpha.
- Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
- Upon receiving a malformed connected cell, stop processing the cell immediately. Previously we would mark the connection for close, but continue processing the cell as if the connection were open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
- Minor bugfixes (directory authorities, IPv6):
- When creating a routerstatus (vote) from a routerinfo (descriptor), set the IPv6 address to the unspecified IPv6 address, and explicitly initialize the port to zero. Fixes bug 24488; bugfix on 0.2.4.1-alpha.
- Minor bugfixes (documentation):
- Document that the PerConnBW{Rate,Burst} options will fall back to their corresponding consensus parameters only if those parameters are set. Previously we had claimed that these values would always be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
- Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
- Minor bugfixes (exit relay DNS retries):
- Re-attempt timed-out DNS queries 3 times before failure, since our timeout is 5 seconds for them, but clients wait 10-15. Also allow slightly more timeouts per resolver when an exit has multiple resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
- Minor bugfixes (fallback directory mirrors):
- Make updateFallbackDirs.py search harder for python. (Some OSs don't put it in /usr/bin.) Fixes bug 24708; bugfix on 0.2.8.1-alpha.
- Minor bugfixes (hibernation, bandwidth accounting, shutdown):
- When hibernating, close connections normally and allow them to flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes bug 7267.
- Do not attempt to launch self-reachability tests when entering hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
- Resolve several bugs related to descriptor fetching on bridge clients with bandwidth accounting enabled. (This combination is not recommended!) Fixes a case of bug 12062; bugfix on 0.2.0.3-alpha.
- When hibernating, do not attempt to launch DNS checks. Fixes a case of bug 12062; bugfix on 0.1.2.2-alpha.
- When hibernating, do not try to upload or download descriptors. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
- Minor bugfixes (IPv6, bridges):
- Minor bugfixes (Linux seccomp2 sandbox):
- When running with the sandbox enabled, reload configuration files correctly even when %include was used. Previously we would crash. Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
- Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
- Allow the nanosleep() system call, which glibc uses to implement sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
- Minor bugfixes (logging):
- Fix a (mostly harmless) race condition when invoking LOG_PROTOCOL_WARN message from a subthread while the torrc options are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
- Minor bugfixes (man page, SocksPort):
- Remove dead code from the old "SocksSocket" option, and rename SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
- Minor bugfixes (memory leaks):
- Avoid possible at-exit memory leaks related to use of Libevent's event_base_once() function. (This function tends to leak memory if the event_base is closed before the event fires.) Fixes bug 24584; bugfix on 0.2.8.1-alpha.
- Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix on 0.2.1.1-alpha.
- Minor bugfixes (network IPv6 test):
- Tor's test scripts now check if "ping -6 ::1" works when the user runs "make test-network-all". Fixes bug 24677; bugfix on 0.2.9.3-alpha. Patch by "ffmancera".
- Minor bugfixes (networking):
- string_is_valid_hostname() will not consider IP strings to be valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
- Minor bugfixes (onion service v3):
- Avoid an assertion failure when the next onion service descriptor rotation type is out of sync with the consensus's valid-after time. Instead, log a warning message with extra information, so we can better hunt down the cause of this assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
- Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
- Fix a memory leak when a v3 onion service is configured and gets a SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
- When parsing the descriptor signature, look for the token plus an extra white-space at the end. This is more correct but also will allow us to support new fields that might start with "signature". Fixes bug 26069; bugfix on 0.3.0.1-alpha.
- Minor bugfixes (onion services):
- If we are configured to offer a single onion service, don't log long-term established one hop rendezvous points in the heartbeat. Fixes bug 25116; bugfix on 0.2.9.6-rc.
- Minor bugfixes (performance):
- Reduce the number of circuits that will be opened at once during the circuit build timeout phase. This is done by increasing the idle timeout to 3 minutes, and lowering the maximum number of concurrent learning circuits to 10. Fixes bug 24769; bugfix on 0.3.1.1-alpha.
- Avoid calling protocol_list_supports_protocol() from inside tight loops when running with cached routerinfo_t objects. Instead, summarize the relevant protocols as flags in the routerinfo_t, as we do for routerstatus_t objects. This change simplifies our code a little, and saves a large amount of short-term memory allocation operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
- Minor bugfixes (performance, timeouts):
- Consider circuits for timeout as soon as they complete a hop. This is more accurate than applying the timeout in circuit_expire_building() because that function is only called once per second, which is now too slow for typical timeouts on the current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
- Use onion service circuits (and other circuits longer than 3 hops) to calculate a circuit build timeout. Previously, Tor only calculated its build timeout based on circuits that planned to be exactly 3 hops long. With this change, we include measurements from all circuits at the point where they complete their third hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
- Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
- Avoid a crash when running with DirPort set but ORPort tuned off. Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
- Minor bugfixes (Rust FFI):
- Fix a minor memory leak which would happen whenever the C code would call the Rust implementation of protover_get_supported_protocols(). This was due to the C version returning a static string, whereas the Rust version newly allocated a CString to pass accross the FFI boundary. Consequently, the C code was not expecting to need to free() what it was given. Fixes bug 25127; bugfix on 0.3.2.1-alpha.
- Minor bugfixes (spelling):
- Use the "misspell" tool to detect and fix typos throughout the source code. Fixes bug 23650; bugfix on various versions of Tor. Patch from Deepesh Pathak.
- Minor bugfixes (testing):
- Minor bugfixes (unit test, monotonic time):
- Increase a constant (1msec to 10msec) in the monotonic time test that makes sure the nsec/usec/msec times read are synchronized. This change was needed to accommodate slow systems like armel or when the clock_gettime() is not a VDSO on the running kernel. Fixes bug 25113; bugfix on 0.2.9.1.
- Code simplification and refactoring:
- Move the list of default directory authorities to its own file. Closes ticket 24854. Patch by "beastr0".
- Remove the old (deterministic) directory retry logic entirely: We've used exponential backoff exclusively for some time. Closes ticket 23814.
- Remove the unused nodelist_recompute_all_hsdir_indices(). Closes ticket 25108.
- Remove a series of counters used to track circuit extend attempts and connection status but that in reality we aren't using for anything other than stats logged by a SIGUSR1 signal. Closes ticket 25163.
- Remove /usr/athena from search path in configure.ac. Closes ticket 24363.
- Remove duplicate code in node_has_curve25519_onion_key() and node_get_curve25519_onion_key(), and add a check for a zero microdesc curve25519 onion key. Closes ticket 23966, patch by "aruna1234" and teor.
- Rewrite channel_rsa_id_group_set_badness to reduce temporary memory allocations with large numbers of OR connections (e.g. relays). Closes ticket 24119.
- Separate the function that deletes ephemeral files when Tor stops gracefully.
- Small changes to Tor's buf_t API to make it suitable for use as a general-purpose safe string constructor. Closes ticket 22342.
- Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to avoid source code identifier confusion. Closes ticket 24467.
- The tor_git_revision[] constant no longer needs to be redeclared by everything that links against the rest of Tor. Done as part of ticket 23845, to simplify our external API.
- We make extend_info_from_node() use node_get_curve25519_onion_key() introduced in ticket 23577 to access the curve25519 public keys rather than accessing it directly. Closes ticket 23760. Patch by Neel Chauhan.
- Add a function to log channels' scheduler state changes to aid debugging efforts. Closes ticket 24531.
- Documentation:
- Improved the documentation of AccountingStart parameter. Closes ticket 23635.
- Update the documentation for "Log" to include the current list of logging domains. Closes ticket 25378.
- Add documentation on how to build tor with Rust dependencies without having to be online. Closes ticket 22907; bugfix on 0.3.0.3-alpha.
- Clarify the behavior of RelayBandwidth{Rate,Burst} with client traffic. Closes ticket 24318.
- Document that OutboundBindAddress doesn't apply to DNS requests. Closes ticket 22145. Patch from Aruna Maurya.
- Code simplification and refactoring (channels):
- Remove the incoming and outgoing channel queues. These were never used, but still took up a step in our fast path.
- The majority of the channel unit tests have been rewritten and the code coverage has now been raised to 83.6% for channel.c. Closes ticket 23709.
- Remove other dead code from the channel subsystem: All together, this cleanup has removed more than 1500 lines of code overall and adding very little except for unit test.
- Code simplification and refactoring (circuit rendezvous):
- Split the client-side rendezvous circuit lookup into two functions: one that returns only established circuits and another that returns all kinds of circuits. Closes ticket 23459.
- Code simplification and refactoring (controller):
- Make most of the variables in networkstatus_getinfo_by_purpose() const. Implements ticket 24489.
- Documentation (backport from 0.3.4.1-alpha):
- Correct an IPv6 error in the documentation for ExitPolicy. Closes ticket 25857. Patch from "CTassisF".
- Documentation (man page):
- The HiddenServiceVersion torrc option accepts only one number: either version 2 or 3. Closes ticket 25026; bugfix on 0.3.2.2-alpha.
- Documentation (manpage, denial of service):
- Provide more detail about the denial-of-service options, by listing each mitigation and explaining how they relate. Closes ticket 25248.
Comments
Please note that the comment area below has been archived.
May 23 01:18:54.000 [warn]…
May 23 01:18:54.000 [warn] tor_bug_occurred_(): Bug: src/or/circuitbuild.c:2772: onion_extend_cpath: Non-fatal assertion info || client failed. (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: Non-fatal assertion info || client failed in onion_extend_cpath at src/or/circuitbuild.c:2772. Stack trace: (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(log_backtrace+0x42) [0x2af1fa0be7f2] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(tor_bug_occurred_+0xca) [0x2af1fa0d92da] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(circuit_establish_circuit+0x11e6) [0x2af1fa00b7f6] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(circuit_launch_by_extend_info+0xb3) [0x2af1fa01cf23] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(circuit_build_needed_circs+0x34b) [0x2af1fa01eefb] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor [0x2af1f9f86e58] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(event_base_loop+0x805) [0x2af1fa13fc05] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(do_main_loop+0x426) [0x2af1f9f83586] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(tor_run_main+0x28c) [0x2af1f9f83b5c] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(tor_main+0x43) [0x2af1f9f7e483] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor(main+0x19) [0x2af1f9f7e319] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /lib64/libc.so.6(__libc_start_main+0xf4) [0x2af1fb12f9f4] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Bug: /usr/bin/tor [0x2af1f9f7e229] (on Tor 0.3.3.6 7dd0813e783ae16e)
May 23 01:18:54.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
That's https://trac…
That's https://trac.torproject.org/projects/tor/ticket/25692 and it seems this is almost ready to get merged.
torrc regressed 4 years with…
torrc regressed 4 years with this update? SOCKSPolicy lost IP6?
Please re-roll this update?
root@local [/etc/tor]# head torrc
## Configuration file for a typical Tor user
## Last updated 9 October 2013 for Tor 0.2.5.2-alpha.
root@local [/etc/tor]# diff -u torrc.orig torrc
--- torrc.orig 2018-05-23 10:28:34.865489493 -0500
+++ torrc 2018-05-23 02:34:48.000000000 -0500
@@ -1,5 +1,5 @@
## Configuration file for a typical Tor user
-## Last updated 22 December 2017 for Tor 0.3.2.8-rc.
+## Last updated 9 October 2013 for Tor 0.2.5.2-alpha.
## (may or may not work for much older or much newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
@@ -12,20 +12,19 @@
## Tor will look for this file in various places based on your platform:
## https://www.torproject.org/docs/faq#torrc
-## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't
-## configure one below. Set "SOCKSPort 0" if you plan to run Tor only
+## Tor opens a socks proxy on port 9050 by default -- even if you don't
+## configure one below. Set "SocksPort 0" if you plan to run Tor only
## as a relay, and not make any local application connections yourself.
-#SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections.
-#SOCKSPort 192.168.0.1:9100 # Bind to this address:port too.
+#SocksPort 9050 # Default: Bind to localhost:9050 for local connections.
+#SocksPort 192.168.0.1:9100 # Bind to this address:port too.
## Entry policies to allow/deny SOCKS requests based on IP address.
-## First entry that matches wins. If no SOCKSPolicy is set, we accept
-## all (and only) requests that reach a SOCKSPort. Untrusted users who
-## can access your SOCKSPort may be able to learn about the connections
+## First entry that matches wins. If no SocksPolicy is set, we accept
+## all (and only) requests that reach a SocksPort. Untrusted users who
+## can access your SocksPort may be able to learn about the connections
## you make.
-#SOCKSPolicy accept 192.168.0.0/16
-#SOCKSPolicy accept6 FC00::/7
-#SOCKSPolicy reject *
+#SocksPolicy accept 192.168.0.0/16
+#SocksPolicy reject *
Yes. Merge mistake? https:/…
Yes. Merge mistake?
https://gitweb.torproject.org/tor.git/tree/src/config/torrc.minimal.in?…
https://gitweb.torproject.org/tor.git/commit/src/config/torrc.minimal.i…
This was intended : "Use…
This was intended :
"Use minimal torrc in /etc and put the longer into usr/share/docdebian-tor-0.3.3.6-1"
- mv debian/tor/etc/tor/torrc.sample debian/tor/etc/tor/torrc
+ rm debian/tor/etc/tor/torrc.sample
+ cp build/src/config/torrc.minimal debian/tor/etc/tor/torrc
https://gitweb.torproject.org/debian/tor.git/commit/debian/rules?h=debi…
File "torrc.minimal" remained unchanged for many years in most branches (if not all). See also "torrc.minimal.in-staging" and "torrc.sample.in".
"We try to change torrc.minimal.in as infrequently as possible, since doing so makes the users of many packages have to re-build their torrc files."
https://gitweb.torproject.org/debian/tor.git/tree/src/config/README?h=d…
And it also prevents unattended upgrades. Let's hope this commit, will proove the above statement true. At last but not least :)
I wish the Debian package would stop interfering with /etc/tor/torrc, entirely. It does not look appropriate to me (?) and "apt full-upgrade" is also put on hold, every time, prompting if maintainer or user version should be applied/diffed/merged, or else. Even "include" files or folders still do not solve this, since they need at least one line change in torrc to call them. On all Debian hosts I maintain, that's the last package upgrade showing such a trap, I think.
Further, tor service is not restarted until that question is answered, which is really *not* great while connected... over Tor. I usually remember to program some service restart from another tmux, just before launching these upgrades. Or I cry-and-retry to connect the harder way if achievable, else I beg local folks to reboot the entire thing(s) for me.
Can / How / Should we update…
Can / How / Should we update this in Tails?
source code page cannot be…
source code page cannot be found.
It seems https://archive…
It seems https://archive.torproject.org/tor-package-archive/tor-0.3.3.6.tar.gz and https://archive.torproject.org/tor-package-archive/tor-0.3.3.6.tar.gz.a… are the things you are looking for?
how updating correctly when…
how updating correctly when you using tor as gateway on linux systems.
keep or updating torrc (os ask it)?
I try to build latest tor 0…
I try to build latest tor 0.3.3.6 from source under "x86_64 Cygwin".
Earlier versions did compile, I'm running now "Tor version 0.3.2.9 (git-9e8b762fcecfece6)."
Compilation now Fails with the following erros:
make all-am
make[1]: Entering directory '/cygdrive/f/tor-0.3.3.6'
CC src/ext/ed25519/ref10/src_ext_ed25519_ref10_libed25519_ref10_a-fe_0.o
In file included from src/ext/ed25519/ref10/crypto_int32.h:6,
from src/ext/ed25519/ref10/fe.h:4,
from src/ext/ed25519/ref10/fe_0.c:1:
./src/common/torint.h:214:2: error: #error "Can't define ssize_t."
#error "Can't define ssize_t."
^~~~~
./src/common/torint.h:237:2: error: #error "void * is either >8 bytes or <= 2. In either case, I am confused."
#error "void * is either >8 bytes or <= 2. In either case, I am confused."
^~~~~
./src/common/torint.h:241:2: error: #error "Missing type int8_t"
#error "Missing type int8_t"
^~~~~
./src/common/torint.h:244:2: error: #error "Missing type uint8_t"
#error "Missing type uint8_t"
^~~~~
./src/common/torint.h:247:2: error: #error "Missing type int16_t"
#error "Missing type int16_t"
^~~~~
./src/common/torint.h:250:2: error: #error "Missing type uint16_t"
#error "Missing type uint16_t"
^~~~~
./src/common/torint.h:253:2: error: #error "Missing type int32_t"
#error "Missing type int32_t"
^~~~~
./src/common/torint.h:256:2: error: #error "Missing type uint32_t"
#error "Missing type uint32_t"
^~~~~
./src/common/torint.h:259:2: error: #error "Missing type int64_t"
#error "Missing type int64_t"
^~~~~
./src/common/torint.h:262:2: error: #error "Missing type uint64_t"
#error "Missing type uint64_t"
^~~~~
./src/common/torint.h:269:2: error: #error "Seems that your platform doesn't use 2's complement arithmetic. Argh."
#error "Seems that your platform doesn't use 2's complement arithmetic. Argh."
^~~~~
./src/common/torint.h:277:2: error: #error "Can't define LONG_MAX"
#error "Can't define LONG_MAX"
^~~~~
./src/common/torint.h:287:2: error: #error "Can't define INT_MAX"
#error "Can't define INT_MAX"
^~~~~
./src/common/torint.h:299:2: error: #error "Can't define UINT_MAX"
#error "Can't define UINT_MAX"
^~~~~
./src/common/torint.h:309:2: error: #error "Can't define SHORT_MAX"
#error "Can't define SHORT_MAX"
^~~~~
./src/common/torint.h:367:2: error: #error "Can't define SSIZE_MAX"
#error "Can't define SSIZE_MAX"
^~~~~
make[1]: *** [Makefile:6513: src/ext/ed25519/ref10/src_ext_ed25519_ref10_libed25519_ref10_a-fe_0.o] Error 1
make[1]: Leaving directory '/cygdrive/f/tor-0.3.3.6'
make: *** [Makefile:3409: all] Error 2
I couldn't find any viable solution to those errors.
I opened https://trac…
I opened https://trac.torproject.org/projects/tor/ticket/26356 for you. Please provide further information as requested in the ticket otherwise it's hard to fix your issue, thanks.
When the expert bundle…
When the expert bundle update?
The expert bundles is built…
The expert bundles is built during the Tor Browser build. So, once the latter updates and picks up a new Tor version, there will be a new expert bundle.
New TBB for Firefox 52.8…
New TBB for Firefox 52.8.1esr?
Yes, we got a new one built…
Yes, we got a new one built and it is out, both for the stable as the alpha series.