{5} Accepted, Active Tickets by Owner (Full Description) (110 matches)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

Results (1 - 100 of 110)

1 2

Cthulhu (2 matches)

Ticket Summary Component Milestone Type Created
#13421 GoodBadISP's Revamp Internal Services/Wiki project Oct 15, 2014

Following a discussion on the mailing list [1] the GoodBadISP page could do with some updating and proper arranging.

Some of the categories I have in mind to make available in the table format are as follows: Country, Company Name, ASN, Bridges Allowed, Relays Allowed, Exits Allowed, Last Updated, Correspondence.

Would "Bridges Allowed" be a redundant measure since they won't be in the public sphere?

Moritz @ Torservers already has done a fair deal of work, some is outdated or could use an update though but it's a good place to start our focus and give inspiration where needed. [2] [3] [4]

[1] https://lists.torproject.org/pipermail/tor-relays/2014-October/005493.html

[2] https://www.torservers.net/wiki/hoster/experience

[3] https://www.torservers.net/wiki/hoster/inquiry

[4] https://www.torservers.net/wiki/hoster/index

Note: Those wishing to assist on this project please feel free to CC yourself in and keep an eye on the child tickets. I can be found under the pseudonym "TheCthulhu" on IRC or contacted at thecthulhu <at> riseup <dot> net if you wish to ask me directly what to work on next. If this is the first time you've assisted using Trac or the Tor Wiki, don't hesitate to ask for help.

#13473 Sort Existing GoodBadISP page into tables Internal Services/Wiki task Oct 19, 2014

The existing GoodBadISP tables need sorting into the new format. All opinions, feedback and communications to that ISP must go in the correct section on ISPCorrespondence page to keep the primary page clean and to the point since it will grow substantially over time.

The new format should be available soon after this ticket is posted as it will be done for the US hosts (good experiences).

JacobHenner (1 match)

Ticket Summary Component Milestone Type Created
#8177 Vidalia Help Documentation Out of Date Archived/Vidalia defect Feb 6, 2013

In the most recent release of the Tor Browser Bundle, the help documentation bundled with Vidalia (accessed by selecting Help) is out of date. A search of GeoIP will confirm this, as the documentation still lists the GeoIP lookup server at geoip.vidalia-project.net, which has not been maintained since 2010.

MB (1 match)

Ticket Summary Component Milestone Type Created
#9328 o2online.de Live Check not working with enabled SSL strictness HTTPS Everywhere/EFF-HTTPS Everywhere defect Jul 25, 2013

With enabled HTTPS Everywhere, http://www.o2online.de/microsite/o2-netz/live-check/ does not load additional JavaScript from a non-SSL CDN

ahf (7 matches)

Ticket Summary Component Milestone Type Created
#11660 Make tor_spawn_background and related interfaces work the same on windows and *nix Core Tor/Tor Tor: unspecified defect Apr 30, 2014

Have a look at the tor_spawn_background unit tests. That's sure a lot of #ifdefs! It would be nice if our portability code actually let us write code to be portable across platforms: we should fix tor_spawn_background and tor_read_all_handle to act the same across platforms.

#21662 prop278: Add support for LZMA2 and/or Zstandard Core Tor/Tor Tor: 0.3.1.x-final task Mar 7, 2017

Add support for the compression schemes needed to implement prop#278.

See: http://facebook.github.io/zstd/ and http://7-zip.org/sdk.html for the respective libraries.

#21663 prop278: Refactor the torgzip module to support additional compression schemes Core Tor/Tor Tor: 0.3.1.x-final task Mar 7, 2017

The current torgzip module should be refactored such that the new compression schemes needed for prop#278 can fit nicely into the code.

This is the tracking bug for this task.

#21664 prop278: Make the current 'torgzip' module a submodule of a new 'compression' module Core Tor/Tor Tor: 0.3.1.x-final task Mar 7, 2017
  • Create a new 'compression' module to handle all compression schemes.
  • Refactor the current 'torgzip' module into a module that handles only GZip and deflate, but adheres to the 'compression' module API.
  • Create modules for the new compression schemes: LZMA2 and Zstd.

#21665 Prop278: Establish an upper-bound for LZMA2 memory usage Core Tor/Tor Tor: 0.3.1.x-final task Mar 7, 2017

Our initial analysis shows that LZMA2 can be quite a memory hog, which means we should establish some sort of upper-bound for its memory usage and how we can actually enforce it.

#21667 Prop278: Handle new headers in directory.c Core Tor/Tor Tor: 0.3.1.x-final task Mar 7, 2017

Handle the newly defined headers and their new values from Prop#278 in the directory server/client code.

#21678 Unify Windows and Unix API for tor_read_all_handle() in util.c Core Tor/Tor Tor: 0.3.1.x-final enhancement Mar 8, 2017

While working on #21654 I noticed that we have some different code paths that depends upon whether we're running on Windows or not where it would be trivial to turn them into a single code path.

I do not have access to a Windows machine right now, so it would be useful if someone could help test the patch(es).

arma (5 matches)

Ticket Summary Component Milestone Type Created
#18213 The parameter WarnUnsafeSocks does not work as specified in the documentation, no warning is logged in the log file Core Tor/Tor Tor: unspecified defect Feb 2, 2016

The parameter WarnUnsafeSocks does not work as specified in the documentation, no warning is logged in the log file when a connection is done to an ip address.

If WarnUnsafeSocks 1 (default) is set there is no warning in the log file. If you look at the code for log_unsafe_socks_warning, the only case where an error is logged is when safe_socks is true. safe_socks is true only when SafeSocks parameter is set, but not when WarnUnsafeSocks is set.

The code should be

if (safe_socks || options->WarnUnsafeSocks) {

instead of

if (safe_socks) {

#15713 toggling DisableNetwork during bootstrap causes delay Core Tor/Tor Tor: unspecified defect Apr 17, 2015

While testing a fix for #11879, Kathy and I noticed that if the bootstrap process is interrupted by setting DisableNetwork=1 via the control port, Tor waits about a minute after DisableNetwork is set back to 0 before continuing network activity. We observed this problem on a Mac OS 10.8.5 system. Possibly related tickets: #9229, #11069.

Once release candidates for Tor Browser 4.5 are available, this should be reproducible by following these steps:

  1. Start Tor Browser and click "Connect".
  2. Click "Open Settings" in the connection progress window to interrupt the bootstrap process.
  3. Click "Connect" again. Notice that there is a delay before the bootstrap makes more progress.

We are also able to reproduce it using Tor and a manual (telnet) control port connection. Follow these steps (control port authentication is up to you):

  1. Remove all cached Tor data and start Tor like this:

./tor --defaults-torrc torrc-defaults -f torrc DisableNetwork 1

  1. Make a control port connection and issue this command:

SETCONF DisableNetwork=0

  1. Wait for bootstrapping to reach 25-50% and then do:

SETCONF DisableNetwork=1

  1. Re-enable network access:

SETCONF DisableNetwork=0 Notice that there is a delay before the bootstrap makes more progress.

We used the torrc-defaults file that ships with Tor Browser 4.5a5:

# If non-zero, try to write to disk less frequently than we would otherwise.
AvoidDiskWrites 1
# Where to send logging messages.  Format is minSeverity[-maxSeverity]
# (stderr|stdout|syslog|file FILENAME).
Log notice stdout
# Bind to this address to listen to connections from SOCKS-speaking
# applications.
SocksPort 9150
ControlPort 9151
CookieAuthentication 1
## fteproxy configuration
ClientTransportPlugin fte exec PluggableTransports/fteproxy.bin --managed

## obfs4proxy configuration
ClientTransportPlugin obfs2,obfs3,obfs4,scramblesuit exec PluggableTransports/obfs4proxy

## flash proxy configuration
# Change the second number here (9000) to the number of a port that can
# receive connections from the Internet (the port for which you
# configured port forwarding).
ClientTransportPlugin flashproxy exec PluggableTransports/flashproxy-client --register :0 :9000

## meek configuration
ClientTransportPlugin meek exec PluggableTransports/meek-client-torbrowser -- PluggableTransports/meek-client

Our torrc is also from Tor Browser and it just contains a few paths:

DataDirectory /Users/.../tb-11879.app/TorBrowser/Data/Tor
GeoIPFile /Users/.../tb-11879.app/TorBrowser/Data/Tor/geoip
GeoIPv6File /Users/.../tb-11879.app/TorBrowser/Data/Tor/geoip6

I will attach some log output.

#15715 spurious "Network is unreachable" error after setting DisableNetwork=1 Core Tor/Tor Tor: unspecified defect Apr 17, 2015

If DisableNetwork is set to 1 via SETCONF during bootstrapping, Tor sometimes generates spurious errors such as "Network is unreachable". Kathy and I saw this while testing a fix for #11879. We realize this may be difficult to fix due to the internal architecture / concurrency inside Tor.

See #15713 for steps to reproduce (but note that an error does not occur every time). In the log that is attached to #15713 you can see an example:

Apr 17 10:28:10.000 [warn] Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (Network is unreachable; NOROUTE; count 1; recommendation warn; host 847B1F850344D7876491A54892F904934E4EB85D at

(the error happens right away if it happens at all – no delay).

This problem may cause some Tor Browser users to be a little confused; all they need to do is click "Open Settings" while Tor Browser was starting up and they will sometimes see an error alert.

#19162 Make it even harder to become HSDir Core Tor/Tor Tor: unspecified defect May 23, 2016

In #8243 we started requiring Stable flag for becoming HSDirs, but this is still not hard enough for motivated adversaries. Hence we need to make it even harder for a relay to become HSDir, so that only relays that have been around for long get the flag. After prop224 gets deployed, there will be less incentive for adversaries to become HSDirs since they won't be able to harvest onion addresses.

Until then, our current plan is to increase the bandwidth and uptime required to become an HSDir to something almost unreasonable. For example requiring an uptime of over 6 months, or maybe requiring that the relay is in the top 1/4th of uptimes on the network.

#17773 Should clients avoid using guards that lost the Guard flag? Core Tor/Tor Tor: unspecified enhancement Dec 8, 2015

Nick and I both thought that at least in the past, Tor clients would stop using a relay as their guard, if it loses the Guard flag.

But it looks like the code doesn't do that -- once a relay is your guard, you'll use it in the guard position regardless of whether it has the Guard flag at this moment or not.

This is actually a tricky design decision. In favor of avoiding guards that don't have the guard flag:

  • If they get really slow, we can instruct clients to abandon them.
  • If a relay gets the guard flag for only a short period of time, it will have only a small number of (dedicated) users using it for the next months.

In favor of using non-Guard guards anyway:

  • An attacker can't push you away from your guard by hurting its performance in the eyes of the directory authorities.
  • You won't rotate guards as many times.

That "can't push you away" one looks big. What other aspects should we be considering here?

asn (1 match)

Ticket Summary Component Milestone Type Created
#4626 Very high cpu usage for gabelmoo running with renegotiation-limiting code Core Tor/Tor Tor: unspecified defect Dec 1, 2011

Hey there,

gabelmoo is seeing almost full cpu utilization lately. I'm running openssl1 and libevent master. Traffic is at around 200KB/s, so not very much. Here's a profile for everything over 0.5%:

samples  %        image name               app name                 symbol name
397332   26.8226  libc.so.6                libc.so.6                /home/karsten/debug/libc.so.6
210739   14.2263  libpthread.so.0          libpthread.so.0          __pthread_mutex_unlock_usercnt
157849   10.6559  libpthread.so.0          libpthread.so.0          pthread_mutex_lock
62969     4.2508  tor                      tor                      connection_handle_write
56998     3.8477  tor                      tor                      _openssl_locking_cb
44452     3.0008  tor                      tor                      assert_connection_ok
38146     2.5751  tor                      tor                      connection_bucket_write_limit
37917     2.5597  [vdso] (tgid:17627 range:0x7fffb85ff000-0x7fffb8600000) tor                      [vdso] (tgid:17627 range:0x7fffb85ff000-0x7fffb8600000)
32683     2.2063  tor                      tor                      flush_buf_tls
29224     1.9728  tor                      tor                      connection_is_rate_limited
28245     1.9067  tor                      tor                      connection_bucket_round_robin
25259     1.7052  tor                      tor                      tor_tls_get_error
22309     1.5060  tor                      tor                      tor_tls_write
21562     1.4556  tor                      tor                      assert_buf_ok
20642     1.3935  tor                      tor                      get_options_mutable
19521     1.3178  tor                      tor                      approx_time
19272     1.3010  tor                      tor                      _check_no_tls_errors
19108     1.2899  tor                      tor                      conn_write_callback
18312     1.2362  tor                      tor                      tor_addr_is_internal
14932     1.0080  tor                      tor                      tor_tls_get_forced_write_size
14237     0.9611  tor                      tor                      tor_gettimeofday_cache_clear
12501     0.8439  librt.so.1               librt.so.1               /home/karsten/debug/librt.so.1
11918     0.8045  tor                      tor                      tor_mutex_acquire
11907     0.8038  tor                      tor                      tor_mutex_release
11376     0.7680  tor                      tor                      connection_bucket_refill
9770      0.6595  tor                      tor                      connection_is_listener
9582      0.6468  tor                      tor                      connection_is_reading
9493      0.6408  tor                      tor                      tor_tls_state_changed_callback
9087      0.6134  tor                      tor                      connection_is_writing
8689      0.5866  tor                      tor                      TO_OR_CONN
7890      0.5326  tor                      tor                      connection_state_is_connecting

atagar (1 match)

Ticket Summary Component Milestone Type Created
#16348 Suppress exception chaining when PEP 3134 is merged Core Tor/Stem defect Jun 10, 2015

with tor- and stem-1.4.1 I run (rarely) into this :

cat ioerror.stderr.old
Exception in thread Event Notifier:
Traceback (most recent call last):
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 1758, in get_network_status
    desc_content = self.get_info(query, get_bytes = True)
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 414, in wrapped
    raise exc
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 409, in wrapped
    return func(self, *args, **kwargs)
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 1113, in get_info
    raise exc
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 1066, in get_info
    stem.response.convert('GETINFO', response)
  File "/usr/lib64/python3.3/site-packages/stem/response/__init__.py", line 135, in convert
  File "/usr/lib64/python3.3/site-packages/stem/response/getinfo.py", line 38, in _parse_message
    raise stem.InvalidArguments('552', 'GETINFO request contained unrecognized keywords: %s\n' % ', '.join(unrecognized_keywords), unrecognized_keywords)
stem.InvalidArguments: GETINFO request contained unrecognized keywords: ns/id/2BCDF9F0BCEFC2A44F7850F92362BA85AA226E1F

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.3/threading.py", line 901, in _bootstrap_inner
  File "/usr/lib64/python3.3/threading.py", line 858, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 882, in _event_loop
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 3480, in _handle_event
  File "./err.py", line 47, in orconn_event
    relay = controller.get_network_status(fingerprint)
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 414, in wrapped
    raise exc
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 409, in wrapped
    return func(self, *args, **kwargs)
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 1761, in get_network_status
    raise stem.DescriptorUnavailable("Tor was unable to provide the descriptor for '%s'" % relay)
stem.DescriptorUnavailable: Tor was unable to provide the descriptor for '2BCDF9F0BCEFC2A44F7850F92362BA85AA226E1F'

while running this script :

$ cat err.py
#!/usr/bin/python3 -u

#   Toralf Foerster
#   Hamburg
#   Germany

# collect data wrt to https://trac.torproject.org/projects/tor/ticket/13603

import time
import functools

from stem import ORStatus, ORClosureReason
from stem.control import EventType, Controller

def main():
  class Cnt(object):
    def __init__(self, done=0, closed=0, ioerror=0):
      self.done = done
      self.closed = closed
      self.ioerror = ioerror

  c = Cnt()

  with Controller.from_port(port=9051) as controller:

    orconn_listener = functools.partial(orconn_event, controller, c)
    controller.add_event_listener(orconn_listener, EventType.ORCONN)

    while True:

def orconn_event(controller, c, event):
  if event.status == ORStatus.CLOSED:
    c.closed += 1

    if event.reason == ORClosureReason.DONE:
      c.done += 1

    if event.reason == ORClosureReason.IOERROR:
      c.ioerror += 1

      fingerprint = event.endpoint_fingerprint
      print (" %i %i %i %i %s %40s" % (c.closed, c.done, c.ioerror, event.arrived_at, time.ctime(event.arrived_at), fingerprint), end='')
      relay = controller.get_network_status(fingerprint)
      if relay:
        print (" %15s %5i %s %s" % (relay.address, relay.or_port, controller.get_info("ip-to-country/%s" % relay.address, 'unknown'), relay.nickname), end='')
      print ('', flush=True)

if __name__ == '__main__':

boklm (2 matches)

Ticket Summary Component Milestone Type Created
#11508 Test that about:tor page is properly loaded Applications/Quality Assurance and Testing enhancement Apr 14, 2014

During the last beta release we realized that some translators translate "about:tor" which breaks it. We should write a test that checks this crucial page is working in built bundles.

#11509 Make sure search engine strings are not translated Applications/Quality Assurance and Testing enhancement Apr 14, 2014

Bug #11236 is caused by translated search engine strings. We should make sure those strings are not translated.

danieleweber7624 (1 match)

Ticket Summary Component Milestone Type Created
#8915 Cannot spoof useragent and vendor Applications/Tor Browser TorBrowserBundle 2.3.x-stable defect May 20, 2013

Can add any way to chage vendor to firefox via general.useragent.vendor?

Seems this only work in firefox 3 or older

Also firefox 17 not update the pref general.useragent.override without restarting the browser, this is actually same bug for newest vesions of firefox.

dgoulet (14 matches)

Ticket Summary Component Milestone Type Created
#21403 prop224: Implement HS descriptor fetching Core Tor/Tor Tor: 0.3.1.x-final enhancement Feb 6, 2017

Before the client actually can connect to the service, it has to fetch the descriptor first. As already specified in prop224 section 2.1 and 2.2.6

The client needs to parse the service's master public key from the onion address, derive the blinded public key, and then use that blinded public key to fetch the descriptor from the HSDir.

(Note that, this ticket doesn't implement how to pick the HSDir)

#14322 torsocks fails to wrap setcap binaries Core Tor/Torsocks defect Jan 22, 2015

the Linux 'capabilities' library for allowing non-root users to perform tasks which normally require elevated privileges.

at present the torsocks wrappers have checked for setuid and setgid flags on the binaries it executes and failed closed, throwing an error if this occurs, however there is currently no check to see if the binaries have capabilities applied.

in the case where they do, the LD_PRELOAD set by torsocks is stripped and the program will execute with no warning and without the torsocks wrapper.

as an example of this, the current 'ping' command on my Linux is setcap:

$ getcap which ping /usr/bin/ping = cap_net_raw+ep $ torsocks ping -c 1 torproject.org PING torproject.org ( 56(84) bytes of data. 64 bytes from icmp_seq=1 ttl=50 time=38.1 ms

the install script which does setcap
setuid here:


#16706 Too many connection_edge_process_relay_cell warnings Core Tor/Tor Tor: 0.3.1.x-final defect Aug 2, 2015

Hosting multiple hidden services on a Debian server running Tor (no special setup or config options). I see thousands of such lines in the log files:

Jul 31 07:55:39.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 07:57:59.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:00:36.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:02:49.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:05:12.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:07:30.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:09:49.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:12:09.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:14:30.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:16:50.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:19:11.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:21:45.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:24:14.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:26:27.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:29:01.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:31:18.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:33:38.000 [warn] connection_edge_process_relay_cell (at origin) failed.
Jul 31 08:35:58.000 [warn] connection_edge_process_relay_cell (at origin) failed.

All hidden services are working and accessible, didn't reload/restart Tor. What is concerning is that there are so so many of these messages in a very short time. #9635 mentioned this as well, but along with other error messages which were indicating a wrong nTor key. Here we only have a single line, heavily repeated at short time intervals.

#16934 youtube-dl (recent), torsocks 2.1.0 and TBB5+ failure Core Tor/Torsocks defect Aug 31, 2015

ERROR torsocks[29369]: [socks5] Resolve destination buffer too small (in socks5_recv_resolve_reply() at socks5.c:690) ERROR: Unable to download webpage: <urlopen error [Errno -4] Non-recoverable failure in name resolution> (caused by URLError(gaierror(-4, 'Non-recoverable failure in name resolution'),))

The error changes over time. But it is mostly in this range. With a fresh restart the problem goes away, but it is back after some time blocking all requests.

Stopping any TBB5 running and starting TBB4.5.3 makes everything go smooth again.

Besides TBB, nothing changes in the configuration.

#21293 circuit_receive_relay_cell(): Bug: relay crypt failed. Dropping connection. Core Tor/Tor Tor: 0.3.1.x-final defect Jan 24, 2017

I've hit this today on a machine running Debian Jessie and Tor (git-1a45398ffa713ca3+5156f73) acting as an onion service client with a SocksPort open and used as well. Functionality appears not to be affected, everything continues to run normally.

Besides the incoming rendezvous traffic, this instance also sends outgoing traffic via the SocksPort but to .onion destinations only, so it's mostly rendezvous traffic.

Jan 23 15:31:44.000 [warn] circuit_receive_relay_cell(): Bug: relay crypt failed. Dropping connection. (on Tor )

#11579 Torsocks should support Java Core Tor/Torsocks enhancement Apr 21, 2014

Right now Java programs run with torsocks have their network calls dropped, or sometimes crash. Torsocks should force Java programs to use Tor. This could be done by setting the proxy settings in the JVM with -DsockProxyHost= -DsocksProxyPort=8080. To ensure proxy obedience for DNS calls, torsocks might implement a DNS provider that uses SOCKS for resolution, add that to the classpath, and use it to override the DNS provider the JVM uses at runtime.

#11724 Check recvmmsg() FD passing on Unix socket for TCP socket Core Tor/Torsocks enhancement May 4, 2014

recvmsg() is supported as of now. A full exit should be done here because Torsocks can't handle this inet socket with Tor.

#11727 Support shared onion pool for DNS resolution in separate process Core Tor/Torsocks enhancement May 4, 2014

So it turns out that in irssi is doing DNS resolution in an other process and passing the result back to the first process which will make the connection.

This means that the two process have two distinct onion pools so the process doing the DNS resolution will store the onion address with the reserved cookie but the other process, when connecting using that cookie, will be unable to find the onion address in its pool.

One solution I have in mind is to create that onion pool in a shared memory (SHM) and hijack the clone/fork symbol so when we detect a new process we can set the onion pool reference in it thus sharing the pool across processes that have a common parent.

I have a PoC that works but maybe there could be an IPC approach instead.

#13184 Add an option to whitelist networks Core Tor/Torsocks enhancement Sep 17, 2014

This warning is possible for anything socket trying to connect to a localhost address.

WARNING torsocks[12360]: [connect] Connection to a local address are denied since it might be a TCP DNS query to a local DNS server. Rejecting it for safety reasons. (in tsocks_connect() at connect.c:177)

We should implement a whitelist mechanism so the user can tell which local network is allowed such as localhost.

#13207 Is rend_cache_clean_v2_descs_as_dir cutoff crazy high? Core Tor/Tor Tor: unspecified enhancement Sep 21, 2014
  time_t cutoff = now - REND_CACHE_MAX_AGE - REND_CACHE_MAX_SKEW;

That's currently 3 days.


config.c:  V(RendPostPeriod,              INTERVAL, "1 hour"),

So we expect our current one to get overwritten once an hour, yet if the hidden service goes away (stops publishing) we continue to serve its old (presumably no longer working) descriptor for 71 more hours.

One downside to this poor tuning is that we waste the time of clients who try to access the hidden service -- if we instead tell them there is no descriptor, they could go to another hsdir or give up more promptly.

One upside is that if we say we don't have one, clients *will* go visit five other hsdirs before giving up, which could result in a lot of thrashing. Whereas providing an old one will keep the client distracted for a while. But that's not really a good reason.

Another downside is that it's easier to stuff our cache full of things, i.e. use hsdirs for arbitrary storage of blobs for three days.

#15621 Kill the pre-version 3 intro protocol code with fire. Core Tor/Tor Tor: unspecified enhancement Apr 7, 2015

We still have code for dealing with version 0, 1, and 2 of the HS intro protocol.

From rend-spec.txt:

As of Tor and, clients switched to using the v2 intro format.

From the release notes:

Bugfix on, when the v3 intro-point protocol (the first one which sent a timestamp field in the INTRODUCE2 cell) was introduced;

Anything that generates INTRODUCE cells with these versions are long dead, so the code for handling this protocol version should be removed.

#19407 Support FD passing on Unix socket Core Tor/Torsocks enhancement Jun 13, 2016

Multiple issues need FD passing through a Unix socket to work: #8585, #16183

It's maybe possible to support this safely. My intuition is that we might be able to get it work by passing some cookies in the ancillary data so we can recognize the sendmsg() with the recvmsg(). Maybe!?...

#18295 Make shared random rounds configurable in test networks Core Tor/Tor Tor: unspecified enhancement Feb 10, 2016

From #16943: Replying to dgoulet:

Replying to teor:

A hard-coded SHARED_RANDOM_N_ROUNDS is going to make it really hard to test hidden services quickly using chutney. (We'll always be testing them using the default initial shared random value.) Can we make this configurable in test networks?


The part I do not like about changing this value for testing network is that we do NOT get the real behavior of the protocol... I'm not against for a testing value but I would do that after merge in a separate ticket.

#19793 Torsocks - only torify .onion domains Core Tor/Torsocks enhancement Jul 31, 2016

What torsocks does: Routes all traffic through Tor.

What it should do: It shoud have an option to route .onion domains through Tor, while normal traffic is not routed through Tor.

Advantages This would allow Mail/XMPP servers to connect to .onion domains, without any configuration hassle.

Original discussion http://tor-talk.torproject.narkive.com/j7MtPG5T/torsocks-usewithtor-only-for-onion

feynman (1 match)

Ticket Summary Component Milestone Type Created
#9022 Create an XMPP pluggable transport Obfuscation/Pluggable transport task Jun 5, 2013

We should look into XMPP pluggable transports. There are many public XMPP services that see widespread use even from censored countries.

hellais (1 match)

Ticket Summary Component Milestone Type Created
#12823 Design and implement new deck format Metrics/Ooni enhancement Aug 7, 2014

The current test deck format has some limitations.

These are namely:

1) There is no way of making an input be part of the test deck itself

2) The format is too verbose and contains redundant information (all of the ooniprobe command line options need to be explicitly specified)

For this reason I think we should have a new format that makes it possible to include inputs as part of the test deck. The test deck should therefore be a compressed container (tar and gzip seem to be good candidates as they are well supported in python).

It should then be possible to reference input files that are part of the test deck itself.

irl (1 match)

Ticket Summary Component Milestone Type Created
#13350 Provide ooni-backend packages for Debian Metrics/Ooni task Oct 7, 2014

A check to determince the package dependencies requirements. Do I miss anything?

package exp. version status Debian version

isis (1 match)

Ticket Summary Component Milestone Type Created
#12802 BridgeDB needs Nagios checks for the Email Distributor Obfuscation/BridgeDB enhancement Aug 6, 2014

BridgeDB needs Nagios checks that the Email Distributor is working. The best way to do this would be to send an email to bridges@… which say "get help".

iwakeh (8 matches)

Ticket Summary Component Milestone Type Created
#19169 verify, correct and extend runtime statistics Metrics/CollecTor CollecTor 1.2.0 defect May 25, 2016

see Analysis Part 2 for background information.

  • verify current stats
  • avoid ambiguous log statements
  • maybe, separate stats for download and import
  • ...

#15753 add performance tests to Onionoo's project structure and add the corresponding Ant task Metrics/Onionoo enhancement Apr 21, 2015

Make room for performance tests somewhere in src/ and write a separate Ant task to run them. (see parent #13616)

#18798 Analyze descriptor completeness Metrics/CollecTor enhancement Apr 12, 2016

I started a wiki page here.

#20489 add tests for CollecTor Metrics/CollecTor enhancement Oct 28, 2016

For all issues fixed during system test of the sync-release (#18910):

  • verify that there are tests checking the fixed functionality (where it makes sense)
  • add tests to catch similar issues with junit test instead of system testing (where feasible)

At least for comments 82, 95, 98 in #18910.

#21219 collector should rm data from out/ after archiving Metrics/CollecTor enhancement Jan 13, 2017

Unless I'm mistaken (or misconfigured) -- which is entirely possible -- collector will accumulate uncompressed data in out/ indefinitely, long after it's been archived in archive/ and will no longer be modified.

This takes up a lot of disk space and it'd be nice to

a) get confirmation I can remove data from out/ than is older than N months (2? 3?) b) have it deleted automagically (or at least with a config setting)

#18730 provide guidelines for the Metrics Team's java projects Metrics task Apr 6, 2016

This is the parent issue for defining

  • contributor's guidelines
  • coding style guidelines
  • release process description
  • (more?)

for java projects.

This issue serves for discussing "meta" questions like finding a central location and defining the structure.

The central place could be another git repository metrics-team-meta (or some better title), which could hold all documents like coding style guides for the various languages used by the Metrics-Team, guides and documents covering more than one Metrics-Team project, and other docs like the road-map.)

#18732 describe release process for java projects Metrics task Apr 6, 2016

The Release Process description should be based on existing documentation:

metrics-lib's CONTRIB.md

and after completion be referenced by metrics-lib's README

#20325 perform available space check using the partition recent is located on Metrics/CollecTor CollecTor 1.2.0 enhancement Oct 9, 2016

Currently, the root path of the configured 'recent' directory is used when measuring the available space.

This might not make sense in situations when partitions are mounted elsewhere. For example:

/dev/sda1 on /      (just the os)
/dev/sdb1 on /data  (here the 'recent' folder resides somewhere)

In this case sda1 might be small and sdb1 could be the huge data partition. Thus, the measurement of free space for / is useless.

Suggestion: (cf. comments) Last resort: add CheckSpacePath property and default to the root of the recent path in case it doesn't exist.

karsten (3 matches)

Ticket Summary Component Milestone Type Created
#17430 Top 10 countries graph Metrics/Metrics website enhancement Oct 27, 2015

on the main user stat page, we have the list of top ten countries connecting directly to Tor. and on the left side of the table, there's a huge white space.

Now I don't know if it's been left blank intentionally or not, but it'd be great to have a graph showing all the top ten countries with different colors on it.

#20540 define log-levels for all java metrics-products Metrics enhancement Nov 2, 2016

This is the parent issue for creating that document.

The definitions should applied in child-tickets.

#6856 new graph: bandwidth by major Tor version and bandwidth by recommended flag Metrics/Metrics website enhancement Sep 15, 2012

It would be nice to have a graph similar to [1] but replacing the number of relays with overall traffic share.

example (numbers completely made up): 0.2.4 is handling 15% of the traffic 0.2.3 is handling 40% of the traffic ...

[1] https://metrics.torproject.org/network.html#versions

lunar (1 match)

Ticket Summary Component Milestone Type Created
#11355 Provide obfsproxy nightlies in our debian repositories Obfuscation/Obfsproxy task Mar 28, 2014

People are asking for obfsproxy nightlies (#10954). It would be brilliant if people could add our debian repo, and get the latest obfsproxy master through it.

How can I help you do this?

No hurry on this one. I mainly made this ticket because #10954 was not very specific.


mikeperry (1 match)

Ticket Summary Component Milestone Type Created
#2161 Allow subscription to external rule feeds HTTPS Everywhere/EFF-HTTPS Everywhere enhancement Nov 6, 2010

The ultimate direction we want to go is towards an adblock plus model, where people can subscribe to rule feeds that are relevant to them, maintained by third parties. This involves both altering our XML schema to include a 'rulefeed' envelope tag, and adding a bit of UI to add and manage subscription urls.

It also depends upon a few enhancements being completed first. These are in the child ticket list below:

n8fr8 (7 matches)

Ticket Summary Component Milestone Type Created
#2424 Android purges firewall rules after network disable/airplane mode. Applications/Orbot defect Jan 22, 2011

Setting my phone to disable data access and/or enable airplane mode seems to cause the transproxy iptables rules created by OrBot to get silently flushed. After re-enabling, all apps access everything without tor, until I go into the orbot config screen to cause it to reapply them.

OrBot should listen for these network disable/loss/disconnect events if possible, and reinstate the iptables rules after this happens.

Someone should also test if switching from cell data to+from wifi also triggers this iptables reset. I have not tested that yet.

#3595 Connections with IPv4-mapped IPv6 addresses bypass transproxy Applications/Orbot defect Jul 14, 2011

A user (DEplan on #guardianproject) reported that Gibberbot was using his real IP despite Orbot's transproxy being turned on; further research led to the conclusion that recent releases of Android seem to use IPv4-mapped IPv6 adresses for a large portion of connections. For examples, please see http://pastebin.com/Z4KDDq40. These connections completely bypass transproxy.

I am not yet sure about the circumstances under which Android employs these addresses.

The problems in finding a solution are that Android usually does not include ip6tables (though Orbot could simply package that) and kernels do usually not include IPv6 netfilter modules. The latter is a major issue, since Orbot can't package modules for every single kernel a user might be running.

As a side note, IPv6 does not support NAT (which is what transproxying is based on).

I'll try to figure out what triggers this behaviour of Android and find possible solutions (using sysctl to disable IPv6 does not solve it).

#5393 orbot relay bug - orbot is not setting the relay values into torrc properly causing orbot to not work when set as relay Applications/Orbot defect Mar 15, 2012

This is about the bug discussed with 'n8fr8' on #guardianproject at freenode. So, the relay functionality you said was broken and needs to be fixed for 'orbot' on smartphones. I checked with the orbot version '' and you have checked with the 'dev branch of the code' as you said (i suppose that means you have checked with latest version of code by compiling and running the latest updated version from git; i will do it too and let you know again). But none seemed to work. In fact, you said you were getting a more significant crash, when you enabled relaying on smartphone for dev branch of code. You also thought if the problem is: whether the Relay conflict is with transproxying/root or with Tor client connection in general. But, i'm not sure if it later seemed not to be the problem. Then, you told me to change the torrc file on my android phone, as you said that orbot is not setting the relay values properly which might be the reason for orbot not working as a relay on smartphone. So, I will do that and let you know about it. I will also keep checking 'https://guardianproject.info/builds/Orbot/' to see if any new dev/debug release is posted. Thankyou so very much for all your help, Mr.Nathan.

#2761 Orbot Service not shutting down Applications/Orbot defect Mar 15, 2011

Behaviour: When closing tor network with big Button and exiting Orbot after tor is "deactivated", privoxy is still running and the Orbot service is not stopped.


  • Killing Privoxy from shell stops the privoxy process (OK)
  • Killing Orbot process simply restarts the process (BAD)


  • Running Orbot v1.0.4.1
  • Android Froyo 2.2.1 speedmod kernel
  • Samsung Galaxy

#3775 Permission error on Orbot Applications/Orbot defect Aug 21, 2011

There's some kind of problem with permissions in Orbot. I'm not sure if this happens only to me, but when I try to start Tor, it cannot access cache/control_auth_cookie. I can chmod it every time, but it is a bit annoying.

#5469 Orbot: can't specify node restrictions Applications/Orbot defect Mar 24, 2012

I'm using Orbot (v0.2.3.10-alpha-1.0.7-FINAL, on Android ICS v4.0.1) and I can't seem to get the exit node I request. In the Exit and Entrance Node fields I have "{us}" entered, yet sometimes I get IP's outside the US. Yesterday I got a UK ip.

Also, at random (usually after 30 minutes or so) I seem to lose connection to the Tor network without Orbot notifying me. I'm using Pandora from Canada.

#5700 Make/modify VoIP applications to work better on Tor Metrics/Analysis project Apr 30, 2012

Depending on how hard it will be to make Tor handle VoIP applications people already want to use (#5699), we should explore how much mileage we can get out of making our own or modifying existing VoIP applications to work better on Tor. One example here is Roger's "push to talk" not-actually-realtime-but-close VoIP wishlist item that Nathan is working on.

nickm (30 matches)

Ticket Summary Component Milestone Type Created
#17278 Fix malleable relay crypto Core Tor/Tor Tor: unspecified defect Oct 7, 2015

This has been an annoyance in our protocol for entirely too long. Once we have a solid proposal (#5640) for this, we should implement it posthaste.

#18346 Separate the various roles that directory authorities play, from a configuration POV Core Tor/Tor Tor: unspecified enhancement Feb 19, 2016

It would be handy if the following roles were split up:

1) The list of IP:Orport:Identity to which every relay should upload every descriptor. 2) The list of IP:Orport:Identity from which caches should expect to find canonical consensuses and descriptors. 3) The list of IP:Orport:Identity from which non-caches should expect to bootstrap consensuses and descriptors. (See 'fallbackdir') 4) The list of keys that must sign a vote or a consensus. 5) The list of IP:Orport:Identity that authorities use when sending and receiving votes.

Splitting roles up in this way would better prepare us for an implementation of prop#257 down the road.

#18637 Have OOM handler look at all memory consumption, not just some Core Tor/Tor Tor: unspecified enhancement Mar 25, 2016

Just because our OOM handler doesn't know how to free every kind of memory we allocate, doesn't mean we shouldn't teach it to consider our total allocation when deciding that we're low on memory.

For platforms where malloc() can return NULL, we could have it look at that too.

#1749 Split relay and link crypto across multiple CPU cores Core Tor/Tor Tor: unspecified project Jul 29, 2010

Right now, Tor does nearly all of its work in one main thread. We have a basic "CPUWorker" implementation that we use for doing server-side onionskin crypto in a separate thread, but thanks to improvements long ago, server-side onionskin crypto on longer dominates. If we could split the work of relay AES-CTR crypto and SSL crypto across multiple threads, that would be pretty helpful in letting high-performance servers saturate their connections. (Blutmagie has wanted this for some while.)

Child Tickets:

Parallel Crypto: Design a good crypto parallelization plan and architecture

#20835 Refactor choose_good_entry_server so it is (almost) never used Core Tor/Tor Tor: unspecified task Nov 29, 2016

From my prop271 branch:

 * XXXX prop271 this function is used in four ways: picking out guards for
 *   the old (pre-prop271) guard algorithm; picking out guards for circuits;
 *   picking out guards for testing circuits on non-bridgees;
 *   picking out entries when entry guards are disabled.  These options
 *   should be disentangled.

#21554 Inventory proposals that need merging into specs ; merge them. Core Tor/Tor Tor: 0.3.0.x-final task Feb 24, 2017

Before we can call 0.3.0 done, we must have the specs up-to-date.

#3428 Control port may emit log messages in the middle of another event/reply Core Tor/Tor Tor: unspecified defect Jun 18, 2011

If the following call to connection_printf_to_buf in handle_control_getinfo in src/or/control.c fails, it may emit a LOG control-port event in the middle of a reply:

    if (!strchr(v, '\n') && !strchr(v, '\r')) {
      connection_printf_to_buf(conn, "250-%s=", k);
      connection_write_str_to_buf(v, conn);
      connection_write_str_to_buf("\r\n", conn);
    } else {

I expect that other output functions can emit log messages in the middle of a control port event or reply, too. We should make sure that never happens, by making all control-port code build each complete reply/event in a separate buffer before writing any of it out, and adding an event/reply queue to the control_connection_t structure.

#16579 (Sandbox) Caught a bad syscall attempt (syscall socket) Core Tor/Tor Tor: unspecified defect Jul 14, 2015

I'm running tor on Gentoo Hardened. The bug exists in and tor crashes within seconds of starting, before any clients can connect I think.

Jul 14 13:13:07.000 [notice] Tor (git-df76da0f3bfd6897) opening log file.
Jul 14 13:13:07.182 [notice] Tor v0.2.7.1-alpha (git-df76da0f3bfd6897) running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.1p and Zlib 1.2.8.
Jul 14 13:13:07.182 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jul 14 13:13:07.182 [notice] This version is not a stable Tor release. Expect more bugs than usual.
Jul 14 13:13:07.182 [notice] Read configuration file "/etc/tor/torrc".
Jul 14 13:13:07.187 [notice] Opening Socks listener on
Jul 14 13:13:07.187 [notice] Opening Socks listener on
Jul 14 13:13:07.187 [notice] Opening Socks listener on
Jul 14 13:13:07.187 [notice] Opening Control listener on
Jul 14 13:13:07.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jul 14 13:13:07.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jul 14 13:13:07.000 [notice] Bootstrapped 0%: Starting

============================================================ T= 1436875987
(Sandbox) Caught a bad syscall attempt (syscall socket)
$ uname -r

This bug has been reported downstream: https://bugs.gentoo.org/show_bug.cgi?id=550302. It occurs with the following torrc:

# Minimal torrc so tor will work out of the box
User tor
PIDFile /var/run/tor/tor.pid
Log notice syslog
Log notice file /var/log/tor/log
DataDirectory /var/lib/tor/data
SandBox 1

SocksPort 9050
SocksPort 9056 IsolateDestAddr IsolateDestPort
SocksPort 9055

ControlPort 9015
CookieAuthentication 1

By commenting out "Sandbox 1" or unsetting it, tor will obviously run without crashing.

#18308 Tor threading broken Core Tor/Tor Tor: unspecified defect Feb 12, 2016

Tor relies on double checked locking for various threading initializations. Double checked locking is not guaranteed to work.

For Posix: 4.11, Memory Synchronization: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html

Applications shall ensure that access to any memory location by more than one thread of control (threads or processes) is restricted such that no thread of control can read or modify a memory location while another thread of control may be modifying it.

Race conditions: compat_pthreads.c:threads_initialized


Mutex static initialization is supported by pthreads via PTHREAD_MUTEX_INITIALIZER.

#18321 Exclude our own vote from the consensus if we think our own vote is invalid Core Tor/Tor Tor: unspecified defect Feb 16, 2016

We're creating a vote that is invalid, but try to make a consensus anyway like nothing's wrong. Then we fail doing that as described above.

#19329 Integrate callgraph complexity measures into our regular process Core Tor/Tor Tor: unspecified defect Jun 7, 2016

Unless we track the size of the largest cycles in our code, big cycles may return

#20522 Enable DISABLE_DISABLING_ED25519 Core Tor/Tor Tor: 0.3.2.x-final defect Nov 1, 2016

Split from #18319

At some point, we should require relays that once had an ed25519 key associated with their RSA key to always have that key, rather than allowing them to drop back to a version that didn't support ed25519.

(This means they need to use a new RSA key to downgrade to an older version of tor without ed25519, which is consistent with the pinning in #18319.)

This means either: 1a. waiting until 0.2.5 is no longer recommended, or 1b. look at historical metrics data to see how often relays run a recent version for a while, then drop back to an older one. If the answer is "almost never" then we can just turn it on now.

To implement this change, replace #undef DISABLE_DISABLING_ED25519 with #define DISABLE_DISABLING_ED25519.

#21474 Fix make test-fuzz-corpora warnings Core Tor/Tor Tor: unspecified defect Feb 15, 2017

The following bug warnings should probably be protocol warnings, or be caught earlier:

Running tests for consensus
Feb 16 02:17:26.012 [warn] tor_timegm: Bug: Out-of-range argument to tor_timegm (on Tor d633c4757c1392fb)
Feb 16 02:17:30.133 [warn] sr_parse_commit: Bug: SR: Commit algorithm "sha6-256" is not recognized. (on Tor d633c4757c1392fb)
Feb 16 02:17:34.625 [warn] commit_decode: Bug: SR: Commit from authority 20EE989200EF98A75102B461DF62F01B2932C0D6 decoded length doesn't match the expected length (36 vs 40). (on Tor d633c4757c1392fb)
Feb 16 02:17:40.758 [warn] commit_decode: Bug: SR: Commit from authority B0F141F4B8CCBCC328572C71E5590BBA19775594 can't be decoded. (on Tor d633c4757c1392fb)
Running tests for descriptor
Feb 16 02:18:08.780 [warn] tor_timegm: Bug: Out-of-range argument to tor_timegm (on Tor d633c4757c1392fb)
Running tests for extrainfo
Feb 16 02:18:18.548 [warn] tor_timegm: Bug: Out-of-range argument to tor_timegm (on Tor d633c4757c1392fb)

I'm not sure whether we need this in 030, but it would be nice to fix them eventually.

#21673 prop140: Handle signatures correctly Core Tor/Tor Tor: 0.3.1.x-final defect Mar 7, 2017

For diffs to work properly, we need to check the input document and the output document in their entirety, including their signatures. Otherwise, the diffs won't apply correctly when they change the signatures!

But for *that* to work, we need to do what we can to minimize the odds that anybody has a consensus with different signatures, or with signatures organized differently.

As an alternative, we could change the diff format so that it always replaces all the old signatures with the new ones.

#6836 Chop functionality out of routerlist.c Core Tor/Tor Tor: unspecified enhancement Sep 13, 2012

In my branch "split_routerlist.c", I have the start of some work on dividing routerlist.c into more sensible pieces. I've chopped out routerset_t, killed a couple of functions, and moved most of the node manipulation pieces into nodelist.c

I'd still like to chop out more: the trusted_dir_server_t logic and the node-selection logic don't belong there any more. Nor does the authority certificate code. Nor does the hidden service directory stuff, nor does the hexdigest stuff.

In the longer term, I want routerlist.c to basically just not get invoked when you're not touching routerinfos.

#17295 Route-selection and guard-selection logic completely replaced Core Tor/Tor Tor: unspecified enhancement Oct 7, 2015

By Nov 2016, we have a deliverable to get our route selection much more right than today, and to have it very tested. We should get this done significantly earlier.

#20719 prop271 -- make parameters configurable Core Tor/Tor Tor: unspecified enhancement Nov 18, 2016

#20931 [prop271] Generate GUARD controller events Core Tor/Tor Tor: unspecified enhancement Dec 8, 2016

#21209 Write, revise, analyze proposals for ways to use less directory bandwidth Core Tor/Tor Tor: 0.3.1.x-final project Jan 12, 2017

We have a bunch of ideas about how to use less bandwidth for directory stuff. But most of them need to be expanded into proposals, and some of the the ones that *are* proposals need better analysis -- informed in part by the information we hope to get from #21205. This is a parent ticket. Each child ticket will be for one particular proposal.

#21213 Write and analyze proposals for fetching consensuses/microdescriptors less frequently? Core Tor/Tor Tor: 0.3.1.x-final task Jan 12, 2017

The idea: Our current algorithm for deciding whether you need a new consensus is ad hoc; we just picked an interval more or less at random.

Depending on the results from #21205, we may learn that it's not as necessary as we had thought for a client to fetch consensuses and microdescriptors so often. If that's the case, we should have proposals and analyses for (optionally?) decreasing the frequency of our downloads.

There may be different results here for "busy" and "not so busy" clients.

Of course, the analysis needs to include the security impact.

#21646 prop140/compression: Refactor "directory request" code Core Tor/Tor Tor: 0.3.1.x-final task Mar 6, 2017

Our current notion of "what is a directory request" includes a bunch of fields that are strewn around directory connections and passed to different functions. It would be nice to instead have a "directory request" type that we created and passed around as appropriate. This would make it easier to test our request generation/parsing code.

#449 dns failures prevent legitimate options being set Core Tor/Tor Tor: unspecified defect Jun 9, 2007

Outright hostname lookup failures for previously configured hidden services prevent other options being set while DNS is down.

For example, I configure a hidden service redirecting to google.com while DNS is working. DNS subsequently stops working, e.g. nameserver becomes completely unreachable. If I then attempt to set a config option using the controller, it will not get set as long as tor cannot resolve the hidden service name.

Rejection of hidden service configurations (and hence any subsequent or unrelated config change) made while tor is running needs to be more tolerant of lookup failures.

The following attempts to validate the hidden service config currently in use (and previously validated when DNS was working). If the validation fails, it must be because DNS is down, so the existing config is retained. If the user was attempting to add a new hidden service config, then it doesn't get added.

Index: src/or/config.c =================================================================== --- src/or/config.c (revision 10545) +++ src/or/config.c (working copy) @@ -963,10 +963,15 @@



  • if (running_tor && rend_config_services(options, 0)<0) {
  • log_warn(LD_BUG,
  • "Previously validated hidden services line could not be added!");
  • return -1;

+ if (running_tor && rend_config_services(options, 1)<0) { + log_warn(LD_CONFIG, + "Previously validated hidden services line no longer valid! Retaining existing hidden services config if there is one."); + }else{ + if (rend_config_services(options, 0)<0){ + log_warn(LD_BUG, + "Previously validated hidden services line could not be added!"); + return -1; + }


if (running_tor) {

@@ -2920,9 +2925,10 @@




if (rend_config_services(options, 1) < 0)

REJECT("Failed to configure rendezvous options. See logs for details.");

- +*/

if (parse_virtual_addr_network(options->VirtualAddrNetwork, 1, NULL)<0)

return -1;

[Automatically added by flyspray2trac: Operating System: All]

#4373 When we close a conn due to bad CERTS cell, we complain about stuff in our outbuf Core Tor/Tor Tor: unspecified defect Nov 1, 2011

While looking at bug #4371, here's what my client said:

Nov 01 04:30:45.000 [warn] Certificate not yet valid: is your system clock set incorrectly?
Nov 01 04:30:45.000 [warn] (certificate lifetime runs from Nov  1 12:15:08 2011 GMT through Oct 31 12:15:08 2012 GMT. Your time is Nov 01 08:30:45 2011 GMT.)
Nov 01 04:30:45.000 [notice] We stalled too much while trying to write 512 bytes to address "".  If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 14, type OR, state 7, marked at command.c:995).

Looks like we had already written our netinfo cell to the outbuf, but hadn't flushed it. Since I'm a client and this was an OR connection, it gets to be severity notice. Fun.

For the client side, I think this bug might be resolved by the proposed fix to #4361.

But my directory authority experiences something similar: Nov 01 06:04:10.000 [info] conn_close_if_marked(): Conn (addr "", fd 1609, type OR, state 7) marked, but wants to flush 916 bytes. (Marked at command.c:995) Nov 01 06:04:10.000 [info] conn_close_if_marked(): We stalled too much while trying to write 916 bytes to address "". If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 1609, type OR, state 7, marked at command.c:995). I wonder what's sitting in its outbuf.

#14987 Settle on a name for descriptors Core Tor/Tor Tor: unspecified defect Feb 22, 2015

As discussed on #14784 we call self-published descriptors quite a few things...

  • 'GETINFO desc/*' and Stem call the main self-published descriptors server descriptors. Metrics also uses a "server-descriptor 1.0" annotation for them.
  • The dir-spec calls them router descriptors... usually. It opts for 'server descriptor' in section 6.2.
  • CollecTor calls them relay descriptors.

Having three different names is confusing for new contributors and... well, us too. We should standardize on a name.

This primarily straddles Tor's spec, Stem, and CollecTor. Personally I'd like for us to standardize on server descriptors because it's codified in the Metrics annotation and classes Stem vends.

Karsten, Nick: any objections? If not then I'm happy to provide a spec patch and file a CollecTor ticket for this.

#19984 Use a better set of comparison/evaluation functions for deciding which connections to kill when OOS Core Tor/Tor Tor: 0.3.1.x-final defect Aug 25, 2016

Our existing OOS code kills low-priority OR connections. But really, we need to look at all connections that an adversary might be able to create (especially dir and exit connections), or else an adversary will be able to open a bunch of those, and force us to kill as many OR connections as they want.

This problem is the reason that DisableOOSCheck is now on-by-default.

#20270 "Descriptor is missing an ntor curve25519 onion key" message too noisy? Core Tor/Tor Tor: 0.3.1.x-final defect Oct 1, 2016

On moria1, I have a lot of these:

Oct 01 18:01:05.421 [notice] Descriptor from router $E0671CF9CB593F27CD389CD4DD819BF9448EA834~ordb1 at is missing an ntor curve25519 onion key.
Oct 01 18:01:20.530 [notice] Descriptor from router $179B10784BF8955C73313CCB195904AE133E5F53~ordb3 at is missing an ntor curve25519 onion key.
Oct 01 18:03:21.653 [notice] Descriptor from router $993992BBD01E36D3ECF8BA0B802C158961BB257C~orchard at is missing an ntor curve25519 onion key.
Oct 01 18:04:00.856 [notice] Descriptor from router $496FED39C1469567B333C3A418A07D5CF62DCD23~rationalist at is missing an ntor curve25519 onion key.
Oct 01 18:14:14.418 [notice] Descriptor from router $184A39F7F891D46592216643CD74DDE50C6DAA75~FlandersRegional at is missing an ntor curve25519 onion key.
Oct 01 18:15:16.620 [notice] Descriptor from router $1AFA214C8AE557640BD29A0A8D674F92EB20948D~Unnamdddd at is missing an ntor curve25519 onion key.
Oct 01 18:23:29.590 [notice] Descriptor from router $40E632BED95FC71E5B622DBB9E336D89A6D52600~younix at is missing an ntor curve25519 onion key.

teor thinks this wasn't really meant to be a notice-level log every time an obsolete relay tries to upload to me.

That said, I think the first two of these relays (ordb1 and ordb3) are actually that alternative nodejs Tor relay implementation, right?

So I think maybe I *do* want to hear about relays that I refused due to lack of an ntor curve onion key, but only the ones that had a satisfactory version string?

#20356 prop220: unit tests for all new/changed circuit extension functions Core Tor/Tor Tor: 0.3.1.x-final defect Oct 13, 2016

#20534 Revise hard-coded download schedules Core Tor/Tor Tor: 0.3.1.x-final defect Nov 2, 2016

We should tweak the download schedules in config.c based on what we've learned in #20499.

These schedules should retry sooner than never: TestingServerDownloadSchedule TestingClientDownloadSchedule

These schedules retry at most every 2 hours, should that be higher? TestingServerConsensusDownloadSchedule

These schedules retry at most every 12 hours, should that be higher? lower? TestingClientConsensusDownloadSchedule

These schedules retry at most every 73 hours, should that be lower? Should we try more times before jumping to retrying after an hour? ClientBootstrapConsensusAuthorityDownloadSchedule ClientBootstrapConsensusFallbackDownloadSchedule ClientBootstrapConsensusAuthorityOnlyDownloadSchedule

Should we try more than 7 or 8 times to get directory documents? TestingConsensusMaxDownloadTries ClientBootstrapConsensusMaxDownloadTries TestingDescriptorMaxDownloadTries TestingMicrodescMaxDownloadTries TestingCertMaxDownloadTries

#20895 Split node_supports_ed25519_link_authentication into two or three separate functions Core Tor/Tor Tor: 0.3.1.x-final task Dec 6, 2016

As of our #15056 code to implement the circuit-side part of prop220, we have a function, node_supports_ed25519_link_authentication, which isn't quite right.

Sometimes, when we use it, we mean, "If we try to connect to this node, should we expect that we will authenticate its ed25519 identity?"

Sometimes, we mean "If we try to make a connection through some random node to this node, authenticating with its ed25519 identity, will that work?"

And sometimes we mean "I'm thinking of asking _that_ node to extend a circuit to _this_ node. Should I tell it about _this_ node's Ed25519 identity, or would it take it the wrong way?" I wrote a patch here in response to dgoulet's review of my #15056 branch, but on reflection, it isn't right. I'll attach it, but it's a bad start, and it's too complex, and maybe you should ignore it?

#16598 fsync ed25519 master key files before closing them. Core Tor/Tor Tor: unspecified defect Jul 15, 2015

Weasel says this is a good idea, and IMO it can't hurt.

nito (1 match)

Ticket Summary Component Milestone Type Created
#3663 Fatal error on Mixminion Mixminion-Client defect Jul 29, 2011

Error message coming up for all commands. Below a couple I get

Traceback (most recent call last):

File "mixminion.py", line 25, in ? File "mixminion\Main.pyc", line 333, in main File "mixminion\ClientMain.pyc", line 1208, in runClient File "mixminion\ClientMain.pyc", line 960, in init File "mixminion\ClientDirectory.pyc", line 116, in init File "mixminion\ClientDirectory.pyc", line 369, in load File "mixminion\Common.pyc", line 604, in readPickled

AttributeError: 'module' object has no attribute 'CachingDescriptorSource'

Traceback (most recent call last):

File "mixminion.py", line 25, in ? File "mixminion\Main.pyc", line 333, in main File "mixminion\Main.pyc", line 279, in commandShell File "mixminion\Main.pyc", line 333, in main File "mixminion\ClientMain.pyc", line 1872, in cleanQueue File "mixminion\ClientUtils.pyc", line 730, in getHandlesByAge File "mixminion\ClientUtils.pyc", line 867, in loadMetadata File "mixminion\Filestore.pyc", line 397, in loadAllMetadata File "mixminion\Filestore.pyc", line 420, in getMetadata


pde (6 matches)

Ticket Summary Component Milestone Type Created
#3777 Should not generate mixed-content warnings if rewriting all http to https HTTPS Everywhere/EFF-HTTPS Everywhere defect Aug 21, 2011

As far as I can tell, Firefox produces mixed-content warnings on an https page that references resources (images, scripts, etc) via http, even if HTTPS Everywhere can rewrite all of those http URLs to use https. (HTTPS Everywhere does rewrite resource requests, right?)

Ideally, if HTTPS Everywhere successfully rewrites every http request from a page to an https request, the page should not generate a mixed content warning. (Though I'd still like to see some indication that the page was only secure due to HTTPS Everywhere, so I know to report the insecure resources to the site owner.)

#4122 Google Translate breakage HTTPS Everywhere/EFF-HTTPS Everywhere defect Sep 28, 2011

Google Translate for whole webpages is broken again. (HTTPS-Everywhere 1.0.3, FF 8) Instead of the translation, you get multiple copies of the Google translate header underneath each other.

#4278 MSDN navigation breakage (due to Origin: header omission?) HTTPS Everywhere/EFF-HTTPS Everywhere defect Oct 20, 2011

Reported here: https://bugzilla.mozilla.org/show_bug.cgi?id=694611

Test case:

Clicking on the fold-out tabs on the left of this page produces no results:


#6276 Hiding the context menu button breaks the Tools->HTTPS Everywhere menu HTTPS Everywhere/EFF-HTTPS Everywhere defect Jul 2, 2012

When you drag the httpse icon from the urlbar to 'menu_bar.view.toolbars.customize' window you lose the 'menu_bar.tools.https_everywhere' drop down menu content for httpse, though the menu item itself is still there. At that point, the only way to configure httpse is via 'about:addons'. Or of course to restore the icon to the urlbar.

Seems to me the drop down menu content should remain regardless of where the icon is, or is not.

FF 10.0.3 ESR HTTPS-E v2.1

#6592 HTTPS Everywhere Causes WordPress.com Zemanta Media Gallery To Not Work HTTPS Everywhere/EFF-HTTPS Everywhere defect Aug 11, 2012


Every version of HTTPS Everywhere that I have tested has caused a problem with at least one of the common websites that I visit, so I finally am reporting one of these problems.

When using WordPress.com with Zemanta enable, the Media Gallery/Recommended Images show up, but the hover feature that allow you to preview images does not work and clicking images to add them to your post does not work when HTTPS Everywhere is installed.

Here is an example of what Zemanta looks like on WordPress.com:


I am using HTTPS Everywhere in the latest Firefox and have had this problem in other versions of Firefox, and with various versions of HTTPS Everywhere.

I think this problem happens even if HTTPS Everywhere is disabled, but once uninstalled the problem stops, but I could be wrong.

Thank you, -John Jr :)

#7454 Active rules list doesn't indicate effects of securecookie if no URL rewrite took place HTTPS Everywhere/EFF-HTTPS Everywhere defect Nov 12, 2012

We just had a bug reported about a securecookie rule that applied to all of MIT (including pages that don't support HTTPS at all!) and was breaking logins.

However, the ruleset in question didn't appear in the active rules menu, because no rewrite rule was triggered on the page in question -- only a securecookie. This made the problem take slightly longer to debug and made it harder for affected users to work around. The existing logic for deciding which rules are "active" on the current pages seems to be triggered solely by rewrite rules.

Since securecookie rules affect page rendering and can even break it, rulesets containing them should also show up in the active rules menu when they were applied to a resource on the current page.

phoul (4 matches)

Ticket Summary Component Milestone Type Created
#13951 Add EFF technologists as maintainers for the HTTPS Everywhere transifex strings Community/Translations defect Dec 12, 2014

I think I used to have the ability to edit all of our translated strings, but it now says, "to translate you need to be logged in and a members of the $LANG team" (I am logged in).

EFF technologists we should add:

pde schoen jsha jgillula cooperq

#20538 TB manual single page Community/Tor Browser Manual defect Nov 2, 2016

Can we please (additionally if you like) have a single-page build of the manual?

#20665 Create alpha Tor Browser Manual Community/Tor Browser Manual defect Nov 14, 2016

We should have an "alpha" version of the manual that tracks the alpha Tor Browser, and is eventually frozen and turned into the stable manual.

#10966 Define a process on how new support assistants can be accepted in the team Community/Tor Support task Feb 20, 2014

The switch from having a single person handling all support request to a team was made through recruiting support assistants as a contracting position. It would be good to define a process on how new people can get accepted in the team. It's mostly a question of trust and probably we need to define a vouching process and a set of people that need to ack the decision.

1 2
Note: See TracReports for help on using and creating reports.