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

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

Results (1 - 100 of 121)

1 2

Cthulhu (2 matches)

Ticket Summary Component Milestone Type Created
Description
#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
Description
#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
Description
#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 (2 matches)

Ticket Summary Component Milestone Type Created
Description
#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.


#21678 Unify Windows and Unix API for tor_read_all_handle() in util.c Core Tor/Tor Tor: 0.3.2.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).


angelo620 (1 match)

Ticket Summary Component Milestone Type Created
Description
#2149 new 'extra dormant' mode for people who never use their tor Core Tor/Tor Tor: unspecified enhancement Nov 1, 2010

If you stop using your Tor as a client (and it doesn't have dirport or orport open), after an hour you'll stop fetching descriptors, but you'll continue to fetch consensuses.

Periodically we hear plans like http://wiki.debian.org/FreedomBox/DesignAndToDos that will involve installing Tor on things by default.

We should teach Tor that if a lot of time passes (e.g. 24 hours), it should stop fetching consensuses also. It should also remember in its state file that it's doing so, so the dormancy survives across reboots.


arma (5 matches)

Ticket Summary Component Milestone Type Created
Description
#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 0.2.6.6 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 86.59.21.38:443)

(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?


#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) {

atagar (1 match)

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

with tor-0.2.6.9 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
    message._parse_message(**kwargs)
  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
    self.run()
  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
    self._handle_event(event_message)
  File "/usr/lib64/python3.3/site-packages/stem/control.py", line 3480, in _handle_event
    listener(event_message)
  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:
    controller.authenticate()

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

    while True:
      time.sleep(1)

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__':
  main()

boklm (2 matches)

Ticket Summary Component Milestone Type Created
Description
#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.


catalyst (2 matches)

Ticket Summary Component Milestone Type Created
Description
#20532 Make sure directory_initiate_request handles pluggable transports correctly Core Tor/Tor Tor: 0.3.1.x-final defect Nov 2, 2016

When a relay is configured as a bridge, a user reports this can lead to direct connections being made to the relay/bridge, even when a pluggable transport is configured. We have been unable to confirm this.

https://lists.torproject.org/pipermail/tor-dev/2016-November/011618.html

We should check directory_initiate_command_rend (the linked connection case), and connection_or_connect to make sure it is not possible for a connection to go directly to a configured bridge when a transport is set up.


#22619 SessionGroup = Reading config failed Core Tor/Tor Tor: 0.3.2.x-final defect Jun 15, 2017

If i specify SessionGroup as described in manual. tor stops with error.

torrc:

SocksPort 9051 SessionGroup=1

Jun 15 16:46:24.700 [warn] Invalid SocksPort option '"SessionGroup=INT"'

Jun 15 16:46:24.700 [warn] Failed to parse/validate config: Invalid SocksPort/SocksListenAddress configuration

Jun 15 16:46:24.701 [err] Reading config failed--see warnings above.

second try

SocksPort 9051 SessionGroup=INT

Results into:

Jun 15 16:46:35.677 [warn] Invalid SocksPort option '"SessionGroup=1"'

Jun 15 16:46:35.678 [warn] Failed to parse/validate config: Invalid SocksPort/SocksListenAddress configuration

Jun 15 16:46:35.677 [warn] Invalid SocksPort option '"SessionGroup=1"'

Jun 15 16:46:35.678 [warn] Failed to parse/validate config: Invalid SocksPort/SocksListenAddress configuration

Jun 15 16:46:35.678 [err] Reading config failed--see warnings above.


danieleweber7624 (1 match)

Ticket Summary Component Milestone Type Created
Description
#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
Description
#21509 Fuzz v3 hidden services Core Tor/Tor Tor: 0.3.1.x-final task Feb 19, 2017

If we want the fuzzer to effectively fuzz v3 hidden services, we need to:

  • fuzz GET requests: #21476
  • fuzz POST requests: #21478
  • add v3 GET and POST requests to the fuzzing corpus
  • add tokens from v3 GET and POST requests as new fuzzing token lists
  • disable the encrypted connection check when fuzzing (we should do this for v2 services as well)
  • create a v3 descriptor fuzzer
  • add v3 descriptor examples to the fuzzing corpus
  • add tokens from v3 descriptors as a new fuzzing token list

#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 (82.195.75.101) 56(84) bytes of data. 64 bytes from 82.195.75.101: icmp_seq=1 ttl=50 time=38.1 ms

the install script which does setcap
setuid here:

https://projects.archlinux.org/svntogit/packages.git/tree/trunk/iputils.install?h=packages/iputils


#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.


#21084 sometimes we call circuit has_opened() more than 2 times on client side Core Tor/Tor Tor: unspecified defect Dec 26, 2016

We have a branch bug15618_030-testing at https://gitweb.torproject.org/user/dgoulet/tor.git that logs a warning when we call more than 2 times circuit has_opened() on a circuit. The patch was made to confirm the theory on #15618 related to a warning we see on relays. While until now I never saw the warning on relay side, I see it quite often on client side.

Based on the log messages, I think this is related to introduction point circuits and not rendezvous circuits as we thought. Basically it happens when we open a 4 hop circuit with last hop X, and immediately we extend that circuit to a 5 hop one with last hop Y, where Y is (I think) the introduction point. I got the warning 2 times in a row and the similarity between them is that they are 5 hop circuits with the last two hops 4 and 5 the same, but different hops 2 and 3.

Dec 25 13:15:15.000 [info] internal circ (length 5, last hop $D7316BF7FD633DD7474B18C33E1D5FDEB04D26A7): $A7C411B809D0AA98C4264917BB701ABF17B2181E(open) $B5212DB685A2A0FCFBAE425738E478D12361710D(open) $123F403DA94A74F959B7FE0E5B27FA57EFA12925(open) $1F4105C688E835A56AF3D66C787677B57240FFA2(open) $D7316BF7FD633DD7474B18C33E1D5FDEB04D26A7(open)
Dec 25 13:15:15.000 [info] entry_guards_note_guard_success(): Recorded success for primary confirmed guard sakujakira ($A7C411B809D0AA98C4264917BB701ABF17B2181E)
Dec 25 13:15:15.000 [info] circuit_send_next_onion_skin(): circuit built!
Dec 25 13:15:15.000 [warn] BLAM. Circuit has_opened() called 3 times.
Dec 25 13:15:15.000 [info] rend_client_introcirc_has_opened(): introcirc is open
Dec 25 13:15:15.000 [info] connection_ap_handshake_attach_circuit(): pending-join circ 3419634369 already here, with intro ack. Stalling. (stream 26 sec old)
Dec 25 13:15:15.000 [info] connection_ap_handshake_attach_circuit(): ready rend circ 2404371907 already here (no intro-ack yet on intro 2259155742). (stream 26 sec old)
Dec 25 13:15:15.000 [info] connection_ap_handshake_attach_circuit(): found open intro circ 2259155742 (rend 2404371907); sending introduction. (stream 26 sec old)
Dec 25 13:15:15.000 [info] rend_client_send_introduction(): Sending an INTRODUCE1 cell
Dec 25 13:15:15.000 [info] pathbias_count_use_attempt(): Used circuit 53293 is already in path state use succeeded. Circuit is a Hidden service client: Pending rendezvous point currently open.
Dec 25 13:15:16.000 [info] internal circ (length 5, last hop $D7316BF7FD633DD7474B18C33E1D5FDEB04D26A7): $A7C411B809D0AA98C4264917BB701ABF17B2181E(open) $5C01D5518D1F5A071C6F07D1F4630F577AB5B60A(open) $DA9DA02A7B0565DF5F3E961CA911E750072DCBBD(open) $1F4105C688E835A56AF3D66C787677B57240FFA2(open) $D7316BF7FD633DD7474B18C33E1D5FDEB04D26A7(open)
Dec 25 13:15:16.000 [info] entry_guards_note_guard_success(): Recorded success for primary confirmed guard sakujakira ($A7C411B809D0AA98C4264917BB701ABF17B2181E)
Dec 25 13:15:16.000 [info] circuit_send_next_onion_skin(): circuit built!
Dec 25 13:15:16.000 [warn] BLAM. Circuit has_opened() called 3 times.
Dec 25 13:15:16.000 [info] rend_client_introcirc_has_opened(): introcirc is open
Dec 25 13:15:16.000 [info] connection_ap_handshake_attach_circuit(): pending-join circ 3419634369 already here, with intro ack. Stalling. (stream 26 sec old)
Dec 25 13:15:16.000 [info] connection_ap_handshake_attach_circuit(): Intro circ 2259155742 present and awaiting ack (rend 2404371907). Stalling. (stream 26 sec old)
Dec 25 13:15:16.000 [info] connection_ap_handshake_attach_circuit(): Intro circ 3200472182 present and awaiting ack (rend 4286776399). Stalling. (stream 26 sec old)
Dec 25 13:15:16.000 [info] connection_ap_handshake_attach_circuit(): ready rend circ 2334828448 already here (no intro-ack yet on intro 4002828471). (stream 27 sec old)
Dec 25 13:15:16.000 [info] connection_ap_handshake_attach_circuit(): found open intro circ 4002828471 (rend 2334828448); sending introduction. (stream 27 sec old)
Dec 25 13:15:16.000 [info] rend_client_send_introduction(): Sending an INTRODUCE1 cell
Dec 25 13:15:16.000 [info] pathbias_count_use_attempt(): Used circuit 53301 is already in path state use succeeded. Circuit is a Hidden service client: Pending rendezvous point currently open.

#22068 Make it explicit that Torsocks won't work correctly in certain scenarios in the README Core Tor/Torsocks defect Apr 26, 2017

As far as I understand, Torsocks works by setting LD_PRELOAD, so an application that doesn't uses libc, and instead uses syscalls directly will be able to bypass torsocks and connect directly to the Internet.

I think a warning about it on the README file, and MAN page is needed, besides making it explicit that using Torsocks is not 100% safe as the README might make you think, for example:

Torsocks allows you to use most applications in a safe way with Tor. It ensures that DNS requests are handled safely and explicitly rejects any traffic other than TCP from the application you're using. Torsocks is an ELF shared library that is loaded before all others. The library overrides every needed Internet communication libc function calls such as connect(2) or gethostbyname(3). This process is transparent to the user and if torsocks detects any communication that can't go through the Tor network such as UDP traffic, for instance, the connection is denied. If, for any reason, there is no way for torsocks to provide the Tor anonymity guarantee to your application, torsocks will force the application to quit and stop everything.


#22159 Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 77 seconds Core Tor/Tor Tor: 0.3.1.x-final defect May 4, 2017

Running Tor 0.3.1.0-alpha-dev (git-38a13b91a8d1f2ef) as a client with an onion service:

May 04 14:17:59.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 77 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:17:59.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:17:59.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:17:59.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:17:59.178 [warn]   Intro point 2 at ProstoHome: circuit is doing handshakes
May 04 14:17:59.178 [warn]   Intro point 3 at PhantomTrain6: circuit is doing handshakes
May 04 14:17:59.178 [warn]   Intro point 4 at fastnightmare: circuit is open
May 04 14:18:00.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 78 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:00.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:00.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:00.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:00.178 [warn]   Intro point 2 at ProstoHome: circuit is doing handshakes
May 04 14:18:00.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:01.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 79 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:01.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:01.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:01.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:01.179 [warn]   Intro point 2 at ProstoHome: circuit is doing handshakes
May 04 14:18:01.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:02.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 80 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:02.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:02.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:02.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:02.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:02.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:03.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 81 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:03.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:03.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:03.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:03.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:03.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:04.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 82 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:04.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:04.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:04.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:04.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:04.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:05.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 83 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:05.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:05.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:05.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:05.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:05.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:06.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 84 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:06.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:06.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:06.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:06.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:06.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:07.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 85 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:07.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:07.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:07.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:07.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:07.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:08.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 86 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:08.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:08.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:08.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:08.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:08.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:09.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 87 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:09.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:09.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:09.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:09.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:09.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:10.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 88 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:10.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:10.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:10.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:10.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:10.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:11.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 89 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:11.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:11.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:11.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:11.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:11.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:12.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 90 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:12.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:12.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:12.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:12.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:12.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:13.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 91 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:13.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:13.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:13.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:13.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:13.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:14.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 92 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:14.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:14.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:14.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:14.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:14.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:15.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 93 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:15.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:15.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:15.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:15.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:15.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:16.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 94 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:16.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:16.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:16.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:16.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:16.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:17.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 95 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:17.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:17.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:17.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:17.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:17.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:18.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 96 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:18.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:18.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:18.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:18.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:18.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:19.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 97 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:19.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:19.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:19.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:19.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:19.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:20.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 98 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:20.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:20.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:20.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:20.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:20.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:21.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 99 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:21.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:21.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:21.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:21.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:21.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:22.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 100 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:22.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:22.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:22.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:22.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:22.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:23.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 101 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:23.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:23.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:23.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:23.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:23.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:24.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 102 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:24.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:24.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:24.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:24.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:24.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:25.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 103 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:25.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:25.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:25.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:25.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:25.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:26.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 104 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:26.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:26.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:26.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:26.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:26.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:27.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 105 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:27.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:27.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:27.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:27.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:27.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:28.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 106 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:28.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:28.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:28.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:28.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:28.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:29.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 107 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:29.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:29.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:29.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:29.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:29.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:30.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 108 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:30.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:30.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:30.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:30.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:30.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:31.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 109 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:31.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:31.179 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:31.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:31.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:31.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:32.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 110 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:32.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:32.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:32.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:32.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:32.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:33.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 111 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:33.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:33.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:33.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:33.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:33.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:34.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 112 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:34.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:34.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:34.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:34.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:34.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:35.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 113 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:35.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:35.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:35.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:35.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:35.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:36.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 114 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:36.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:36.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:36.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:36.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:36.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:37.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 115 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:37.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:37.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:37.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:37.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:37.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:38.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 116 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:38.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:38.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:38.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:38.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:38.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:39.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 117 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:39.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:39.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:39.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:39.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:39.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:40.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 118 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:40.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:40.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:40.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:40.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:40.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:41.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 119 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:41.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:41.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:41.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:41.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:41.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:42.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 120 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:42.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:42.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:42.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:42.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:42.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:43.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 121 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:43.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:43.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:43.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:43.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:43.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:44.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 122 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:44.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:44.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:44.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:44.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:44.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:45.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 123 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:45.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:45.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:45.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:45.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:45.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:46.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 124 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:46.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:46.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:46.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:46.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:46.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:47.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 125 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:47.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:47.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:47.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:47.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:47.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:48.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 126 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:48.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:48.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:48.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:48.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:48.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:49.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 127 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:49.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:49.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:49.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:49.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:49.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:50.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 128 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:50.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:50.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:50.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:50.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:50.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:51.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 129 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:51.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:51.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:51.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:51.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:51.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:52.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 130 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:52.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:52.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:52.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:52.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:52.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:53.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 131 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:53.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:53.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:53.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:53.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:53.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:54.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 132 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:54.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:54.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:54.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:54.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:54.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:55.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 133 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:55.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:55.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:55.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:55.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:55.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:56.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 134 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:56.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:56.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:56.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:56.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:56.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:57.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 135 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:57.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:57.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:57.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:57.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:57.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:58.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 136 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:58.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:58.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:58.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:58.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:58.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:18:59.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 137 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:18:59.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:18:59.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:18:59.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:18:59.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:18:59.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:00.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 138 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:00.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:00.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:00.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:00.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:00.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:01.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 139 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:01.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:01.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:01.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:01.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:01.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:02.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 140 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:02.179 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:02.179 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:02.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:02.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:02.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:03.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 141 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:03.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:03.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:03.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:03.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:03.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:04.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 142 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:04.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:04.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:04.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:04.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:04.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:05.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 143 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:05.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:05.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:05.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:05.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:05.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:06.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 144 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:06.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:06.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:06.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:06.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:06.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:07.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 145 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:07.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:07.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:07.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:07.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:07.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:08.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 146 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:08.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:08.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:08.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:08.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:08.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:09.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 147 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:09.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:09.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:09.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:09.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:09.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:10.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 148 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:10.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:10.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:10.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:10.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:10.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:11.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 149 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:11.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:11.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:11.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:11.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:11.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:12.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 150 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:12.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:12.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:12.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:12.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:12.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:13.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 151 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:13.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:13.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:13.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:13.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:13.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:14.179 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 152 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:14.179 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:14.179 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:14.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:14.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:14.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:15.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 153 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:15.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:15.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:15.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:15.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:15.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:16.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 154 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:16.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:16.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:16.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:16.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:16.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:17.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 155 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:17.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:17.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:17.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:17.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:17.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:18.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 156 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:18.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:18.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:18.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:18.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:18.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:19.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 157 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:19.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:19.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:19.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:19.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:19.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:20.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 158 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:20.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:20.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:20.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:20.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:20.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:21.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 159 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:21.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:21.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:21.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:21.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:21.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:22.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 160 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:22.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:22.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:22.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:22.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:22.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:23.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 161 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:23.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:23.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:23.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:23.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:23.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:24.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 162 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:24.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:24.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:24.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:24.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:24.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:25.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 163 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:25.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:25.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:25.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:25.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:25.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:26.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 164 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:26.177 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:26.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:26.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:26.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:26.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:27.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 165 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:27.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:27.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:27.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:27.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:27.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:28.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 166 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:28.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:28.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:28.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:28.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:28.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:29.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 167 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:29.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:29.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:29.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:29.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:29.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:30.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 168 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:30.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:30.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:30.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:30.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:30.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:31.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 169 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:31.177 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:31.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:31.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:31.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:31.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:32.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 170 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:32.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:32.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:32.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:32.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:32.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:33.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 171 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:33.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:33.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:33.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:33.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:33.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:34.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 172 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:34.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:34.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:34.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:34.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:34.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:35.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 173 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:35.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:35.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:35.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:35.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:35.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:36.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 174 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:36.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:36.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:36.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:36.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:36.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:37.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 175 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:37.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:37.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:37.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:37.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:37.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:38.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 176 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:38.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:38.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:38.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:38.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:38.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:39.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 177 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:39.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:39.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:39.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:39.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:39.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:40.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 178 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:40.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:40.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:40.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:40.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:40.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:41.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 179 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:41.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:41.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:41.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:41.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:41.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:42.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 180 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:42.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:42.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:42.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:42.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:42.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:43.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 181 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:43.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:43.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:43.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:43.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:43.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:44.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 182 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:44.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:44.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:44.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:44.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:44.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:45.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 183 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:45.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:45.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:45.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:45.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:45.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:46.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 184 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:46.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:46.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:46.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:46.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:46.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:47.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 185 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:47.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:47.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:47.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:47.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:47.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:48.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 186 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:48.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:48.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:48.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:48.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:48.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:49.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 187 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:49.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:49.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:49.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:49.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:49.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:50.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 188 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:50.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:50.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:50.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:50.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:50.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:51.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 189 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:51.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:51.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:51.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:51.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:51.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:52.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 190 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:52.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:52.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:52.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:52.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:52.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:53.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 191 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:53.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:53.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:53.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:53.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:53.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:54.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 192 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:54.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:54.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:54.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:54.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:54.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:55.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 193 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:55.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:55.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:55.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:55.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:55.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:56.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 194 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:56.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:56.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:56.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:56.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:56.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:57.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 195 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:57.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:57.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:57.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:57.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:57.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:58.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 196 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:58.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:58.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:58.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:58.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:58.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:19:59.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 197 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:19:59.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:19:59.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:19:59.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:19:59.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:19:59.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:00.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 198 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:00.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:00.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:00.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:00.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:00.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:01.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 199 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:01.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:01.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:01.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:01.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:01.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:02.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 200 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:02.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:02.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:02.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:02.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:02.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:03.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 201 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:03.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:03.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:03.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:03.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:03.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:04.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 202 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:04.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:04.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:04.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:04.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:04.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:05.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 203 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:05.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:05.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:05.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:05.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:05.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:06.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 204 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:06.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:06.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:06.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:06.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:06.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:07.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 205 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:07.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:07.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:07.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:07.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:07.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:08.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 206 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:08.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:08.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:08.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:08.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:08.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:09.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 207 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:09.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:09.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:09.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:09.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:09.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:10.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 208 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:10.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:10.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:10.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:10.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:10.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:11.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 209 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:11.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:11.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:11.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:11.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:11.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:12.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 210 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:12.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:12.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:12.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:12.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:12.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:13.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 211 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:13.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:13.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:13.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:13.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:13.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:14.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 212 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:14.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:14.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:14.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:14.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:14.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:15.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 213 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:15.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:15.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:15.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:15.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:15.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:16.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 214 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:16.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:16.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:16.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:16.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:16.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:17.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 215 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:17.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:17.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:17.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:17.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:17.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:18.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 216 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:18.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:18.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:18.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:18.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:18.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:19.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 217 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:19.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:19.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:19.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:19.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:19.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:20.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 218 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:20.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:20.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:20.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:20.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:20.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:21.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 219 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:21.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:21.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:21.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:21.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:21.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:22.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 220 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:22.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:22.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:22.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:22.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:22.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:23.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 221 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:23.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:23.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:23.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:23.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:23.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:24.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 222 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:24.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:24.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:24.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:24.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:24.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:25.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 223 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:25.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:25.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:25.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:25.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:25.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:26.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 224 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:26.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:26.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:26.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:26.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:26.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:27.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 225 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:27.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:27.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:27.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:27.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:27.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:28.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 226 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:28.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:28.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:28.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:28.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:28.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:29.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 227 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:29.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:29.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:29.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:29.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:29.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:30.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 228 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:30.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:30.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:30.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:30.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:30.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:31.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 229 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:31.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:31.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:31.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:31.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:31.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:32.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 230 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:32.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:32.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:32.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:32.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:32.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:33.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 231 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:33.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:33.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:33.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:33.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:33.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:34.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 232 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:34.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:34.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:34.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:34.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:34.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:35.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 233 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:35.177 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:35.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:35.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:35.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:35.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:36.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 234 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:36.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:36.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:36.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:36.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:36.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:37.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 235 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:37.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:37.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:37.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:37.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:37.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:38.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 236 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:38.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:38.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:38.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:38.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:38.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:39.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 237 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:39.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:39.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:39.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:39.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:39.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:40.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 238 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:40.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:40.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:40.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:40.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:40.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:41.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 239 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:41.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:41.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:41.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:41.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:41.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:42.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 240 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:42.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:42.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:42.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:42.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:42.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:43.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 241 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:43.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:43.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:43.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:43.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:43.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:44.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 242 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:44.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:44.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:44.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:44.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:44.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:45.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 243 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:45.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:45.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:45.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:45.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:45.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:46.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 244 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:46.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:46.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:46.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:46.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:46.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:47.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 245 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:47.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:47.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:47.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:47.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:47.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:48.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 246 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:48.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:48.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:48.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:48.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:48.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:49.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 247 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:49.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:49.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:49.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:49.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:49.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:50.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 248 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:50.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:50.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:50.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:50.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:50.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:51.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 249 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:51.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:51.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:51.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:51.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:51.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:52.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 250 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:52.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:52.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:52.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:52.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:52.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:53.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 251 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:53.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:53.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:53.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:53.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:53.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:54.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 252 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:54.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:54.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:54.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:54.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:54.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:55.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 253 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:55.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:55.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:55.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:55.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:55.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:56.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 254 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:56.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:56.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:56.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:56.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:56.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:57.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 255 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:57.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:57.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:57.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:57.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:57.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:58.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 256 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:58.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:58.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:58.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:58.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:58.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:20:59.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 257 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:20:59.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:20:59.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:20:59.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:20:59.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:20:59.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:00.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 258 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:00.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:00.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:00.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:00.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:00.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:01.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 259 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:01.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:01.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:01.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:01.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:01.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:02.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 260 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:02.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:02.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:02.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:02.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:02.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:03.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 261 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:03.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:03.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:03.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:03.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:03.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:04.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 262 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:04.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:04.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:04.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:04.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:04.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:05.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 263 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:05.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:05.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:05.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:05.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:05.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:06.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 264 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:06.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:06.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:06.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:06.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:06.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:07.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 265 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:07.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:07.179 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:07.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:07.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:07.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:08.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 266 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:08.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:08.179 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:08.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:08.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:08.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:09.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 267 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:09.177 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:09.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:09.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:09.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:09.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:10.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 268 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:10.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:10.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:10.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:10.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:10.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:11.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 269 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:11.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:11.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:11.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:11.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:11.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:12.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 270 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:12.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:12.180 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:12.180 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:12.180 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:12.180 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:13.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 271 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:13.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:13.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:13.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:13.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:13.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:14.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 272 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:14.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:14.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:14.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:14.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:14.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:15.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 273 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:15.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:15.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:15.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:15.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:15.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:16.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 274 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:16.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:16.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:16.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:16.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:16.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:17.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 275 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:17.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:17.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:17.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:17.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:17.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:18.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 276 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:18.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:18.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:18.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:18.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:18.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:19.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 277 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:19.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:19.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:19.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:19.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:19.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:20.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 278 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:20.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:20.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:20.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:20.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:20.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:21.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 279 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:21.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:21.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:21.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:21.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:21.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:22.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 280 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:22.177 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:22.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:22.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:22.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:22.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:23.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 281 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:23.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:23.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:23.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:23.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:23.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:24.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 282 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:24.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:24.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:24.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:24.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:24.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:25.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 283 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:25.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:25.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:25.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:25.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:25.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:26.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 284 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:26.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:26.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:26.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:26.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:26.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:27.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 285 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:27.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:27.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:27.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:27.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:27.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:28.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 286 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:28.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:28.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:28.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:28.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:28.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:29.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 287 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:29.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:29.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:29.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:29.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:29.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:30.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 288 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:30.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:30.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:30.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:30.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:30.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:31.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 289 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:31.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:31.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:31.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:31.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:31.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:32.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 290 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:32.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:32.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:32.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:32.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:32.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:33.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 291 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:33.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:33.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:33.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:33.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:33.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:34.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 292 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:34.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:34.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:34.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:34.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:34.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:35.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 293 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:35.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:35.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:35.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:35.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:35.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:36.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 294 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:36.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:36.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:36.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:36.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:36.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:37.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 295 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:37.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:37.179 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:37.179 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:37.179 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:37.179 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:38.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 296 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:38.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:38.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:38.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:38.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:38.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:39.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 297 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:39.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:39.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:39.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:39.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:39.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:40.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 298 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:40.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:40.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:40.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:40.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:40.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:41.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 299 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:41.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:41.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:41.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:41.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:41.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:42.178 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 300 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:42.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:42.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:42.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:42.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:42.178 [warn]   Intro point 3 at fastnightmare: circuit is open
May 04 14:21:43.177 [warn] Hidden service f3oap63t7u7hfnki exceeded launch limit with 11 intro points in the last 301 seconds. Intro circuit launches are limited to 8 per 300 seconds.
May 04 14:21:43.178 [warn] Service configured in "/tmp/hidden_service/":
May 04 14:21:43.178 [warn]   Intro point 0 at Parckwart: circuit is open
May 04 14:21:43.178 [warn]   Intro point 1 at tancouAlpha: circuit is open
May 04 14:21:43.178 [warn]   Intro point 2 at ProstoHome: no circuit
May 04 14:21:43.178 [warn]   Intro point 3 at fastnightmare: circuit is open

#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=127.0.0.1 -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.


#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 0.2.0.7-alpha and 0.1.2.18, clients switched to using the v2 intro format.

From the release notes:

Bugfix on 0.2.1.6-alpha, 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!?...


#21888 prop224: Groundwork for service implementation Core Tor/Tor Tor: 0.3.2.x-final enhancement Apr 7, 2017

This is the parent ticket for a series of patches we want to merge upstream to lay the groundwork for the service implementation (#20657) in order to bring down the number of commits and size of that branch and making review less of a pain.

I'll set this to 031 milestone if we have time to do it great! but ultimately this is only needed for 032 merge window so no biggy if we don't make it.


#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
Description
#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
Description
#12823 Design and implement new deck format Archived/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
Description
#13350 Provide ooni-backend packages for Debian Archived/Ooni task Oct 7, 2014

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

package exp. version status Debian version
pyyamlunspec.OKstable:3.10-4
python-twisted>=12.2.0OKstable-bpo:13.2.0-1
python-cyclone>1.1OKtesting:1.1-1
python-ipaddr>2.1.10OKstable:2.1.10-1
python-geoip>=0.2.6OKstable:1.2.4-2
transaction>=1.4.1OKtesting:1.4.3-3
python-txtorcon>=0.7OKstable-bpo:0.11.0-1
pyopenssl>=0.13OKstable:0.13-2
zope.component>=4.0.0OKtesting:4.2.1-2
zope.event>=4.0.0OKtesting:4.0.3-2
zope.interface>=4.0.1OKtesting:4.1.1-2
python-pysqlite2>=2.6.0OKstable:2.6.3-3
service-identityunspec.OKtesting:1.0.0-3

isis (1 match)

Ticket Summary Component Milestone Type Created
Description
#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 (12 matches)

Ticket Summary Component Milestone Type Created
Description
#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
  • ...

#20395 metrics-lib should be able to handle large descriptor files Metrics/metrics-lib defect Oct 18, 2016

Discovered OOM problem for large descriptor files in #20335, see comment 12 there for how to reproduce.


#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.


#19640 review and improve interface hierarchy Metrics/metrics-lib enhancement Jul 7, 2016

see #19398 (comment 10)


#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)


#22428 add webstats module to collector Metrics/CollecTor enhancement May 29, 2017

Port the python code for sanitizing weblogs and add a webstat module to collector.


#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


#17861 Consider adding a new interface RelayNetworkStatusMicrodescConsensus Metrics/metrics-lib enhancement Dec 15, 2015

There are currently three different version 3 network status document types, identified by the following @type annotations:

  1. @type network-status-vote-3 1.0: these are votes exchanged by directory authorities;
  2. @type network-status-consensus-3 1.0: these are (unflavored) consensuses based on votes and published by directory authorities;
  3. @type network-status-microdesc-consensus-3 1.0: these are the same consensuses as before but using a specific flavor, in this case one that references microdescriptors rather than server descriptors.

So, while we're using a separate interface for the first type (RelayNetworkStatusVote), we're using the same interface (RelayNetworkStatusConsensus) for the second and third type. This only works, because the only differences between unflavored and microdesc-flavored consensuses can be found in the network status entries, and we're using the generic NetworkStatusEntry for those. But as soon as there will be new keywords in either unflavored or microdesc-flavored consensuses, we'll have to add support for them to RelayNetworkStatusConsensus, even though the other flavor doesn't support them.

We might consider adding another interface RelayNetworkStatusMicrodescConsensus for microdesc-flavored consensus, which would probably just extend RelayNetworkStatusConsensus for now (or copy over everything from it? uhhh). But if microdesc-flavored consensuses ever derive from unflavored consensus in header or footer, we'll be able to model those changes correctly.

Related to this suggestion, we might consider making NetworkStatusEntry less generic by using a separate Entry interface like we just did for ExitList. Following that model, RelayNetworkStatusVote.Entry would keep its getMicrodescriptorDigests() method, RelayNetworkStatusConsensus.Entry would drop that method, and RelayNetworkStatusMicrodescConsensus.Entry would get a getMicrodescriptorDigest() (singular) method.

I don't think these changes are super urgent, but I wanted to write them down before resolving #17000 where they first came up.


#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
Description
#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
Description
#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.

Thanks!


mikeperry (1 match)

Ticket Summary Component Milestone Type Created
Description
#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
Description
#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 '0.2.3.10-alpha-orbot-1.0.7-FINAL' 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.

Actions:

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

Env:

  • 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 (40 matches)

Ticket Summary Component Milestone Type Created
Description
#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.


#22276 Merge prop220/prop244 to tor-spec/dir-spec Core Tor/Tor Tor: 0.3.1.x-final defect May 16, 2017

These were finished in 0.3.0.x, but have still not gotten into tor-spec.


#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:

#1760
Parallel Crypto: Design a good crypto parallelization plan and architecture


#15940 Make a standard transition plan for killing off a client version Core Tor/Tor Tor: 0.3.2.x-final task May 6, 2015

Parent ticket for transitioning current and future client versions off the tor network with a minimal amount of pain.


#15941 Form a plan for killing off client versions which assume they'll live forever Core Tor/Tor Tor: 0.3.2.x-final task May 6, 2015

From at least 0.2.4 to 0.2.6, tor client versions assume that they will keep on using the network forever. They have no "request to stop" code or other mechanisms that prevent them becoming a drain on the network.

It would help to plan their transition out at some point, so we can work out what to do to make version obsolescence in future.

See #15233 for killing off 0.2.2 and 0.2.3


#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.1.x-final task Feb 24, 2017

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


#14312 tor-spec says additional fields in exitpolicy response are "optional" when they're not Core Tor/Tor Tor: 0.3.2.x-final defect Jan 20, 2015

A #tor user reported seeing

    if (rh.length < 9) { /* reason+ipv4+dns_ttl */
      log_notice(LD_PROTOCOL,
             "Short path bias probe response length field (%d).", rh.length);
      return - END_CIRC_REASON_TORPROTOCOL;
    }

I think this was triggered by Tom's new relay implementation.

It turns out our spec says

   The payload of a RELAY_END cell begins with a single 'reason' byte to
   describe why the stream is closing, plus optional data (depending on
   the reason.)
   [...]
   (With REASON_EXITPOLICY, the 4-byte IPv4 address or 16-byte IPv6 address
   forms the optional data, along with a 4-byte TTL; no other reason
   currently has extra data.)

Tom and I are now thinking that this word 'optional' means 'required for some types of end cells but not included in others'. But he misinterpreted 'optional' to mean 'you don't have to implement it'. Which is a fine interpretation, except Tor clients complain at log-level notice when you don't.

I think it was originally optional because some very old Tor versions didn't implement it. But now they all do (well, up until yesterday, when Tom's version came online). Should we just make this extra data for reason-exitpolicy be optionally mandatory?


#14948 Clarify in control-spec which relays have ns and md entries and which don't Core Tor/Tor Tor: 0.3.2.x-final defect Feb 19, 2015

Over in #14937 the Tor Browser folks are trying to do a 'getinfo ns/id/...' on a bridge, and of course it's not working because there *are* no networkstatus stanzas for bridges. But our control-spec just says words like "OR" and "server" so I can't blame them for not intuiting that some ORs have ns entries and some don't.

I also bet the same thing would happen in "getinfo md/id/..." -- we just say "the latest microdescriptor for a given OR." when describing what this feature does.

I'm cc'ing Atagar here too since I bet stem could find this ticket interesting too.


#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 0.2.6.7 and 0.2.7.1-alpha. tor crashes within seconds of starting, before any clients can connect I think.

Jul 14 13:13:07.000 [notice] Tor 0.2.7.1-alpha (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 127.0.0.1:9050
Jul 14 13:13:07.187 [notice] Opening Socks listener on 127.0.0.1:9056
Jul 14 13:13:07.187 [notice] Opening Socks listener on 127.0.0.1:9055
Jul 14 13:13:07.187 [notice] Opening Control listener on 127.0.0.1:9015
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)
/usr/bin/tor(+0x142148)[0x4bb7bc8148]
/lib64/libc.so.6(socket+0x7)[0x3adc706ea07]
/lib64/libc.so.6(socket+0x7)[0x3adc706ea07]
/lib64/libc.so.6(+0xf16a0)[0x3adc70686a0]
/lib64/libc.so.6(__vsyslog_chk+0x3ef)[0x3adc7068aff]
/lib64/libc.so.6(__syslog_chk+0x89)[0x3adc7068df9]
/usr/bin/tor(+0x135bb0)[0x4bb7bbbbb0]
/usr/bin/tor(tor_log+0xd0)[0x4bb7bbc680]
/usr/bin/tor(control_event_bootstrap+0x1e4)[0x4bb7b7ba74]
/usr/bin/tor(do_main_loop+0x84)[0x4bb7abe234]
/usr/bin/tor(tor_main+0x16c5)[0x4bb7ac1225]
/lib64/libc.so.6(__libc_start_main+0x114)[0x3adc6f97134]
/usr/bin/tor(+0x34519)[0x4bb7aba519]
$ uname -r
3.18.9-hardened

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 Use a better pattern for "create mutex if not already initialized" 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

log.c:log_mutex_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.


#21031 Please don't remove ClientDNSRejectInternalAddresses Core Tor/Tor Tor: 0.3.2.x-final defect Dec 19, 2016

I have a private tor network that lives in 10.0.0.0/8, and removing this option would make that network unusable.


#21212 Write and analyze proposals for transmitting microdescriptors with less bandwidth Core Tor/Tor Tor: 0.3.2.x-final defect Jan 12, 2017

The idea: I can think of a few ways to lower the amount of bandwidth we use for downloading microdescriptors, without actually fetching any fewer. Would any of them be worthwhile? We should analyze them and write proposals for them.

  • Do we frequently download small batches of microdescriptors? If so, fetching them in larger batches would get us better compression.
  • Do we frequently download small batches of microdescriptors? If so, zlib dictionaries would get us better compression.
  • When a client moves from one consensus to another, the set of microdescriptors that the client wants is almost determined by the difference between those two consensuses. (I say "almost" because the client may have other mds that occurred in even earlier consensuses.) Can we have clients download microdescriptors in batches that depend on the consensus, rather than batches that are named by the microdescriptor digests? This would have these benefits:
    • HTTP requests would get much shorter.
    • Batching many microdescriptors together would improve compression.
    • Batching a predictable group of microdescriptors together would enable us to spend more CPU on compressing those groups, since we wouldn't need to compress so many different groups. (See #21211)

#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:

./src/test/fuzz_static_testcases.sh
Running tests for consensus
Feb 16 02:17:26.012 [warn] tor_timegm: Bug: Out-of-range argument to tor_timegm (on Tor 0.3.0.3-alpha-dev d633c4757c1392fb)
Feb 16 02:17:30.133 [warn] sr_parse_commit: Bug: SR: Commit algorithm "sha6-256" is not recognized. (on Tor 0.3.0.3-alpha-dev 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 0.3.0.3-alpha-dev d633c4757c1392fb)
Feb 16 02:17:40.758 [warn] commit_decode: Bug: SR: Commit from authority B0F141F4B8CCBCC328572C71E5590BBA19775594 can't be decoded. (on Tor 0.3.0.3-alpha-dev d633c4757c1392fb)
Running tests for descriptor
Feb 16 02:18:08.780 [warn] tor_timegm: Bug: Out-of-range argument to tor_timegm (on Tor 0.3.0.3-alpha-dev d633c4757c1392fb)
Running tests for extrainfo
Feb 16 02:18:18.548 [warn] tor_timegm: Bug: Out-of-range argument to tor_timegm (on Tor 0.3.0.3-alpha-dev d633c4757c1392fb)
...

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


#21522 ClientDNSRejectInternalAddresses should not be deprecated in test networks. Core Tor/Tor Tor: 0.3.2.x-final defect Feb 22, 2017

Warning: Testing options override the deprecated option ClientDNSRejectInternalAddresses. Is that intentional?

Yes, it's required for exits in test networks to function. But it's only a warning, so as long as we don't remove ClientDNSRejectInternalAddresses, it's fine.


#22204 I can't list a relay in my EntryNodes if it doesn't have the Guard flag Core Tor/Tor Tor: 0.3.2.x-final defect May 9, 2017

In the past, I could do

src/or/tor entrynodes moria1

and voila, I would begin using my Tor with moria1 as my entry node.

In the new world order, post prop#271 I assume, I instead get this complaint:

May 08 20:27:42.394 [warn] Your configuration excludes 100% of all possible guards. That's likely to make you stand out from the rest of the world.
May 08 20:27:42.394 [notice] Starting with guard context "restricted"
May 08 20:27:42.405 [notice] Bootstrapped 80%: Connecting to the Tor network
May 08 20:27:43.425 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.

and then I never bootstrap.

This is clearly a regression. Is it intentional, and I should go read guard-spec.txt for why, or is it accidental?


#22264 Remove old cached_dir_t code Core Tor/Tor Tor: 0.3.2.x-final defect May 15, 2017

I'm pretty sure that with the completion of prop 278, we no longer use the old cached_dir_t code for anything at all. Let's rip it out!


#22278 Is anything undocumented from proposals 158, 162? Core Tor/Tor Tor: 0.3.1.x-final defect May 16, 2017

These proposals are marked "FINISHED", meaning that they are implemented but not completely merged into the specs:

   158  Clients download consensus + microdescriptors [in 0.2.3.1-alpha]
   162  Publish the consensus in multiple flavors [in 0.2.3.1-alpha]

What, if anything, did we not merge there? I think that most of this stuff actually is documented.

We should merge whatever got implemented that still remains, and close these proposals.


#22342 Add a nice append-only stringbuffer, and refactor code to use it Core Tor/Tor Tor: 0.3.2.x-final defect May 23, 2017

Right now we have 2.5 strategies for building strings out of pieces:

1a) Sometimes, we use a stack-allocated buffer, and a pointer into that buffer, and we write into that buffer using tor_snprintf and strlcpy and friends.

1b) Sometimes we do the same with a heap-allocated buffer.

2) Sometimes we allocate a smartlist full of little strings, and use smartlist_join_strings() to turn it into one big string.

Both of these methods are cumbersome and at least somewhat inefficient. It would be better to have something that managed the buffer size, and supported commands like "extend with snprintf" or "extend with string".

Calling this "intro" because it doesn't require extensive knowledge of Tor; but it isn't a small task to do it right. This is something where we'd want to optimize for efficiency... though in the short run, we might just do it as a wrapper around smartlist_t and smartlist_join_strings().


#22349 dir auth attempts to fetch a descriptor every minute for every relay with mismatched rsa/ed key Core Tor/Tor Tor: 0.3.1.x-final defect May 23, 2017

moria1's logs are full of stanzas like this:

May 23 17:57:11.242 [info] handle_response_fetch_desc(): Received server info (body size 8933) from server '154.35.175.225:80'
May 23 17:57:11.244 [info] router_load_routers_from_string(): 4 elements to add
May 23 17:57:11.244 [info] dirserv_router_get_status(): Descriptor from router $2F7A826CC5B7E6D834ECA25E236A1351D389D195~EchoBase at 85.212.41.58 has an Ed25519 key, but the <rsa,ed25519> keys don't match what they were before.
May 23 17:57:11.244 [info] router_load_routers_from_string(): Marking router D3F5ABDFB2F5AED2E3D6C95F270953DEB3FCBC93 as never downloadable
May 23 17:57:11.244 [info] dirserv_router_get_status(): Descriptor from router $878413A9DE5AC497A2A5F200DA163F12D503FD8D~torlink2 at 128.199.242.75 has an Ed25519 key, but the <rsa,ed25519> keys don't match what they were before.
May 23 17:57:11.244 [info] router_load_routers_from_string(): Marking router E3E7039714569018DBF9880D5C4799054F0CE59C as never downloadable
May 23 17:57:11.244 [info] dirserv_router_get_status(): Descriptor from router $B5C45F1FD0DFE044772ED1B34160F6CF49B267EC~e35 at 88.75.214.223 has an Ed25519 key, but the <rsa,ed25519> keys don't match what they were before.
May 23 17:57:11.244 [info] router_load_routers_from_string(): Marking router E95C042AA6EB02AB262568B869A4D014E79EBE9F as never downloadable
May 23 17:57:11.244 [info] dirserv_router_get_status(): Descriptor from router $F94A792CE808F8FE39C80AD17CB2D0802F7B9D90~Void at 95.54.95.153 has an Ed25519 key, but the <rsa,ed25519> keys don't match what they were before.
May 23 17:57:11.244 [info] router_load_routers_from_string(): Marking router D56C3F9C4627222890C0C49543370499AA2D7CD6 as never downloadable
May 23 17:57:11.261 [info] handle_response_fetch_desc(): Received 4/4 router descriptors requested from 154.35.175.225:80

In fact, check out this line:

May 23 17:59:11.167 [info] update_consensus_router_descriptor_downloads(): 16 router descriptors downloadable. 0 delayed; 7180 present (615 of those were in old_routers); 0 would_reject; 0 wouldnt_use; 0 in progress.

(The number '16' is the same number as in #22348.)

I have a new line, once per minute, for each relay whose keys I think are mismatched.

It looks like I am failing to actually mark the descriptor as undownloadable, or I am failing to stick with my decision once it was marked.


#22400 We bootstrap from different primary guards when we start with a non-live consensus and not enough guards in the state file Core Tor/Tor Tor: 0.3.1.x-final defect May 26, 2017

I started my Tor client (0.3.1.1-alpha (git-ab9976b7245f05a9)) with these three guards (and only these three guards) in my state file:

Guard in=default rsa_id=BB119A5A4D5DA2BBB7B796ECC50E3C0F1D4FD910 nickname=onslaught sampled_on=2017-04-29T09:28:05 sampled_by=0.3.1.0-alpha-dev listed=1 confirmed_on=2017-05-02T22:48:40 confirmed_idx=1
Guard in=default rsa_id=7369A0E14C59B11D78357EC5AFE573A259264BBD nickname=yono1 sampled_on=2017-05-02T20:44:35 sampled_by=0.3.1.0-alpha-dev listed=1 confirmed_on=2017-04-25T13:14:11 confirmed_idx=0 pb_use_attempts=3.000000 pb_use_successes=3.000000 pb_circ_attempts=105.000000 pb_circ_successes=105.000000 pb_successful_circuits_closed=95.000000 pb_collapsed_circuits=10.000000 pb_timeouts=8.000000
Guard in=default rsa_id=62DA0256BBC28992D41CBAFB549FFD7C9B846A99 nickname=IRejectTorFoundatnN sampled_on=2017-05-21T02:25:50 sampled_by=0.3.1.0-alpha-dev listed=1 confirmed_on=2017-05-23T22:28:05 confirmed_idx=2

I figured that since there were three, and they were all confirmed, they would be my primary guards.

Also, my cached-microdesc-consensus file was about a day old.

When Tor starts, it says

May 25 20:58:06.155 [info] sampled_guards_update_from_consensus(): No live consensus; can't update sampled entry guards.

Ok, great, it's not going to go deleting or modifying any of my guards before it's even tried to load my consensus file from disk. Makes sense.

Then it goes through to update my three guards to say that they're not working:

May 25 20:58:06.155 [debug] entry_guard_set_filtered_flags(): Updated sampled guard onslaught ($BB119A5A4D5DA2BBB7B796ECC50E3C0F1D4FD910): filtered=0; reachable_filtered=0.
May 25 20:58:06.155 [debug] entry_guard_set_filtered_flags(): Updated sampled guard yono1 ($7369A0E14C59B11D78357EC5AFE573A259264BBD): filtered=0; reachable_filtered=0.
May 25 20:58:06.156 [debug] entry_guard_set_filtered_flags(): Updated sampled guard IRejectTorFoundatnN ($62DA0256BBC28992D41CBAFB549FFD7C9B846A99): filtered=0; reachable_filtered=0.

I'm guessing that happened because of entry_guards_update_filtered_sets() which got called from entry_guards_update_all(), but there are several possible paths to that function so I'm not sure which one it was. Maybe it's decided they're all down, since it hasn't even loaded a consensus yet, so they're all missing from the nonexistent consensus?

Then we get to:

May 25 20:58:06.156 [info] sample_reachable_filtered_entry_guards(): Trying to sample a reachable guard: We know of 0 in the USABLE_FILTERED set.
May 25 20:58:06.156 [info] sample_reachable_filtered_entry_guards():   (That isn't enough. Trying to expand the sample.)
May 25 20:58:06.156 [info] entry_guards_expand_sample(): Expanding the sample guard set. We have 3 guards in the sample, and 0 eligible guards to extend it with.
May 25 20:58:06.156 [info] entry_guards_expand_sample(): Not expanding the guard sample any further; just ran out of eligible guards
May 25 20:58:06.156 [info] sample_reachable_filtered_entry_guards():   (After filters [b], we have 0 guards to consider.)

Ok, great, we refuse to expand the guard list now. That's good because we don't have any consensus loaded yet.

Then I finish loading the state file, and load other stuff from my datadirectory, like the cached-microdesc-consensus file:

May 25 20:58:06.644 [info] A consensus needs 5 good signatures from recognized authorities for us to accept it. This one has 8 (dannenberg tor26 longclaw maatuska moria1 dizum gabelmoo Faravahar).
May 25 20:58:06.797 [info] microdesc_cache_reload(): Reloaded microdescriptor cache. Found 7298 descriptors.
May 25 20:58:06.812 [info] update_consensus_networkstatus_fetch_time_impl(): No live microdesc consensus; we should fetch one immediately.
May 25 20:58:06.812 [info] cell_ewma_set_scale_factor(): Enabled cell_ewma algorithm because of value in CircuitPriorityHalflifeMsec in consensus; scale factor is 0.793701 per 10 seconds
May 25 20:58:07.046 [info] networkstatus_set_current_consensus(): Loaded an expired consensus. Discarding.
May 25 20:58:07.046 [info] router_reload_consensus_networkstatus(): Couldn't load unverified consensus microdesc networkstatus from cache

Ok, fine, it's expired so we discarded it, no problem.

May 25 20:58:07.182 [info] update_consensus_bootstrap_attempt_downloads(): Launching microdesc bootstrap mirror networkstatus consensus download.
May 25 20:58:07.182 [notice] Starting with guard context "default"
May 25 20:58:07.182 [info] sample_reachable_filtered_entry_guards(): Trying to sample a reachable guard: We know of 0 in the USABLE_FILTERED set.
May 25 20:58:07.182 [info] sample_reachable_filtered_entry_guards():   (That isn't enough. Trying to expand the sample.)

Sounds good, I agree it's time to go get a fresh consensus.

May 25 20:58:07.182 [info] entry_guards_expand_sample(): Expanding the sample guard set. We have 3 guards in the sample, and 2220 eligible guards to extend it with.

Wait, what? Where did these 2220 eligible guards come from?

Did they get added to a list of potential eligible guards, when we were examining the old microdesc consensus -- the one that we then discarded because it was too old?

That theory sounds plausible:

$ grep "^s " cached-microdesc-consensus |grep Guard|grep V2Dir|wc -l
2224

That's bug number one.

So we proceed to add an eligible guard, since I have 0 eligible guards in my set:

May 25 20:58:07.182 [debug] compute_weighted_bandwidths(): Generated weighted bandwidths for rule weight as guard based on weights Wg=0.594700 Wm=0.594700 We=0.000000 Wd=0.000000 with total bw 0
May 25 20:58:07.182 [info] entry_guard_add_to_sample(): Adding $9285B22F7953D7874604EEE2B470609AD81C74E9~0x3d005 at 62.138.7.171 as to the entry guard sample set.
May 25 20:58:07.182 [debug] entry_guard_set_filtered_flags(): Updated sampled guard 0x3d005 ($9285B22F7953D7874604EEE2B470609AD81C74E9): filtered=1; reachable_filtered=1.

In fact, we add 20 of them like this. And these ones are filtered=1, reachable_filtered=1, because we just picked them out of, I guess, a consensus that said they were Running.

After we add the 20, we hit:

May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards(): Trying to sample a reachable guard: We know of 20 in the USABLE_FILTERED set.
May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards():   (After filters [b], we have 20 guards to consider.)
May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards():   (Selected 0x3d005 ($9285B22F7953D7874604EEE2B470609AD81C74E9).)
May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards(): Trying to sample a reachable guard: We know of 20 in the USABLE_FILTERED set.
May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards():   (After filters [b], we have 19 guards to consider.)
May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards():   (Selected colosimo ($51939625169E2C7E0DC83D38BAE628BDE67E9A22).)
May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards(): Trying to sample a reachable guard: We know of 20 in the USABLE_FILTERED set.
May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards():   (After filters [b], we have 18 guards to consider.)
May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards():   (Selected Tungurahua ($7CB15FA5CD985B9BBD6AC386C62C206A1F391C23).)

Ok, we've picked three. Then we see:

May 25 20:58:07.185 [info] entry_guards_update_primary(): Primary entry guards have changed. New primary guard list is: 
May 25 20:58:07.185 [info] entry_guards_update_primary():   1/3: 0x3d005 ($9285B22F7953D7874604EEE2B470609AD81C74E9)
May 25 20:58:07.185 [info] entry_guards_update_primary():   2/3: colosimo ($51939625169E2C7E0DC83D38BAE628BDE67E9A22)
May 25 20:58:07.185 [info] entry_guards_update_primary():   3/3: Tungurahua ($7CB15FA5CD985B9BBD6AC386C62C206A1F391C23)

I had three perfectly fine primary guards earlier, but I had marked them down, so I guess we have three new ones.

But then we proceed to ignore those three new ones too!

May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards():   (After filters [7], we have 17 guards to consider.)
May 25 20:58:07.185 [info] sample_reachable_filtered_entry_guards():   (Selected Yuman ($3265FB6279E142BFBB8BE08AA0582011D23ED2EF).)
May 25 20:58:07.185 [info] select_entry_guard_for_circuit(): No primary or confirmed guards available. Selected random guard Yuman ($3265FB6279E142BFBB8BE08AA0582011D23ED2EF) for circuit. Will try other guards before using this circuit.

That's bug number two.

It looks like it launches a consensus download attempt to Yuman smoothly:

May 25 20:58:07.185 [info] directory_send_command(): Downloading consensus from 37.187.177.2:9001 using /tor/status-vote/current/consensus-microdesc/0232AF+14C131+23D15D+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z

And it launches a parallel fetch to an authority too, just like it's supposed to:

May 25 20:58:07.185 [info] directory_send_command(): Downloading consensus from 154.35.175.225:443 using /tor/status-vote/current/consensus-microdesc/0232AF+14C131+23D15D+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z

Faravahar is way more responsive than whoever Yuman is, so by the time I get my one-hop circuit open to Yuman, I'm already partway through fetching the consensus from Faravahar:

May 25 20:58:07.824 [info] internal circ (length 1, last hop Yuman): $3265FB6279E142BFBB8BE08AA0582011D23ED2EF(open)
May 25 20:58:07.824 [debug] command_process_created_cell(): Moving to next skin.
May 25 20:58:07.824 [debug] circuit_send_next_onion_skin(): starting to send subsequent skin.
May 25 20:58:07.824 [info] circuit_send_next_onion_skin(): circuit built!
May 25 20:58:07.824 [info] connection_ap_handshake_attach_circuit(): Closing extra consensus fetch (to 37.187.177.2) since one is already downloading.

But then

May 25 20:58:07.825 [debug] conn_close_if_marked(): Cleaning up connection (fd -1).
May 25 20:58:07.825 [info] entry_guards_note_guard_failure(): Recorded failure for guard Yuman ($3265FB6279E142BFBB8BE08AA0582011D23ED2EF)

That's not very nice of us, since the guard didn't actually fail, we just opted not to use that circuit because another circuit was faster.

That's bug number three.

Ok, after a bunch of lines, I get my microdesc consensus from Faravahar:

May 25 20:58:16.296 [debug] Received response from directory server '154.35.175.225:443': 200 "OK" (purpose: 14, response size: 629424, compression: 2)

And we start acting on it:

May 25 20:58:16.764 [info] launch_descriptor_downloads(): Launching 5 requests for 2262 microdescs, 500 at a time
May 25 20:58:16.766 [info] select_entry_guard_for_circuit(): Selected primary guard Tungurahua ($7CB15FA5CD985B9BBD6AC386C62C206A1F391C23) for circuit.

and we happily fetch the missing microdescriptors using our 3 (new) primary guards.

There is this interesting tidbit:

May 25 20:58:18.032 [debug] fetch_from_buf_http(): headerlen 197, bodylen 127544.
May 25 20:58:18.032 [debug] Received response from directory server '109.236.90.209:443': 200 "OK" (purpose: 19, response size: 127741, compression: 2)
May 25 20:58:18.032 [info] make_guard_confirmed(): Marking colosimo ($51939625169E2C7E0DC83D38BAE628BDE67E9A22) as a confirmed guard (index 3)
May 25 20:58:18.032 [info] entry_guards_update_primary(): Primary entry guards have changed. New primary guard list is: 
May 25 20:58:18.032 [info] entry_guards_update_primary():   1/3: colosimo ($51939625169E2C7E0DC83D38BAE628BDE67E9A22) (confirmed)
May 25 20:58:18.032 [info] entry_guards_update_primary():   2/3: 0x3d005 ($9285B22F7953D7874604EEE2B470609AD81C74E9)
May 25 20:58:18.032 [info] entry_guards_update_primary():   3/3: Tungurahua ($7CB15FA5CD985B9BBD6AC386C62C206A1F391C23)
May 25 20:58:18.032 [info] entry_guards_note_guard_success(): Recorded success for primary confirmed guard colosimo ($51939625169E2C7E0DC83D38BAE628BDE67E9A22)

We marked our guard confirmed because we used it to fetch directory info? I believe that's what we programmed it to do, but maybe our definition of confirmed should be that we attached a 'real' (non dir fetch) stream to a 'real' (3 hop or more) circuit.

(We can call that bug number four if we like, but it's really more like feature request number one.)

Eventually we get enough microdescs to convince us we should start making circuits:

May 25 20:58:18.453 [debug] compute_frac_paths_available(): f_guard: 0.86, f_mid: 0.86, f_exit: 0.88
May 25 20:58:18.453 [notice] Bootstrapped 80%: Connecting to the Tor network
May 25 20:58:18.454 [debug] update_guard_selection_choice(): Staying with guard context "default" (no change)
May 25 20:58:18.454 [info] sampled_guards_update_from_consensus(): Updating sampled guard status based on received consensus.
May 25 20:58:18.454 [debug] sampled_guards_update_from_consensus(): Sampled guard onslaught ($BB119A5A4D5DA2BBB7B796ECC50E3C0F1D4FD910) is still listed.
May 25 20:58:18.454 [debug] sampled_guards_update_from_consensus(): Sampled guard yono1 ($7369A0E14C59B11D78357EC5AFE573A259264BBD) is still listed.

and we see those sampled_guards_update_from_consensus() lines for each of our 23 of our guards, followed by 23 of these lines, one for each guard:

May 25 20:58:18.454 [debug] entry_guard_set_filtered_flags(): Updated sampled guard onslaught ($BB119A5A4D5DA2BBB7B796ECC50E3C0F1D4FD910): filtered=1; reachable_filtered=1.
May 25 20:58:18.454 [debug] entry_guard_set_filtered_flags(): Updated sampled guard yono1 ($7369A0E14C59B11D78357EC5AFE573A259264BBD): filtered=1; reachable_filtered=1.

And then, oh hey, we get our original primary guards back!

May 25 20:58:18.455 [info] entry_guards_update_primary(): Primary entry guards have changed. New primary guard list is: 
May 25 20:58:18.455 [info] entry_guards_update_primary():   1/3: yono1 ($7369A0E14C59B11D78357EC5AFE573A259264BBD) (confirmed)
May 25 20:58:18.455 [info] entry_guards_update_primary():   2/3: onslaught ($BB119A5A4D5DA2BBB7B796ECC50E3C0F1D4FD910) (confirmed)
May 25 20:58:18.455 [info] entry_guards_update_primary():   3/3: IRejectTorFoundatnN ($62DA0256BBC28992D41CBAFB549FFD7C9B846A99) (confirmed)

And then we build a 3-hop circuit with yono1, as expected:

May 25 20:58:19.738 [info] exit circ (length 3, last hop digineo3): $7369A0E14C59B11D78357EC5AFE573A259264BBD(open) $0269165034C5586D6551CCCFA8940D2305948754(
open) $B21211A1A2C68F2D9E57E3C7AEAF4F04AFC10E7F(open)
May 25 20:58:19.738 [info] entry_guards_note_guard_success(): Recorded success for primary confirmed guard yono1 ($7369A0E14C59B11D78357EC5AFE573A259264BBD)
May 25 20:58:19.738 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.

#7176 Adapt and update AccessLabs' patches for reduced TOR memory consumption for embedded devices Core Tor/Tor Tor: 0.3.2.x-final enhancement Oct 21, 2012

These are a set of patches written by Access Labs. They claim that these patches reduce memory usage on small low memory devices.

The patches are in several different areas:

  • using anonymous mmap() for storing large chunks of data (instead of tempfiles)
  • persisting the keys into /etc/tor/keys, rather than putting them in /var (tmpfs on OpenWRT)
  • using fixed values for should_rebuild_md_cache() && router_should_rebuild_store()
  • reducing the age of microdesc (changing the compile time defines)
  • using gzipped files for storing cache

I am including the files here as one ticket item rather than 5, but it might make sense to break them up into separate issues.

The source for these changes is the TorWRT package from Access Labs: https://accesslabs.org/wiki/TorWRT


#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.2.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.


#21215 Lower the directory overhead for low-bandwidth clients Core Tor/Tor Tor: 0.3.2.x-final project Jan 12, 2017

This is a parent ticket for the actual implementation work of sponsor4. As we complete measurement (#21205) and design (#21209), we'll add child tickets here for the particular work we are going to accomplish.


#21213 Write and analyze proposals for fetching consensuses/microdescriptors less frequently? Core Tor/Tor Tor: 0.3.2.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.


#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]


#18140 Update dir-spec for "reasonably live" consensuses Core Tor/Tor Tor: 0.3.2.x-final defect Jan 24, 2016

In networkstatus_get_reasonably_live_consensus() and check_expired_networkstatus_callback(), tor has the concept of a "reasonably live" consensus. A consensus is reasonably live if it expired less than 24 hours ago.

This isn't in the directory spec, should it be?


#19537 Cryptic description for download GETINFO options Core Tor/Tor Tor: 0.3.2.x-final defect Jun 30, 2016

Hi there, descriptions for the recent spec addition are pretty cryptic...

"The serialized download status for the FLAV_MICRODESC consensus for whichever bootstrap state Tor is currently in."

I expect this description only makes sense to the feature's author. What is FLAV_MICRODESC? What does this 'serialized download status' mean? Since it discusses 'bootstrap state' I'm guessing this is only relevant when tor is first starting up (showing percentages complete)?


#19984 Use a better set of comparison/evaluation functions for deciding which connections to kill when OOS Core Tor/Tor Tor: 0.3.2.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.


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

#20534 Revise hard-coded download schedules Core Tor/Tor Tor: 0.3.2.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.2.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?


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