Closed
Milestone
Tor: 0.2.2.x-final
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
301
- Update to June GeoIP database
- Update to May GeoIP database
- Update to April GeoIP database
- Update to March GeoIP database
- Update to February GeoIP database
- Update to January GeoIP database
- Backport A1-less GeoIP database
- Tor involuntarily sets TLS session tickets
- Tor Ignores Exit nodes
- use after free crash after "eventdns rejected address [scrubbed]"
- Crash bug in tor_timegm
- compare_tor_addr_to_addr_policy assertion error
- tor 0.2.2.38 release notes list extra item
- Possible timing side-channel in router selection
- Out-of-bounds read in networkstatus_parse_vote_from_string()
- Review every commit of Sebastian
- Review every commit of weasel
- Update to June GeoIP database
- Tor sends a badly formatted string through the controlport
- Tor v2 handshake does not work with openssl 1.0.1
- Be more strict about rejecting pre-handshake data in 0.2.2
- A couple of compile warnings with clang 3.1
- Crashing Tor with SETCIRCUITPURPOSE
- Update to May GeoIP database
- Safe cookie authentication failure replies do not end with a CRLF
- rend_parse_client_keys() prints stack in logs if base64_decode fails
- rend_service_introduce() asserts circuit->rend_data before checking for proto violation
- Update to April GeoIP database
- HttpsProxy sometimes ought to set Host: header
- ides has relocated and become turtles
- BridgePassword would be insecure if anybody used it
- #5090 allows post-auth heap overflow
- net-misc/tor-0.2.2.35 cored
- parse_http_time is borked
- Require a threshold of exit nodes before believing we can build circuits
- Never use a bridge-purpose node as an exit
- Building Tor with --enable-openbsd-malloc gives compile warnings
- ExitNodes setting sometimes ignored for user traffic
- Man page entry for MaxCircuitDirtiness is incomplete
- Implement ‘safe cookie authentication’ in Tor
- parse_config_line_from_str accepts broken hex values
- “We're missing a certificate” message should not be at notice level
- Executable paths for shasum/openssl not protected against whitespace
- 0.2.2.35 doesn't cache microdescriptors
- TBB for Windows plus Kaspersky 2012 equals BSOD
- Relative paths for auth cookie
- Error in log message
- A directory cache will never purge some old descriptors
- Log message contains typo
- HSes could join a client's rend circ before the INTRODUCE_ACK arrives
- Tor Client Bug: "connection_stop_reading: Assertion conn->read_event failed; aborting."
- getsockname in connection_handle_listener_read should be getpeername
- Possible flaws in sockaddr validation in connection_handle_listener_read()
- compile warning on osx 64bit for AuthDirFastGuarantee
- tor_accept_socket(): incosistency in code
- tor_addr_port_lookup(): addr_out filled with random bytes if transient failure
- tor_dup_addr(): buf[] uninited for some cases
- Compile warnings for maint-0.2.2 on Windows
- assign_onionskin_to_cpuworker is too expensive
- parameterize bandwidth cutoffs for Guard and Fast flags
- Assertion at startup on Windows 7 when socketpair fails
- Compile warnings when using --disable-threads
- "[warn] Hidden service with no ports configured; ignoring." should print HiddenServiceDir
- rend_client_any_intro_points_usable leaks an extend_info_t
- Tor clients without geoip DB log that they are configured to collect stats
- netinfo cells declare canonical address for the remote OR, not actual address of the conn
- 0.2.2 relays crash without geoip files
- Updated Tor crashes on Win7/x86_64
- fingerprint example in man page is mangled
- Duplicate call to connection_mark_for_close at command.c:1068 (first at command.c:1002)
- memory leak for hidden service?
- Circuit in CIRCUIT_PURPOSE_C_INTRODUCING with no rend_data
- Bridges should not perform DNS self-tests
- Windows 6.2 is Windows 8
- Bridges should switch to using begindir
- Tor 0.2.2 CBT notices are confusing users
- Iran filters Tor by ssl handshake, Sept 2011
- '--service install' does not prevent Tor from running normally
- Enable DirReqStatistics and ExtraInfoStatistics in 0.2.2.x?
- tor 0.2.2.32 crashes with SIGSEGV on SSL_CIPHER_get_name
- tor 0.2.2.32 dies in assert on reloading config when TrackExitHosts was used
- Tor 0.2.2.32 no longer cross compile (to iOS)
- Controlport behavior changed in 0.2.2.32 - CookieAuthentication now required to access control port
- write release notes for 0.2.2 stable
- Man page does not say that HiddenServiceDir must already exist
- Tor can't create the ControlPortWriteToFile file if it is to be placed into the not-yet-existant datadir
- Please report the following error message to the Tor developers at bugs.torproject.org: ""
- Consistent daily crash on Mac OS X 10.7 / Lion
- Stability on Windows 7
- Building Tor on Mac OS X Lion
- TOR high CPU then crashes
- Assertion failure in start_writing_to_file
- Unable to query fingerprint when there's no connection
- Tor sends a RESOLVEFAILED event when a reverse lookup succeeds.
- online version of manpage strangely formatted
- GETINFO events/names returns incomplete list of events
- Minor comment issues
- Bad State Parsing
- Revert or repair bug2355 changes
- connection_printf_to_buf is crazypants bizarre!
- ControlSocketsGroupWritable option is not compatible with User
- DNS resolver sends empty reply to unsupported query
- unit tests failure on maint
- Overzealous descriptor regeneration bug remains
- Edge case lets us still use an unconfigured bridge
- Incorrect log message in token_check_object
- SIGNAL NEWNYM should clear the last_hid_serv_requests table
- crypto_rand_int() should be returning an unsigned int
- Tor does not complain if the user specifies two HSes with the same HiddenServiceDir
- segmentation fault when setting "StrictNodes 1" in torrc
- Libevent callbacks should take sockets as evutil_socket_t, not int
- control-spec.txt describes HiddenServiceOptions incorrectly
- relays should log why they are making a new descriptor
- Setting BridgeRelay Triggers Assertion Failure
- +LOADCONF control port command is not documented in control-spec.txt
- OrPort auto Errors on Start
- seg fault in 0.2.2.26-beta when adding bridges
- new warnings with gcc 4.6
- After you setconf a bridge you can still reuse old circuits
- Try refetching bridge descriptors each second, not each ten seconds
- smartlist_string_num_isin's buffer is too short
- Return value of crypto_pk_get_digest for v3 legacy keys is ignored
- circuit_list_path_impl() says 'exit' for internal circs
- Implement 'SocksPort auto' and 'ControlPort auto'
- Allow a Tor process to be ‘owned’ by a controller process
- We shouldn't log nodes by nickname
- git 29e0d708 broke LastWritten state entry
- fix a few clang-static analyzer complaints in 0.2.2
- Put out Tor 0.2.2.x stable
- Rejected vote from <ipaddr> ("Duplicate discarded")
- Caches should no longer cache v2 networkstatus documents
- Mismatched accounting interval: moved by 90.32% when no DST changed
- setconf clears bridge descriptor refetch timers
- DNS update causes Tor to fail
- relays don't ever checkpoint their state file
- clear_trackexithosts_mappings() looks at the wrong source for its suffix
- Allow ControlSocket to be group writable
- Tor doesn't expand ~ in Log config options
- Tor network scanning?
- rend_parse_v2_service_descriptor checks wrong length
- SIGNAL DUMP fails on FreeBSD
- Demote “No current certificate known for authority” log messages to level info
- trivial fix for compile warnings in 0.2.2.x
- use of SO_REUSEADDR socket option, was: Error binding network socket: Address already in use
- Resolve or postpone all XXX022/XXX021 items
- Use cbt results when deciding to launch parallel introduction circuit?
- Wrong source port for dns replies when query is sent to an alias interface
- Bug: Duplicate call to connection_mark_for_close
- Send stream-level sendme when outbuf is low: don't wait for it to empty!
- Tor limits HttpProxyAuthenticator values to 48 characters
- Trivially incorrect warning in rend_parse_v2_service_descriptor
- Multiple bogosities in rend_cache_lookup_v2_desc_as_dir
- libevent2 problems on CCC tor servers
- Simplify hid_serv_responsible_for_desc_id
- TunnelDirConns option affects hid_serv_get_responsible_directories
- When we conclude a relay is unreachable, we give it free uptime
- Relays can trick authorities into assigning the hsdir flag early
- BandwidthObserved higher than BandwidthBurst
- Tor doesn't compile under LLVM/clang with --enable-gcc-warnings
- authority received unparseable routerstatus entry
- document Roger's Tor release process and release notes process
- get_interface_address6() fixes
- Make the interval to become a hsdir a little longer
- tor client crashed when using bridges
- eventdns complains about IPv6 nameserver in resolv.conf
- Bridge authority crashes on SIGHUP
- Tor will use an unconfigured bridge if it was a configured bridge last time you ran Tor
- bridge users who configure the non-canonical address of a bridge switch to its canonical address
- When locking a file on windows, EACCESS tells us we have it locked already, not EDEADLOCK
- Tor describes HTTPS proxy 403 errors as 'unexpected status code'
- Some relays without dirport have dirreq-(write|read)-history in their extrainfo desc
- 0.2.2.x manpage mentions country codes for 0.2.2.x EntryNodes option
- A bunch of hidden service warnings should be protocol warnings
- Tor should tell us which geoip file it is parsing
- check_signature_token broken in merge commit ed87738ede789fb
- Please add cbtnummodes to dir-spec.txt
- Tor can choose a relay as both entry and exit node for a circuit
- rend_cache_store(): We already have a v2 descriptor for service xxxxx
- RephistTrackTime missing from the man page
- Detect failed allocations from openssl
- tor memory not freed at exit
- Sync relay's policy with published descriptor.
- evdns_base_resolve_* macros are bogus
- Windows ASLR is not enabled for tor.exe, and DEP should be forced
- ReachableAddresses ignored when playing with bridges using Vidalia
- Clarification of the ReachableAddresses option
- Change UseBridges to prevent any access attempts of public tor network
- Failing to write state file means you try every second
- Check for signed size_t during configure
- Possible integer overflows in base32_encode, base32_decode
- SOCKS client cannot handle responses longer than 128 bytes
- circuit_build_times_disabled() and others missing function comments
- sketchy integer casting in circuit_build_times_shuffle_and_store_array
- var_cell_t with payload_len 0 risky
- Missing sanity checks for cbtnummodes consensus parameter
- automake 1.6.3 leaves src/common/OpenBSD_malloc_Linux.c out of tarball
- Duplicate call to connection_mark_for_close
- TorTestingNetwork vs. GETINFO config-text
- Man page should explain log domains; log domains should be usable
- Stream starvation due to activation order in circuit_resume_edge_reading_helper()
- Tor clients and authorities do not check bad_exit flag w/ consensus weights
- Exclude exit-port statistics from extra-info descriptors
- Handle the case when we can't generate descriptors
- Possible reentrant calls to libevent from libevent logging callback
- Control Protocol Spec Error, Grammars Use Outdated Production ServiceID
- router_rebuild_descriptor(): Bug: Couldn't generate extra-info descriptor
- Document graceful shutdown better.
- Typo in Tor manpage
- Annotation rules not adequately enforced.
- Tor Wakes Up from Hibernation Day 1 of Period
- Crash while checking whether directory_crashes_dir_info()
- HSAuthoritativeDir man page entry is incomplete
- Remove restriction to not send relay_early for rend circs
- Bridges can specify a DirPort
- Capping descriptor build times notice log
- rate-limit "Your application is giving Tor only an IP address" warning
- Bogus comments in tortls.c
- Documentation of BridgeRelay and PublishServerDescriptor is incorrect
- please merge Tor packaging changes
- when your bridges go down, you don't optimistically retry
- Bug: Circuit somehow completed a hop while the network was not live
- Warning from libevent, then Tor doesn't work
- Tor 0.2.2.16-alpha seg faults
- entry nodes marked bad if we don't have their descriptor when we parse the consensus
- networkstatus_check_consensus_signature() prints wrong stats
- LoadLibrary used without restrictions for search path
- Bw Weights error 1 for case Case 3b
- replace bwconnrate/burst consensus params with new names
- Helper functions {get,set}_uint{16,32,64}() are not used
- circuit_resume_edge_reading_helper is highly unfair
- Hidden service fails after getting new v2 descriptor
- It's hard to specify a really long *Nodes option
- Cell statistics warn when being enabled while Tor is running
- Update to September 1 geoip database
- Out of tree builds don't work
- Choosing bridges by bw is problematic
- We should launch a reachability test immediately if a router changes IP or port
- "Failed to find node for hop 0 of our path. Discarding this circuit." log spam after guard went down
- Assertion n_to_skip + n_to_free == freelists[i].cur_length failed
- Relays should store observed bandwidth in state file
- many "warning: 'struct in_addr' declared inside parameter list" when compiled on OpenBSD 4.8
- run_connection_housekeeping() closes circuits early
- Fix compiling Tor with --with-dmalloc
- Fix memory leaks introduced between 0.2.2.13 and 0.2.2.14
- published new server descriptor but authorities dropped because cosmetic
- Frequently repeated [Warning] Weighted bandwidth is 0.000000 ... when using bridges
- Restore support for building Tor in non-Unicode Windows installations
- Wake-up from Hibernation Occurs Day 1 Each Month
- Counting circuit timeouts when we can't establish any TLS connection
- Hidden Service Servers complain about ancient circs
- Circuit build timeout code is recording cannibalized circ times
- Control port no longer sends CIRC TIMEOUT events
- Decide what to do with the debian/ directory in Tor
- tor misparses libevent 1.4.14b-stable on bsd
- Fix compilation with mingw and OpenSSL 0.9.8m+
- exit relays don't consider local cell queue when hearing sendme
- Tor build fails with zlib 1.2.5 on MacOS X
- RESOLVE control port command code path is incorrect
- segmentation fault on 0.2.2.13-alpha
- Document what happens if options are defined more than once
- ExcludeNodes isn't document as being broken.
- log does not record at NOTICE level when Tor is really ready
- Generated a synthetic timeout LESS than the current timeout
- Flood of "Received http status code 404" Warning
- tor stopped publishing descriptor
- Reachability Testing passes, yet Relay is marked as down by authorities
- Exits tracked with TrackHostExits should not reset on hup
- Low value for Xm gives high build timeout
- FAIL test.c:517: assert(fabs(circuit_build_times_cdf(...
- Unable to get Tor to compile using OpenSSL 1.0.0-beta5 on Debian Lenny
- Suggestion: Adding an explanation on dir-spec
- Authority that doesn't make a consensus never fetches one from elsewhere
- CircuitBuildTimes should have an option to disable
- networkstatus warning comes out of nowhere
- Tor allows non-ASCII chars in contact line
- routerlists read from torrc not concatenated
- stop calling getsockname if accept returns a bad address
- Bridge crash
- Tor falsely believing to be offline
- Fluxe3 is not a guard
- mapaddress broken
- manpage doesn't talk about mbytes and friends
- Renegotiation bug still present on OpenBSD 4.6 stable
- Sending useless relay cells after the destroy cell
- Segfault in unit tests on Mac OS X Panther
- Tor fails to load auth-certs
- bug in networkstatus.c using 0.2.1.20
- If bridge authority is unreachable, client doesn't fallback to bridge
- (*chp)->next assertion fail?
- PublishServerDescriptor allows options 0 and 1 simultaneously
- No way to specify a GeoIP country code miss in ExcludeNodes etc.
- Warning about using an excluded node for exit
- rate-limit MaxOnionsPending warns
- Hidden services fail to load if you have a stale descriptor
- Different TLS certs for incoming vs outgoing
- Crash in closing tls connection
- Tor's once-per-second events are not quite once-per-second?
- With BridgeRelay 1 and ORPort 0, things go bad
- If you hup tor while it's hibernating, it rebinds its ports
- Authorities assign Running flag to hibernating relays?
- libevent "error" causes Tor not to start at all
Loading
Loading
Loading