Closed
Milestone
Tor: 0.4.0.x-final
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
198
- tor can overrun its accountingmax if it enters soft hibernation first
- Bug: ../src/lib/process/process_unix.c:265: process_unix_exec: Assertion line should be unreached failed; aborting.
- Redundant build exclusion not working corrently on travis
- Bug stracktrace when pluggable transport cannot bind to port
- heap-use-after-free src/feature/nodelist/routerlist.c:704 in router_get_by_descriptor_digest
- Undefined behavior in tor_vasprintf()
- Memory leak on invalid CSV_INTERVAL value
- circuit_mark_for_close_(): Bug: Duplicate call to circuit_mark_for_close at ../src/feature/hs/hs_service.c:3166 (first at ../src/feature/hs/hs_service.c:2385)
- Every few hours, relays [warn] Received circuit padding stop command for unknown machine.
- Use MAP_INHERIT_NONE/ZERO if available instead of crashing on assertion failure
- make shellcheck expects scripts in the build directory
- Document that MapAddress is automatically strict, but does not handle redirects
- when reloading a consensus with a CRLF, log at notice.
- test failure: dir_handle_get/status_vote_next_bandwidth
- Update the Tor version for bandwidth-file-digest in torspec
- Actually include the bandwidth file digest in the vote
- Refactor handle_get_next_bandwidth() to use connection_dir_buf_add()
- torrc no longer accepts space in executable paths
- Test failure due to memory leaks in shared-random unit tests: long-term fix
- Decrease probability of stochastic failures in test-slow
- Fix an incorrect comment about calling FreeLibrary()
- channelpadding_timers test failed on tor-0.3.5.8
- APPCRASH of tor.exe on Windows when PT bootstrap is cancelled
- Tor nightly fails to build for Windows
- Coverage fails on master
- Regression: map_anon_nofork test is breaking jenkins on some platforms
- util/map_anon_nofork test fails on macOS
- Division by zero: undefined behaviour in circuitpadding/circuitpadding_sample_distribution test
- Tor from Git on FreeBSD: cc src/test/test-slow leads to "/usr/bin/ld: error: unable to find library -levent"
- KIST does not check the right channel's sched_heap_idx when readding channels
- Broken circuitpadding unittests on appveyor
- Put git branch-maintenance scripts into scripts directory
- add an ActiveOnStartup config option
- Update bandwidth-file-spec.txt with the country keyword
- conn_proxy reported instead of conn_pt
- Add units to the bandwidth key-values in the bandwidth file specification
- Inspect circuit queue during padding decisions
- 32-bit warnings in test_circuitpadding.c
- Fix TROVE-2019-001 (KIST can write above outbuf highwater mark)
- Expect some gmtime/localtime() failures on windows, don't log bugs from tests.
- do not LOG_ERR from test_address_get_if_addrs6 when there is no ipv6
- (Sandbox) Caught a bad syscall attempt (syscall getsockopt)
- Update dir-spec with the correct Tor version when bandwidth-file-digest is merged
- Intermittent test failure in circuitpadding/circuitpadding_wronghop
- tor man page doesn't mention isolating between socksports
- Run stochastic tests faster, log better message when they fail
- Shellcheck: chutney-git-bisect: use -n instead of ! -z
- WTF-Pad needs a changes file entry
- Document tor_ersatz_socketpair() and the functions it calls
- Close stdout pipe on error in process_unix_exec (was double closing stdin pipe)
- test_hs_service: CID 1442277: Resource leaks (RESOURCE_LEAK)
- Update dir-spec observed bandwidth to 5 days
- git pre-commit hook that runs 'make check-spaces' and 'make check-changes'
- fix typo/mispaste in BOOTSTRAP_STATUS_AP_CONN_PROXY summary text
- update control-spec.txt for new bootstrap phases
- distinguish PT vs proxy for real in bootstrap tracker
- rep_hist_log_link_protocol_counts() only knows about 4 link protocols, but Tor has 5
- Document --version's actual output
- PT users still have a jump-to-80% problem
- Fix a few scan-build warnings in the unit tests
- Discard strcmp_len()
- parse_short_policy() could be faster
- Remove memset() from get_token_arguments.
- Use new subsystems API for initializing the process subsystem
- Use K/V parser for handling PT LOG and STATUS messages
- DROPOWNERSHIP command
- Allow HeartbeatPeriod of less than 30 minutes in testing Tor networks
- Speed up parsing RSA onion keys from microdescriptors
- confirm hypothesis re PT jump-to-80%
- Fuzzer to check for round-trip encoding/decoding on various types.
- ControlPort has undocumented behavior
- Bug 3.5.5: src/feature/dircache/consdiffmgr.c:278: cdm_diff_ht_check_and_note_pending
- Remove deprecated ControlPort commands from GETINFO info/names listing
- Implement a K/V parser library
- log bootstrap tag name for easier troubleshooting
- doc: cached-routers has been gone for a long time
- Allow relays to serve future consensuses
- Improve general WTF-PAD code quality and maintainability
- Clean up PADDING_TODO.txt
- Pad on specific circuit purposes + ltups
- Resolve TROVE-2018-006
- Should we remember dormant state on restart?
- use documentation IP ranges for documentation (manpage)
- TLS internal error running Tor 0.3.4.9 on Debian Buster (OpenSSL 1.1.1a)
- Can't parse networkstatus consensus time
- Log is filled with OpenSSL errors
- will WTF-PAD impair bandwidth scanning?
- bandwidth-file-spec.txt: bandwidth-avg is not calculated from any bandwidth burst option
- Spurious coverity memory leak error in memoize_protover_summary()
- Various comment fixes
- Mark outdated dirservers in reasonably live consensuses
- test: test_rebind.py doesn't use a temporary a DataDirectory
- hs: Mention in the manpage that Sandbox and adding a service with the control port fails
- Crash in memoize_protover_summary() when cache is full
- Tor's Travis should print the python version after installation
- Complain if net.inet.ip.random_id is not set on FreeBSD-based servers
- Update "ReleasingTor.md" to match current practice
- Actually use zstd on Appveyor
- Try Ubuntu xenial builds on travis
- Update control spec with items from "extra dormant" code
- Tests for 'extra dormant' code
- Make the new "extra dormant" code configurable
- Add a timed "wakeup handler" for hibernation
- Move control_per_second_events() into a separate callback.
- The ns consensus isn't explicitly ns in the network-status-version line of flavored consensuses
- extra-info-digest's sha256-digest isn't actually over the same data as the sha1-digest
- Update bandwidth file headers in dir-spec
- Make sure our .may_includes files describe a noncircular dependency structure
- Replace TODOs in bandwidth file spec with Tor versions
- Specify bandwidth-file-hash in torspec
- Nyx forces Tor error: sandbox_getaddrinfo(): Bug: (Sandbox) failed to get address
- Audit ROLE_ALL callbacks to either have a way to turn them off or relax them
- Implement a way to enable/disable the network participant role
- Split ROLE_ALL into new roles and make it always on role
- Make most periodic events turn themselves off when Tor is dormant, sleeping, etc.
- Make a "subsystem manager" API to handle module setup/teardown/etc
- accept a reasonably live consensus for path selection
- Log the Tor version before running the unit tests
- Implement proposal 298-canonical-families.txt
- Should Tor 0.3.5 be the last 0.3.x since it's an LTS?
- CID 1440805: Memory leak in configured_nameserver_address() due to #21900
- verify guard selection consensus expiry constraints
- doc: Add doc/HACKING/Maintaining.md document
- Unparseable microdescriptor on public relay
- Compile-time assertion
- spec: Add to control-spec.txt some pluggable transport events
- spec: Add to pt-spec.txt control messages going back to main process (tor)
- Signal mechanism from PT processes to Tor
- Handle output from PT processes with the event loop
- Realphabetize list of tests
- Merge original WTF-PAD branch
- Tor shouldn't set Content-Type: application/octet-stream when compressing results
- fix docs in workqueue.c
- Update key/values in the bandwidth file spec
- remove unsafe block from cstr! macro
- Fix the missing unpack function in mmdb-convert.py
- Run shellcheck as part of "make check"
- Run another memory profile in late 0.4.0 to figure out how much memory we saved.
- Collect feedback on mobile DisableNetwork API; resolve issues.
- shellcheck: updateRustDependencies.sh issues
- shellcheck: run_calltool.sh issues
- shellcheck: run_trunnel.sh issues
- shellcheck: cov-diff issues
- shellcheck: coverage script issues
- shellcheck: scan-build.sh issues
- shellcheck: chutney-git-bisect.sh issues
- craft a git pre push hook that declines to receive fixup! commits?
- Consider no longer calling routerlist_remove_old_routers() from check_descriptor_callback()
- Tors with cached consensuses can't upgrade to a version that stops supporting a required protocol
- Update bandwidth-file-spec with scaling methods
- add len argument to consensus parsing functions
- add unit tests for tokenize_string() and get_next_token()
- Use trunnel to parse and generate SOCKS wire format in tor-resolve
- When ClientPreferIPv6ORPort is set to auto, and a relay is being chosen for a directory or orport connection, prefer IPv4 or IPv6 at random
- stop reporting "internal paths" during bootstrap
- require torrc to be UTF-8
- Authorities should reject non-UTF-8 in relay descriptors
- Store family lists more efficiently
- Rework NETINFO cell parsing and generation with trunnel
- Use mmap to hold our cached consensus, when we even need it stored in RAM at all.
- Perform fewer allocations in summarize_protocol_flags()
- add API for allocating aligned memory
- track "first" OR_CONN
- report initial OR_CONN as the earliest bootstrap phases
- gather feedback re decoupling bootstrap progress numbers from BOOTSTRAP_STATUS enum values
- report connection to PT SOCKS proxy separately from OR connection
- Privcount blinding and encryption: add rustfmt CI check
- Privcount blinding and encryption: Safety fixes
- Privcount blinding and encryption: doc fixes
- Privcount blinding and encryption: type fixes
- Implement proposal 293: "Other ways for relays to know when to publish"
- Enumerate unresolved issues that will need to be solved for a WTF-pad deployment
- Solve histogram issues for WTF-Pad
- Updated version of the WTF-pad proposal
- Profile-driven work to reduce memory usage, focusing on clients and mobile.
- count_acceptable_nodes() would be more accurate using node_has_preferred_descriptor()
- Tor relays publish a new descriptor but authorities drop it because they think it's only cosmetically different, and then the relay waits 18 more hours to publish, thus falling out of the consensus
- Report intermediate PT bootstrapping status
- Ensure WTF-Pad padding comes from the expected hop
- Finalize controller interface for idleness
- Add "idleness" interface support in Orbot
- Remove now-unnecessary Rust linking workaround
- Fuzzy match the fallback whitelist
- Update fallback whitelist in late 2018
- Clients should check IPv4 and IPv6 subnets when choosing circuit paths
- Make v3 single onion services parse and use IPv6 introduce link specifiers
- Memory profiling of Tor on Android device
- Make v2 and v3 single onion services retry all failed intro and rend connections with a 3-hop path
- expired consensus causes guard selection to stall at BOOTSTRAP PROGRESS=80
- tor_addr_parse is overly permissive
- gather info on jump-to-80% issues
- evdns fails when resolv.conf is missing, but succeeds when resolv.conf is empty
- DirAuths should expose bwauth bandwidth files
- Relay crash when reloading and resolv.conf is empty
- "Hash of session info was not as expected" should be log_protocol_warn
- Add a new logging domain for transport proxies
- Internal error
- Implement Adaptive Padding or some variant and measure overhead vs accuracy
Loading
Loading
Loading