Closed
Milestone
Tor: 0.3.3.x-final
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
250
- Travis permissions error: failed to write Cargo.lock
- Disable TLS1.3 when openssl bug 7712 is present
- hs-v3: Do not close RP circuits when deleting an ephemeral service
- libtorrunner: memory leak in tor_runner error path
- Heap use-after-free on git master dbb0abc9f1a174efdb65d581f5dbe46dbad2ebb5
- hs-v3: Don't warn so loudly when tor is unable to decode a descriptor
- Bug: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed in retry_all_socks_conn_waiting_for_desc at ../src/or/hs_client.c:268
- DataDirectoryGroupReadable enabled does not have effect
- FTBFS on GNU/Hurd: no PATH_MAX
- WARN: Saying "HTTP/1.0 405 Method Not Allowed\r\n\r\n" WARN: connection_mark_unattached_ap_(): Bug: stream (marked at src/or/connection_edge.c:2551) sending two socks replies? (on Tor 0.3.3.5-rc 81d71f0d41adf0d8)
- use correct CARGO_HOME in test_rust.sh
- client failed in onion_extend_cpath on Illumos/JoyentSmartOS
- Core Tor releases typo
- man page still says CacheIPv4DNS is on by default
- FetchUselessDescriptors also stops Tor from going idle
- CID 1435130: Incorrect expression (COPY_PASTE_ERROR)
- ::/128 is not the IPv6 equivalent of 0.0.0.0/0
- Integrate circuit max_cell_queue_size killer with DoS heartbeats
- Rust files not all included with Tor.
- Refactor circuit_build_failed to separate build vs path failures
- onion_extend_cpath: Non-fatal assertion info || client failed.
- Bridges don't work: Non-fatal assertion !(exit_ei == NULL) failed in onion_pick_cpath_exit
- Default for TOR_RUST_DEPENDENCIES is wrong?
- LZMA/ZSTD descriptor compression support
- RendPostPeriod and HiddenServiceAuthorizeClient are v2 only
- fix CID 1430932
- unable to resolve DNS requests from control port, regression
- Manual includes non-existant ExitPolicyDefault option
- Inconsistent underscore config options (for vanguard options)
- test all rust crates for realsies
- DDOS on HiddenService
- TROVE-2018-005
- Tor in-process restart fails to write auth cookie
- Fix win32 crash in bench.c
- Transparent proxy hangs after kernel update to 4.15.6-200.fc26.x86_64
- moria1 seg faults on testing relay reachability
- Transparent proxy stopped working after Linux kernel update to version 4.4.118 that fixes Spectre variant 1
- document how to allow partially failing builds in Travis CI
- Transparent proxy not working with linux kernel 4.15.6
- Log domain list is out of sync in tor.1.txt
- Create an official tor-rust-dependencies.git repository
- Assertion failure in scale_active_circuits
- Sandbox: Caught a bad syscall attempt (syscall poll)
- Rust implementation of protover code deviates from C in some cases
- Fix TROVE-2018-004: bad consensus can trigger null pointer crash.
- Infinite loop in Rust protover implementation (TROVE-2018-003)
- Spec/implementation deviation in C protover code
- DoS mitgation: improve documentation
- dos: Document torrc default values in the man page when not in the consensus
- Circuit cell queue can fill up memory
- dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed
- 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(), node)) failed.
- Check the calculations in cc_stats_refill_bucket using non fatal assertions
- dos: Avoid blacklisting Exit relays
- change of bandwidth accounting intveral from 4 to 24 hours results in unreasonable memory consumption
- Implement a way to tell if an IP address is a known relay
- Clarify 'recognized' field in tor-spec
- rephist: Remove unused counters in or_history_t
- Make geoip_client_cache_total_allocation() use geoip_client_history_cache_size
- Bug: src/or/dos.c:312: cc_stats_refill_bucket: Non-fatal assertion new_circuit_bucket_count >= stats->circuit_bucket failed
- Rust implementation of protover_get_supported_protocols() leaks memory
- KIST: Bug: scheduler_release_channel: Non-fatal assertion !(smartlist_pos(channels_pending, chan) == -1)
- geoip: Hook the client geoip cache into the OOM handler
- getrandom() syscall failure warning should be a notice and worded better
- Resolve TROVE-2018-002: bug 24700 KIST use-after-free can be remotely triggered
- hs: nodelist_recompute_all_hsdir_indices() is not used
- Remove commented functions in crypto module
- Update dir-spec.txt with recent consensus param additions
- 24902 fix breaks on clang
- TROVE-2018-001: null-pointer crash in directory authority protocol list code
- Add a test-rust make target to the Makefile
- protover_get_supported_protocols() should include Link=5 as of 0.3.1.1-alpha
- Wrap types in protover.rs
- string_is_valid_hostname() returns true for IPv4 addresses
- Tor 0.3.2 rejects connections to raw ipv6 addresses
- Update HiddenServiceVersion in tor.1.txt to only allow one of the HS version 2 or 3
- I think KIST can use hash tables much less.
- Call protocol_list_supports_protocol less often to save time and allocation
- Tor doesn't work when built with (unreleased) OpenSSL 1.1.1 built with enable-tls1_3
- sched: scheduler_notify_networkstatus_changed() calls select_scheduler() without the new consensus
- Bug: src/or/hs_descriptor.c:2357: hs_desc_encode_descriptor: Non-fatal assertion !(ret < 0) failed.
- Tor's DNSPort become unreliable after I upgraded to latest 0329 stable.
- Authorities crash in Shadow with 0.3.2.9 because it's 1970 due to new HS code
- channel: channel_tls_get_remote_addr_method() should return the "real_addr" of the connection
- vanguards bug: connection_ap_expire_beginning(): Bug: circuit->purpose == CIRCUIT_PURPOSE_C_GENERAL failed.
- connection_ap_expire_beginning(): Bug: circuit->purpose == CIRCUIT_PURPOSE_C_GENERAL failed
- tor-gencert says [warn] event_base_free_: no base to free
- Maybe load balance pinned middles?
- if (n_chan_id) in circuit_build_failed() can't fail
- Update dir-spec for new compression options
- Make geoip use channel_is_client so it ignores flapping relays
- Denial of Service mitigation subsystem
- Onion services should include basic intro/rend stats in their heartbeat logs
- MAX_REND_FAILURES is 1, but we will try three times
- v3 onion services don't respect MAX_REND_FAILURES
- Running out of disk space triggers BUG(ent == NULL) at consdiffmgr.c:1316
- Using %zu seems to break mingw :/
- Bug: Assertion cmux failed in circuitmux_get_policy at src/or/circuitmux.c
- Bug: Non-fatal assertion !(ent == NULL) failed in store_multiple at src/or/consdiffmgr.c
- Merge HS v3 prop284 into control-spec.txt
- consensus diffs stall Tor Browser launch for at least 20s or break it entirely if compiled with --enable-expensive-hardening
- UAF after updating `master` to 1dab8bae21bc32e5d4e3ff954f4919d6506ad2e1
- Enforce ipv4 + ipv6 capable exit
- test_rust fails on osx with "can't find crate for `libc`"
- smartlist.rs: do not use i8 interchangeably with libc::c_char
- Set a lower default MaxMemInQueues value
- Mark prop#283 as Accepted
- Reduce "Channel padding timeout scheduled" NOTICE messages
- Increase client idle and connection timeouts to reduce network load
- All relays are constantly connecting to down relays and failing over and over
- What version of Rust does Tor require for 0.3.2?
- tor_remove_file() should ignore NULL filenames
- (Sandbox) Caught a bad syscall attempt (syscall socket)
- Remove unnecessary heap allocations in Rust protover implementation.
- Loading ifc.ifc_buf using the new tor_free() causes undefined behaviour on x86_64 macOS
- Job for tor.service failed when /var/run is tmpfs
- sched: With KIST, a channel can be added more than once in the pending list
- Tor eats all mbufs on FreeBSD
- Make the default fallback weight in Tor 10.0
- Use ping ::1 on Linux when ping6 ::1 fails
- Simplify "did this option change" functions in config.c
- After I updated my relay to Tor 0.3.2.7-rc I got a large amount of Warn errors
- Avoid monotime_coarse_absolute_msec in channelpadding code
- Fix pretty printing of configure output for rust checks
- Update our Cargo.lock file to remove the deprecated and removed [root] section
- Log main loop iteration count as part of the heartbeat messages
- FREE_AND_NULL documentation uses different names for the macro parameter
- Fix memory-leaked event_base_once() users.
- Memory leak in tor-resolve
- Don't crash when restarting Tor in the same process
- options_transition_affects_guards() refers to an old function name in a comment
- rewrite_node_address_for_bridge() should set IPv6 preferences even if there is no ri
- rewrite_node_address_for_bridge() doesn't set rs IPv6 addresses
- Move a comment to relay_send_end_cell_from_edge()
- enable expensive hardening message is wrong with static library builds
- Bug: tor_gmtime_r overflow - gmtime(9223372036854775807) failed with error No error
- Coverity CID 1425934: FORWARD_NULL in circuit_stream_is_being_handled()
- Coverity CID 1425733: Calling "hs_parse_address" without checking return value
- sched: Add function to change scheduler state and always use it
- Make it clear that multi-relay operators are expected to set a working ContactInfo and proper MyFamily
- Remove the --quiet from our cargo build invocation
- When we hit MaxMemInQueues, make the log message more quantitative
- Add some consts to networkstatus_getinfo_by_purpose()
- Make set_routerstatus_from_routerinfo() set IPv6 unspecified addresses
- Cannibalizing a circuit should check that first hop is in our guard state
- Enable -Wnormalized=nfkc when available to avoid source code identifier confusion
- Fix TROVE-2017-013: Use-after-free in onion service v2 when rotating intro points
- Consider using other mach_*_time() functions for monotonic time on OSX
- Reliability: Make sure onion services don't publish until they have (nearly) all hsdirs' descriptors
- Reduce monotime_coarse_absolute_msec() usage
- Fix a confusing comment about tie-breaking in compute_routerstatus_consensus()
- Remove /usr/athena from search path in configure.ac
- Add logging backend for Android
- Remove dead code and doc regarding the old SocksSocket option
- Various spec fixes to dir-spec, rend-spec-v3
- Every _free() function should be a macro that sets the corresponding pointer to NULL.
- Fix TROVE-2017-012: Relays can pick themselves in a circuit path
- Clarify that the RelayBandwidth* options exclude directory fetches by relays
- Tor fails to start if %include
- Add a CacheDirectory option
- Keep parts of data directory in /var/cache instead of /var/lib
- We should specify what is means for a Tor version to be obsolete
- Update GettingStartedRust.md with new build instructions
- Fix TROVE-2017-011: An attacker can make tor ask for a password
- Fix TROVE-2017-009: Replay-cache ineffective for v2 hidden services.
- Tor keeps on creating new circuits even when it's idle
- prop284: Changes needed on the proposal
- rip out everything related to DL_SCHED_DETERMINISTIC
- Fix manual mistakes
- Exit flag should not depend on bandwidth
- GETCONF doesn't resolve "auto" settings
- channel_rsa_id_group_set_badness spends a lot of time in malloc/free
- Make a repository to hold our rust dependencies in a form Cargo can use
- uninitialized value in networkstatus_parse_vote_from_string() via fuzz_consensus.c
- Bug: shared_random.c:918: sr_generate_our_commit: Assertion my_rsa_cert failed; aborting.
- Add comments everywhere that C and Rust must stay in sync
- Protover.rs could use a better algorithm
- Wrap types in protover.rs
- Test all rust functions' behavior when called from C with bad UTF8
- Is proto required for alternate relay implementations?
- Make clients avoid retrying slow exits when they time out
- Add fedora packager contact to ReleasingTor.md
- node_get_ed25519_id() should check if the microdesc ed25519 id is all zero
- entry_guards_update_all() will pretend to update primaries even if sampled set is empty
- Refactor node_has_curve25519_onion_key() to use node_get_curve25519_onion_key()
- Race condition in LOG_PROTOCOL_WARN
- Use stdatomic counters where available
- Improve control-spec.txt
- Let programs call tor_main with a preconstructed control socket
- tor-spec: move IPv6 addresses from microdescs to microdesc consensus
- Implement a way to utilise tor's logging system from Rust code
- Clear the address when node_get_prim_orport() returns early
- Authorities: document what happens when relays have misconfigured IPv6
- Replace all exit() calls with return code style
- Make sure Tor can shut down via control port, and start again in same process
- Document a stable tor main function
- Authorities: Remove IPv6 addresses from microdescriptors
- Clients/Relays: Use IPv6 Addresses from microdesc consensus
- Authorities: Put Relay IPv6 addresses in the microdesc consensus
- Remove non-exponential backoff directory download implementation
- router_reset_descriptor_download_failures() doesn't actually reset descriptor downloads
- [HELP!] 7.5a5's(IIRC) Tor cause DNS disruption!
- Use node_get_curve25519_onion_key() in extend_info_from_node()
- prop224: tor_bug_occurred_(): Bug: src/or/hs_service.c:403: service_intro_point_new: Non-fatal assertion !(!ls) failed. (on Tor 0.3.2.1-alpha 290274dbb5428bc5)
- sched: channel_more_to_flush() is probably looking at the wrong queue
- channel: `outgoing_queue` and `incoming_queue` are always empty
- Make it easier for mobile app developers to embed tor
- improve AccountingStart manual entry
- Why does roflcopter have an empty protocol line in the consensus?
- Hibernation on period roll-over
- prop224: Missing tons of mds over time with a lurking client
- Add rendezvous point IPv6 address to client introduce cells
- Stop closing channels out from under OR connections in hibernate_go_dormant()
- prop224: Disconnects on long-lasting HS connections (possibly because of mds)
- Add ed25519 ids to torrc relay configs
- prop224: Specialize interface of hs_circuitmap_get_rend_circ_client_side()
- Sampled guards are not re-weighted when a new consensus arrives
- control_auth_cookie isn't deleted when tor stops
- BridgeAuth offline key mode seems broken
- Include ed25519 relay id keys in the consensus
- prop280: Finish privcount-in-Tor proposal (280)
- release checklist should include "make sure the new version got recommended"
- Circuit Build Timeout should apply at circuit completion
- Bug: outgoing relay cell sent from src/or/relay.c:836 has n_chan==NULL.
- Predict and build specific HS purpose circuits (rather than GENERAL)
- Circuit Build Timeout needs to count hidden service circuits
- Specify how PrivCount will work with Tor
- Our Rust code is always built in debug mode
- Implement protover in Rust
- prop224: Make the client/service extend properly to the IP/RP
- Add a KeyDirectory option to override location of $datadir/keys, and/or a cachedir option to override location of cached files.
- sandbox_intern_string(): Bug: No interned sandbox parameter found for /etc/tor/torrc.d/
- We bootstrap from different primary guards when we start with a non-live consensus and not enough guards in the state file
- Add a nice append-only stringbuffer, and refactor code to use it
- Tor 0.3.x clients won't use Guard-flagged relays as Guards if they don't have V2Dir, throwing off consensus position weights
- networkstatus_nickname_is_unnamed() can get ripped out
- Document which interface is used for DNS requests in the context of OutboundBindAddressOR/Exit
- apparent inconsistency in prop264
- Split node_supports_ed25519_link_authentication into two or three separate functions
- prop224: Add control port events and commands
- Your Guard is failing an extremely large amounts of circuits.
- Strange Warning: "Couldn't add re-parsed router: Some certs on this router are expired."
- EntryNodes is incompatible with IPv6-only bootstrap
- IPv6-only clients fetch microdescriptors from a small number of IPv6 fallbacks
- Mitigate guard discovery by pinning middle node
- Create a client/relay-side ReducedExitPolicy
- torspec lies about accepting both IPv4 and IPv6 for ORAddress lines
- Audit DisableNetwork, we_are_hibernating usage
- tor crashes with Assertion smartlist_get(rl->old_routers, idx) == sd failed
- Allow MapAddress .exit even if AllowDotExit is 0
Loading
Loading
Loading