Closed
Milestone
Oct 19, 2020–Feb 15, 2021
Tor: 0.4.5.x-stable
Stable release for 0.4.5.x
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
60
- Bug 0.4.5.5-rc ORPort relay (using both IPv4 & IPv6)
- 0.4.5 with unreachable autodetected ipv6 orport logs about testing every few minutes forever
- relay: Don't fail if AF_INET6 family is not supported
- Don't even warn when an ancient consensus says we're missing a protocol.
- 0.4.5 relay with autodetected unreachable ipv6 port says it's publishing but then doesn't
- test suite fails on hppa (0.4.5.5-rc)
- relay: Send back connection refused end reason on network reentry
- relay: Avoid false positive on network reentry detection
- Add consensus param to enable network re-entry at Exit relays
- CID 1472584: Error handling issues in check_descriptor_ipaddress_changed()
- Crash on MetricsPort when prematurely terminating socket
- Can't migrate ORPort options from 0.4.4.6 to 0.4.5.3-rc
- wrong IPv6 is used
- Assist dir auths with vote visibility
- dirauth: IPv6 sybil detection should not use /64
- Fix issue when using FALLTHROUGH with ALL_BUGS_ARE_FATAL
- 0.4.5 dir auths complain often of missing proto and missing identity-ed25519 elements
- v3 onion services require a "live" consensus to publish or fetch
- configure summary misleadingly indicates library support based on enable, not have
- Non-fatal assertion !(smartlist_len(outdated_dirserver_list) > TOO_MANY_OUTDATED_DIRSERVERS)
- Non fatal assertion in relay_addr_learn_from_dirauth when Address is set to an internal non-public address
- Loading statistics from a file for extra-info descriptors does not correctly determine the last statistics block
- Compiling tor on master (2bfb76b927111824a2051d09b1f5542ee58e2a6f) breaks on Android
- Remove DirCache=1 from supported version list
- New address disovery (IPv4 and IPv6) make it impossible to run a local lan or localhost bridge or relay
- Downgrade or fix what is triggering some rendezvous circuit related warning in client log files
- Include the IPv6 address in the descriptor that is going to be tested for self reachability
- Looks like we broke `DirPort auto`?
- Tor man page doesn't mention !badexit
- Fix typos found with codespell
- Logs spammed by address changes while it did not happen
- SocksPort with IPv6 address is silently ignored
- Test failures with Fedora 33
- tracing-instrumentation-usdt fails to build: error: use of undeclared identifier 'tor_circuit'
- tracing-instrumentation-lttng doesn't build: 'core/or/lttng_circuit.inc' file not found
- Build failure on macOS on master
- ExitNodes not respected on all websites
- main: The --dbg-dump-subsystem-list is off by one
- Bug: connection_edge_send_command failed while sending a SENDME. Circuit probably closed, skipping. at 0.4.5.0-alpha-dev 228ac47c2cc2625e)
- Implement proposal 318: "Limit protover values to 0-63"
- Implement proposal 315: "Updating the list of fields required in directory documents"
- Link Tor's code into one big .a file.
- Tor ./configure fails when --enable-static-libevent and --enable-static-openssl when cross compiling mingw target
- Unable to build tor statically (no linkable openssl found)
- Tor client could not re-connect to a bridge which removed its obfs4 feature
- Sandbox failure when adding an extra %include file.
- Add nonfatal_once assertion about is_canonical assertion in `circuit_deliver_create_cell()`
- Bug: Bridge obfs4 0.4.5.0-alpha-dev rebuilding descriptor (source: METHOD=NONE) | Don't know my address while generating descriptor
- relay: IPv4Only ORPort without any IPv6 address configured spam logs
- stats: Create a stat exporter port for monitoring purposes
- Inbuf for outgoing SOCKS 4 proxy not cleared before reading from OR connection
- log rotation for /var/log/tor/debug.log did not close handle to old file after compression
- Static building tor with openssl does not work
- BUG: Non-fatal assertion info failed in onion_extend_cpath at src/core/or/circuitbuild.c:2663. (Stack trace not available) (on Tor 0.4.1.5 439ca48989ece545)
- Tor adds trailing space character to log events
- When ClientTransportPlugin is missing, tor connects directly to bridge addresses, even if they have a transport name
- HSDirs should publish some count about new-style onion addresses (v3 metrics)
- Do any controllers still use getinfo network-status?
- we should log an unmistakeable warning when --disable-asserts-in-tests is enabled
- If only a working static OpenSSL is available, ./configure fails
Loading
Loading
Loading