Tor issueshttps://gitlab.torproject.org/tpo/core/tor/-/issues2022-10-11T23:39:48Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25226Circuit cell queue can fill up memory2022-10-11T23:39:48ZDavid Gouletdgoulet@torproject.orgCircuit cell queue can fill up memoryA relay operator just reported this on 0.3.3.2-alpha:
https://lists.torproject.org/pipermail/tor-relays/2018-February/014496.html
In a nutshell, the OOM fired up with these logs:
```
Feb 12 18:54:55 tornode2 Tor[6362]: We're low on me...A relay operator just reported this on 0.3.3.2-alpha:
https://lists.torproject.org/pipermail/tor-relays/2018-February/014496.html
In a nutshell, the OOM fired up with these logs:
```
Feb 12 18:54:55 tornode2 Tor[6362]: We're low on memory (cell queues total alloc: 1602579792 buffer total alloc: 1388544, tor compress total alloc: 1586784 rendezvous cache total alloc: 489909). Killing circuits withover-long queues. (This behavior is controlled by MaxMemInQueues.)
Feb 12 18:54:56 tornode2 Tor[6362]: Removed 1599323088 bytes by killing 1 circuits; 39546 circuits remain alive. Also killed 0 non-linked directory connections.
```
Notice the ~1GB of cells for one single circuit? Somehow, there is an issue in tor that makes it possible to fill up the circuit cell queue while the scheduler is just not emptying that queue.
This really looks like the Sniper Attack: http://www.robgjansen.com/publications/sniper-ndss2014.pdfTor: 0.3.3.x-finalDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/25236dos: Document torrc default values in the man page when not in the consensus2022-10-11T23:39:48ZDavid Gouletdgoulet@torproject.orgdos: Document torrc default values in the man page when not in the consensusFrom:
https://trac.torproject.org/projects/tor/ticket/24902#comment:68From:
https://trac.torproject.org/projects/tor/ticket/24902#comment:68Tor: 0.3.3.x-finalDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/25248DoS mitgation: improve documentation2022-10-11T23:39:49ZcypherpunksDoS mitgation: improve documentation(some reason for opening this is: a relay operator seemed confused and started to modify the source instead of using these torrc settings)
https://lists.torproject.org/pipermail/tor-relays/2018-February/014503.html
building on top of le...(some reason for opening this is: a relay operator seemed confused and started to modify the source instead of using these torrc settings)
https://lists.torproject.org/pipermail/tor-relays/2018-February/014503.html
building on top of legacy/trac#25236
Lets add a high level overview of available DoS mitigations at the beginning of the section next to "The following options are useful only for a public relay. They control the Denial of Service mitigation subsystem."
as you did in the changelog already before going into the specific settings.
We could start by using a copy from your changelog:
https://gitweb.torproject.org/tor.git/tree/ChangeLog?h=tor-0.3.3.2-alpha#n8
something like:
"
Tor has 3 build-in mitigation options that can be individually enabled/disabled and fine-tuned, but by default Tor directory authorities will define reasonable values for relays and no explicit configuration is required to make use of these protections.
The mitigations are:
* First: if a single client address makes too many concurrent connections (~~>100~~ "too many" is configurable via XXX), hang up on further connections.
* Second: if a
single client IP address (v4 and v6 or does it just work with IPv4?) makes circuits too quickly (more than 3 per
second, with an allowed burst of 90) while also having too many
connections open (3), refuse new create cells for the next while
(1-2 hours).
* Third: if a client asks to establish a rendezvous
point to you directly, ignore the request. These defenses can be
manually controlled by new torrc options, but relays will also
take guidance from consensus parameters, so there's no need to
configure anything manually.
"
instead of the static values add the config options in brackets.
https://www.torproject.org/docs/tor-manual-dev.html.en#DoSCircuitCreationEnabled
Does not say what 0 and 1 means. Maybe use the same wording as you use for most other boolean settings:
"If this option is set to 1, ...
* The section "DENIAL OF SERVICE MITIGATION OPTIONS" refers to the consensus
for default values, lets tell the operator how to find the current consensus values so he has actually some information where they can say "that value is to low for me my system is idle" or "oh that is not defined in consensus" -> legacy/trac#25236
will these values show on https://consensus-health.torprojec.org?Tor: 0.3.3.x-finalDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/25249Spec/implementation deviation in C protover code2020-06-27T13:54:09ZNick MathewsonSpec/implementation deviation in C protover codeOur C protover code will reject any attempt to create a protover range ending with UINT32_MAX. But our spec says that we allow that.
I suggest that, since this case is basically unreasonable, we should amend the spec to reject it, and ...Our C protover code will reject any attempt to create a protover range ending with UINT32_MAX. But our spec says that we allow that.
I suggest that, since this case is basically unreasonable, we should amend the spec to reject it, and amend the code to reject it explicitly.
Found by Teor.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25250Infinite loop in Rust protover implementation (TROVE-2018-003)2020-06-27T13:54:09ZNick MathewsonInfinite loop in Rust protover implementation (TROVE-2018-003)Our rust protover implementation has a denial-of-service problem on certain inputs.
Found by Teor. Calling this a "low-severity", since by default it would be medium-severity, but the rust protover code is uncommonly used and experimental.Our rust protover implementation has a denial-of-service problem on certain inputs.
Found by Teor. Calling this a "low-severity", since by default it would be medium-severity, but the rust protover code is uncommonly used and experimental.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25251Fix TROVE-2018-004: bad consensus can trigger null pointer crash.2020-06-27T13:54:08ZNick MathewsonFix TROVE-2018-004: bad consensus can trigger null pointer crash.When checking their own versions against the subprotocol versions listed in a consensus document, Tor instances could be made to crash if the consensus was incorrectly formatted.
This is a low-severity bug, since it can only be exploite...When checking their own versions against the subprotocol versions listed in a consensus document, Tor instances could be made to crash if the consensus was incorrectly formatted.
This is a low-severity bug, since it can only be exploited by corrupting a majority of directory authorities. (And any attacker who can do that, can do far worse.)
We're tracking this one as TROVE-2018-004. It was present in 0.2.9.4-alpha and later. It is fixed in 0.2.9.15, 0.3.1.10, 0.3.2.10, and 0.3.3.3-alpha.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25252Rust implementation of protover code deviates from C in some cases2020-06-27T13:54:08ZNick MathewsonRust implementation of protover code deviates from C in some casesTeor found some cases where the Rust protover code deviates from the C protover code. We should fix all of these in 0.3.3.Teor found some cases where the Rust protover code deviates from the C protover code. We should fix all of these in 0.3.3.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25313Sandbox: Caught a bad syscall attempt (syscall poll)2020-06-27T13:54:05ZcypherpunksSandbox: Caught a bad syscall attempt (syscall poll)
```
(Sandbox) Caught a bad syscall attempt (syscall poll)
/usr/bin/tor(+0x1a5baa)[0x560fee34ebaa]
/lib/x86_64-linux-gnu/libc.so.6(__poll+0x10)[0x7fd66246c690]
/lib/x86_64-linux-gnu/libc.so.6(__poll+0x10)[0x7fd66246c690]
/lib/x86_6...
```
(Sandbox) Caught a bad syscall attempt (syscall poll)
/usr/bin/tor(+0x1a5baa)[0x560fee34ebaa]
/lib/x86_64-linux-gnu/libc.so.6(__poll+0x10)[0x7fd66246c690]
/lib/x86_64-linux-gnu/libc.so.6(__poll+0x10)[0x7fd66246c690]
/lib/x86_64-linux-gnu/libc.so.6(+0x11b573)[0x7fd6624a8573]
/lib/x86_64-linux-gnu/libc.so.6(+0x11c189)[0x7fd6624a9189]
/lib/x86_64-linux-gnu/libc.so.6(+0x1187f2)[0x7fd6624a57f2]
/lib/x86_64-linux-gnu/libc.so.6(+0x118a3e)[0x7fd6624a5a3e]
/lib/x86_64-linux-gnu/libc.so.6(getpwnam_r+0x1cd)[0x7fd6624443ed]
/lib/x86_64-linux-gnu/libc.so.6(getpwnam+0x90)[0x7fd662443d20]
/usr/bin/tor(tor_getpwnam+0x29)[0x560fee3369e9]
/usr/bin/tor(check_private_dir+0x9f)[0x560fee3480bf]
/usr/bin/tor(create_keys_directory+0x34)[0x560fee29b924]
/usr/bin/tor(init_keys+0x89)[0x560fee2439d9]
/usr/bin/tor(do_main_loop+0x54)[0x560fee1fd5b4]
/usr/bin/tor(tor_run_main+0x275)[0x560fee1fef25]
/usr/bin/tor(tor_main+0x3a)[0x560fee1f836a]
/usr/bin/tor(main+0x19)[0x560fee1f80d9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fd6623ad2b1]
/usr/bin/tor(_start+0x2a)[0x560fee1f812a]
```
config
```
OfflineMasterKey 1
RunAsDaemon 0
Log notice syslog
OutboundBindAddress xxxxxx
SocksPort 0
User xxxx
DataDirectory xxxxx
ORPort xxxxxxx
ORPort xxxxxxxxx
OutboundBindAddress xxxxxxx
DirPort xxxxxxxxx
ControlSocket 0
CookieAuthentication 0
Sandbox 1
ExitRelay 0
ExitPolicy reject *:*
```
os: debian 9 on KVM
reproducible with:
0.3.2.9-1~d90.stretch+1
0.3.3.2-alpha-1~d90.stretch+1
0.3.4.0-alpha-dev-20180220T150525Z-1~d90.stretch+1Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25316Assertion failure in scale_active_circuits2020-06-27T13:54:05ZTracAssertion failure in scale_active_circuitsRelay 855BC2DABE24C861CD887DB9B2E950424B49FC34 crashed with the following log entries:
```
Feb 20 14:33:40.000 [err] tor_assertion_failed_(): Bug: ../src/or/circuitmux_ewma.c:711: scale_active_circuits: Assertion e->last_adjusted_tick ==...Relay 855BC2DABE24C861CD887DB9B2E950424B49FC34 crashed with the following log entries:
```
Feb 20 14:33:40.000 [err] tor_assertion_failed_(): Bug: ../src/or/circuitmux_ewma.c:711: scale_active_circuits: Assertion e->last_adjusted_tick == pol->active_circuit_pqueue_last_recalibrated failed; aborting. (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: Assertion e->last_adjusted_tick == pol->active_circuit_pqueue_last_recalibrated failed in scale_active_circuits at ../src/or/circuitmux_ewma.c:711. Stack trace: (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(log_backtrace+0x42) [0x7f4b7ab65fb2] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(tor_assertion_failed_+0x9f) [0x7f4b7ab80b3f] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(+0xe74b2) [0x7f4b7aac74b2] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(circuitmux_notify_xmit_cells+0xdb) [0x7f4b7aac5a7b] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(channel_flush_from_first_active_circuit+0x269) [0x7f4b7aa5b7d9] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(channel_flush_some_cells+0xe4) [0x7f4b7aaaf8d4] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(+0xbd369) [0x7f4b7aa9d369] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(+0xbb2a2) [0x7f4b7aa9b2a2] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x414) [0x7f4b7a0ee254] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(do_main_loop+0x255) [0x7f4b7aa35d75] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(tor_main+0x1e75) [0x7f4b7aa397d5] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(main+0x19) [0x7f4b7aa31539] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f4b79103ead] (on Tor 0.3.2.9 )
Feb 20 14:33:40.000 [err] Bug: /usr/bin/tor(+0x51589) [0x7f4b7aa31589] (on Tor 0.3.2.9 )
```
Relay runs on Debian wheezy. uname -a:
Linux 3.2.0-5-amd64 #1 SMP Debian 3.2.96-3 x86_64 GNU/Linux
Uptime before the crash was 23 days. Memory and CPU usage was normal:
```
Feb 20 12:55:12.000 [notice] Heartbeat: Tor's uptime is 23 days 17:59 hours, with 30352 circuits open. I've sent 20574.36 GB and received 20125.28 GB.
```
**Trac**:
**Username**: LogformeTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25323Create an official tor-rust-dependencies.git repository2020-06-27T13:54:04ZNick MathewsonCreate an official tor-rust-dependencies.git repositoryRight now, our tor-rust-dependencies repository lives in Sebastian's namespace. We should turn it into an official repository in the root namespace, and adjust our submodules config and our documentation accordingly.
We should also fig...Right now, our tor-rust-dependencies repository lives in Sebastian's namespace. We should turn it into an official repository in the root namespace, and adjust our submodules config and our documentation accordingly.
We should also figure out what our plan is for keeping the dependencies in it up-to-date.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25378Log domain list is out of sync in tor.1.txt2021-07-22T16:20:50ZAlexander Færøyahf@torproject.orgLog domain list is out of sync in tor.1.txtOur list of log domains in the man page is out of sync.Our list of log domains in the man page is out of sync.Tor: 0.3.3.x-finalAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/25380Transparent proxy not working with linux kernel 4.15.62020-06-27T13:54:01ZTracTransparent proxy not working with linux kernel 4.15.6I dunno if yous test with da latest kernel but transparent proxy is not working at all with verion 4.15.6
If I were shooting from the hip or throwing darts blindfolded I would probably blame change 8f2f8993e0f69f4f8d5afe3873158f723daac...I dunno if yous test with da latest kernel but transparent proxy is not working at all with verion 4.15.6
If I were shooting from the hip or throwing darts blindfolded I would probably blame change 8f2f8993e0f69f4f8d5afe3873158f723daacb31 but I am not that kind of person.
The symptoms are tor process gets stuck in the getopt for the original destination address (in connection_edge.c) ipv4 transprarent proxy code and cannot be killed because the system call just sits there UNINTERRUPTIBLE
**Trac**:
**Username**: vafanTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25388document how to allow partially failing builds in Travis CI2020-06-27T13:54:01ZTaylor Yudocument how to allow partially failing builds in Travis CISometimes configurations that fewer developers regularly build with get merged with changes that break our Travis CI builds.
We should make it easier to temporarily allow those builds to fail while people work on getting them fixed, bec...Sometimes configurations that fewer developers regularly build with get merged with changes that break our Travis CI builds.
We should make it easier to temporarily allow those builds to fail while people work on getting them fixed, because sometimes it takes a while. This can include adding commented-out `allow_failure` clauses.Tor: 0.3.3.x-finalTaylor YuTaylor Yuhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25401Transparent proxy stopped working after Linux kernel update to version 4.4.11...2020-06-27T13:54:00ZTracTransparent proxy stopped working after Linux kernel update to version 4.4.118 that fixes Spectre variant 1This happens on a fully updated Slackware64-14.2 system with tor 0.3.2.9 after an update to kernel 4.4.118 that fixes Spectre variant 1. Same version of tor worked fine with a few previous 4.4.x kernel versions (4.4.115, 4.4.111, 4.4.88)...This happens on a fully updated Slackware64-14.2 system with tor 0.3.2.9 after an update to kernel 4.4.118 that fixes Spectre variant 1. Same version of tor worked fine with a few previous 4.4.x kernel versions (4.4.115, 4.4.111, 4.4.88). Tor process freezes in uninterruptible state as soon as a program anonymized using this guideline https://trac.torproject.org/projects/tor/wiki/doc/TransparentProxy#Transparentlyanonymizingtrafficforaspecificuser tries to get online. Symptoms are similar to the ones described in this ticket https://trac.torproject.org/projects/tor/ticket/25380
More technical details from two different sources that were able to reproduce the issue independently can be found in this forum thread https://www.linuxquestions.org/questions/slackware-14/address-already-in-use-errors-when-trying-to-restart-tor-4175624554/
**Trac**:
**Username**: FlinchXTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25415moria1 seg faults on testing relay reachability2020-06-27T13:54:00ZRoger Dingledinemoria1 seg faults on testing relay reachability```
[...]
Mar 03 15:09:16.138 [notice] This version of Tor (0.3.3.3-alpha-dev) is newer than any recommended version, according to the directory authorities. Recommended versions are: 0.2.5.16,0.2.5.17,0.2.9.14,0.2.9.15,0.3.1.9,0.3.1.10,...```
[...]
Mar 03 15:09:16.138 [notice] This version of Tor (0.3.3.3-alpha-dev) is newer than any recommended version, according to the directory authorities. Recommended versions are: 0.2.5.16,0.2.5.17,0.2.9.14,0.2.9.15,0.3.1.9,0.3.1.10,0.3.2.8-rc,0.3.2.9,0.3.2.10,0.3.3.1-alpha,0.3.3.2-alpha,0.3.3.3-alpha
============================================================ T= 1520107762
Tor 0.3.3.3-alpha-dev (git-6d44cf66c7cca6e0) died: Caught signal 11
../git/src/or/tor(+0x18d2aa)[0x7f7b748152aa]
../git/src/or/tor(tor_memeq+0x27)[0x7f7b748355e7]
../git/src/or/tor(tor_memeq+0x27)[0x7f7b748355e7]
../git/src/or/tor(router_ed25519_id_is_me+0x2a)[0x7f7b7472472a]
../git/src/or/tor(connection_or_connect+0x1a8)[0x7f7b747a1ad8]
../git/src/or/tor(channel_tls_connect+0xaa)[0x7f7b74758aaa]
../git/src/or/tor(dirserv_single_reachability_test+0xa8)[0x7f7b747c4108]
../git/src/or/tor(routerlist_descriptors_added+0x90)[0x7f7b7472b0a0]
../git/src/or/tor(router_load_routers_from_string+0x438)[0x7f7b747336a8]
../git/src/or/tor(+0xab81c)[0x7f7b7473381c]
../git/src/or/tor(router_reload_router_list+0x26)[0x7f7b74733926]
../git/src/or/tor(do_main_loop+0x2fb)[0x7f7b746db17b]
../git/src/or/tor(tor_run_main+0x29b)[0x7f7b746db88b]
../git/src/or/tor(tor_main+0x43)[0x7f7b746d61a3]
../git/src/or/tor(main+0x19)[0x7f7b746d6039]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f7b731f8d1d]
../git/src/or/tor(+0x4df49)[0x7f7b746d5f49]
Aborted
```
```
#0 0x00007ffff7ca55e7 in tor_memeq (a=<value optimized out>,
b=<value optimized out>, sz=<value optimized out>)
at src/common/di_ops.c:110
#1 0x00007ffff7b9472a in router_ed25519_id_is_me (id=<value optimized out>)
at src/or/routerkeys.c:1248
#2 0x00007ffff7c11ad8 in connection_or_connect (_addr=0x7fffffffe180,
port=443, id_digest=0x7fffeb96c8ac "\fÚ0ÍÛRku>K§\t8p;ïl´¸áv\237\232Z",
ed_id=0x20, chan=0x7ffffecb8230) at src/or/connection_or.c:1210
#3 0x00007ffff7bc8aaa in channel_tls_connect (addr=0x7fffffffe180, port=443,
id_digest=0x7fffeb96c8ac "\fÚ0ÍÛRku>K§\t8p;ïl´¸áv\237\232Z", ed_id=0x20)
at src/or/channeltls.c:206
#4 0x00007ffff7c34108 in dirserv_single_reachability_test (
now=<value optimized out>, router=0x7fffeb96c880) at src/or/dirserv.c:3405
#5 0x00007ffff7b9b0a0 in routerlist_descriptors_added (sl=0x7ffffb9b2900,
from_cache=1) at src/or/routerlist.c:4280
#6 0x00007ffff7ba36a8 in router_load_routers_from_string (
s=0x7fffee9720f8 "", eos=<value optimized out>,
saved_location=<value optimized out>, requested_fingerprints=0x0,
descriptor_digests=0, prepend_annotations=<value optimized out>)
at src/or/routerlist.c:4415
#7 0x00007ffff7ba381c in router_reload_router_list_impl (store=0x7ffff81306c0)
at src/or/routerlist.c:1565
#8 0x00007ffff7ba3926 in router_reload_router_list ()
at src/or/routerlist.c:1607
#9 0x00007ffff7b4b17b in do_main_loop () at src/or/main.c:2671
#10 0x00007ffff7b4b88b in tor_run_main (tor_cfg=<value optimized out>)
at src/or/main.c:4064
#11 0x00007ffff7b461a3 in tor_main (argc=3, argv=0x7fffffffe638)
at src/or/tor_api.c:84
#12 0x00007ffff7b46039 in main (argc=<value optimized out>,
argv=<value optimized out>) at src/or/tor_main.c:32
```
```
#0 0x00007ffff7ca55e7 in tor_memeq (a=<value optimized out>,
b=<value optimized out>, sz=<value optimized out>)
at src/common/di_ops.c:110
110 const uint8_t byte_diff = *ba++ ^ *bb++;
(gdb) up
#1 0x00007ffff7b9472a in router_ed25519_id_is_me (id=<value optimized out>)
at src/or/routerkeys.c:1248
1248 ed25519_pubkey_eq(id, &master_identity_key->pubkey);
(gdb) up
#2 0x00007ffff7c11ad8 in connection_or_connect (_addr=0x7fffffffe180,
port=443, id_digest=0x7fffeb96c8ac "\fÚ0ÍÛRku>K§\t8p;ïl´¸áv\237\232Z",
ed_id=0x20, chan=0x7ffffecb8230) at src/or/connection_or.c:1210
1210 if (server_mode(options) && router_ed25519_id_is_me(ed_id)) {
```
```
(gdb) print ed_id
$4 = (const ed25519_public_key_t *) 0x20
```Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25465Transparent proxy hangs after kernel update to 4.15.6-200.fc26.x86_642020-06-27T13:53:58ZTracTransparent proxy hangs after kernel update to 4.15.6-200.fc26.x86_64Long running stable router box (FC26), tor transparent proxy has been working great for years. Tor now crashes and hangs when application attempts to connect through transparent proxy (TransProxy 9040) etc:
# ps -auxf | grep toranon
to...Long running stable router box (FC26), tor transparent proxy has been working great for years. Tor now crashes and hangs when application attempts to connect through transparent proxy (TransProxy 9040) etc:
# ps -auxf | grep toranon
toranon 2479 0.1 0.2 80920 34640 ? Ds 19:45 0:00 /usr/bin/tor --runasdaemon 0 --defaults-torrc /usr/share/tor/defaults-torrc -f /etc/tor/torrc
Attempted to downgrade tor back to 0.2.9.10 with dnf... No joy.
Attempted to downgrade openssl to 1.1.0f-4... No joy
When I attempt to connect, say with curl, the last 2 lines in debug.log are:
Mar 11 20:06:20.000 [debug] connection_add_impl(): new conn type Socks, socket 16, address 172.16.111.3, n_conns 7.
Mar 11 20:06:20.000 [debug] connection_ap_process_transparent(): entered.
curl hangs, tor hangs (STATUS Ds), have to reboot to clear it.
Suggestions welcome.
**Trac**:
**Username**: freerjTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25479Fix win32 crash in bench.c2020-06-27T13:53:58ZIsis LovecruftFix win32 crash in bench.cOn the mailing lists, Gisle Vanem [reported](https://lists.torproject.org/pipermail/tor-dev/2018-March/012998.html) a crash while running `bench.exe` on a windows system. On first sight, it appeared to be possibly related to calling `opt...On the mailing lists, Gisle Vanem [reported](https://lists.torproject.org/pipermail/tor-dev/2018-March/012998.html) a crash while running `bench.exe` on a windows system. On first sight, it appeared to be possibly related to calling `options_new()` from `bench.c`'s `main()`, but Gisle [provided a patch](https://lists.torproject.org/pipermail/tor-dev/2018-March/013005.html) which reportedly fixes the crash by calling `init_protocol_warning_severity_level()` which instead suggests that the crash was due to calling `init_logging()` (which calls `tor_mutex_init()`, which then calls `InitializeCriticalSection()`). The [MSDN documentation](https://msdn.microsoft.com/en-us/library/windows/desktop/ms683472(v=vs.85).aspx) for `InitializeCriticalSection()` states that has slightly different behaviours during edge cases for different windows flavours, so that could possibly have been the cause of the issue?Tor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25512Tor in-process restart fails to write auth cookie2020-06-27T13:53:55ZTracTor in-process restart fails to write auth cookieI integrated latest Tor master on 2018-03-15 into [Tor.framework](http://github.com/iCepa/Tor.framework/) resp. [OnionBrowser 2](http://github.com/mtigas/OnionBrowser). Shutdown with the improved `SIGNAL SHUTDOWN` seems to work just fine...I integrated latest Tor master on 2018-03-15 into [Tor.framework](http://github.com/iCepa/Tor.framework/) resp. [OnionBrowser 2](http://github.com/mtigas/OnionBrowser). Shutdown with the improved `SIGNAL SHUTDOWN` seems to work just fine.
When restarting Tor, however, it turns out, that the auth cookie is not written to the file system on the second time. First time works, file obviously gets deleted on `SHUTDOWN` but is not recreated on second start.
There is an according log entry the first time:
[info] init_cookie_authentication: Generated auth cookie file in '"/var/mobile/Containers/Data/Application/0653FD89-2D17-477A-B541-FC53F1A29EBD/Library/Caches/tor/control_auth_cookie"'.
This is **not** appearing on restart.
**Trac**:
**Username**: tlaTor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25517TROVE-2018-0052021-08-23T15:16:33ZIsis LovecruftTROVE-2018-005Tracking issue for TROVE-2018-005.
(The bug here is a memory-related denial-of-service attack, but only applies to directory authorities. They've all been informed.)Tracking issue for TROVE-2018-005.
(The bug here is a memory-related denial-of-service attack, but only applies to directory authorities. They've all been informed.)Tor: 0.3.3.x-finalIsis LovecruftIsis Lovecrufthttps://gitlab.torproject.org/tpo/core/tor/-/issues/25557DDOS on HiddenService2020-06-27T13:53:53ZTracDDOS on HiddenServiceHello.
I installed the torus on my server (debian 8), included in torrc HiddenService.
.onion domains are working. But I ran into the problem, the DDOS attack on HiddenService, at this point the TOR process consumes 100% of the processor...Hello.
I installed the torus on my server (debian 8), included in torrc HiddenService.
.onion domains are working. But I ran into the problem, the DDOS attack on HiddenService, at this point the TOR process consumes 100% of the processor core and the domains stop working.
NumCPUs does not work, the TOP process still consumes 100% of the kernel.
Tor version 0.3.3.3-alpha (tried different)
What options for solving the problem can you advise?
Dump of traffic http://dropmefiles.com/Vdnu2
**Trac**:
**Username**: myxaxerTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25560test all rust crates for realsies2020-06-27T13:53:53ZIsis Lovecrufttest all rust crates for realsiesAfter we merged legacy/trac#23881, it seems the tests in the `tor_log` crate aren't being run because there's an array in `src/test/test_rust.sh` that we didn't add the crate name to. I propose making that shell script automatically find...After we merged legacy/trac#23881, it seems the tests in the `tor_log` crate aren't being run because there's an array in `src/test/test_rust.sh` that we didn't add the crate name to. I propose making that shell script automatically find the crates available and run their tests, e.g.
```
manifests=`find ${abs_top_srcdir:-.}/src/rust/ -mindepth 2 -maxdepth 2 -name 'Cargo.toml'`
```
(Currently, we're only running tests for `crates="protover tor_util smartlist tor_allocate"`.)
As a side-note, I also think we should be calling cargo with --verbose so that our test logs actually tell us when something's wrong, e.g. for legacy/trac#24795 it would help.Tor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25581Inconsistent underscore config options (for vanguard options)2020-06-27T13:53:52ZDamian JohnsonInconsistent underscore config options (for vanguard options)Hi lovely tor folks. In December new **_HSLayer2Nodes** and **_HSLayer3Nodes** torrc options were added...
https://gitweb.torproject.org/tor.git/commit/?id=20a3f61
These are unusual in a couple ways...
* Tor uses proceeding underscore...Hi lovely tor folks. In December new **_HSLayer2Nodes** and **_HSLayer3Nodes** torrc options were added...
https://gitweb.torproject.org/tor.git/commit/?id=20a3f61
These are unusual in a couple ways...
* Tor uses proceeding underscores to indicate that a torrc option is private. These shouldn't appear in the tor manual, which these do.
* Private options start with two underscores, not one.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25582Manual includes non-existant ExitPolicyDefault option2020-06-27T13:53:52ZDamian JohnsonManual includes non-existant ExitPolicyDefault optionBack in November I made a few manual fixes which included making its **ExitPolicyDefault** line visible...
https://gitweb.torproject.org/tor.git/commit/?id=3563a2c
On reflection the tor codebase doesn't look to include any such option....Back in November I made a few manual fixes which included making its **ExitPolicyDefault** line visible...
https://gitweb.torproject.org/tor.git/commit/?id=3563a2c
On reflection the tor codebase doesn't look to include any such option. If it wasn't for a torrc option then I'm unsure what ExitPolicyDefault was in reference to...
Most likely we should just drop it from the manual.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25617unable to resolve DNS requests from control port, regression2020-06-27T13:53:51Zstarlightunable to resolve DNS requests from control port, regression```
setevents addrmap
250 OK
resolve blog.torproject.org
250 OK
650 ADDRMAP blog.torproject.org <error> "2018-03-25 08:39:54" error=yes EXPIRES="2018-03-25 12:39:54" CACHED="NO"
```
```
Mar 25 08:39:55 Tor[]: Refusing to connect to hos...```
setevents addrmap
250 OK
resolve blog.torproject.org
250 OK
650 ADDRMAP blog.torproject.org <error> "2018-03-25 08:39:54" error=yes EXPIRES="2018-03-25 12:39:54" CACHED="NO"
```
```
Mar 25 08:39:55 Tor[]: Refusing to connect to hostname [scrubbed] because Port has NoDNSRequest set.
```Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25629fix CID 14309322020-06-27T13:53:50ZTaylor Yufix CID 1430932Coverity found a null pointer reference in nodelist_add_microdesc().
This is almost certainly impossible assuming that the routerstatus_t
returned by router_get_consensus_status_by_descriptor_digest() always
corresponds to an entry in th...Coverity found a null pointer reference in nodelist_add_microdesc().
This is almost certainly impossible assuming that the routerstatus_t
returned by router_get_consensus_status_by_descriptor_digest() always
corresponds to an entry in the nodelist.Tor: 0.3.3.x-finalTaylor YuTaylor Yuhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25661RendPostPeriod and HiddenServiceAuthorizeClient are v2 only2021-09-30T13:46:29ZteorRendPostPeriod and HiddenServiceAuthorizeClient are v2 onlyRendPostPeriod and HiddenServiceAuthorizeClient only apply to v2 onion services. We should update the man page so this is clearer.RendPostPeriod and HiddenServiceAuthorizeClient only apply to v2 onion services. We should update the man page so this is clearer.Tor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25667LZMA/ZSTD descriptor compression support2020-06-27T13:53:48ZDamian JohnsonLZMA/ZSTD descriptor compression supportHi lovely core tor folks. I've been working on Stem support for spec 278 which was merged in tor 0.3.1.1 but I'm struggling to find an example of it working in practice...
https://gitweb.torproject.org/torspec.git/commit/?id=1cb56af
htt...Hi lovely core tor folks. I've been working on Stem support for spec 278 which was merged in tor 0.3.1.1 but I'm struggling to find an example of it working in practice...
https://gitweb.torproject.org/torspec.git/commit/?id=1cb56af
https://gitweb.torproject.org/user/atagar/stem.git/commit/?h=compression
Moria1 is running tor 0.3.4.0 so it definitely should have lzma and zstd compression support, but when I query its dirport only the identity and deflate headers seem to work...
```
% curl --header "Accept-Encoding: identity" 128.31.0.39:9131/tor/server/fp/9695DFC35FFEB861329B9F1AB04C46397020CE31
router moria1 128.31.0.34 9101 0 9131
identity-ed25519
-----BEGIN ED25519 CERT-----
AQQABnxNAQS9ja600v/ZodOUiu7NepTkbPIOrFPgEVQE+03rGBtPAQAgBADKnR/C
2nhpr9UzJkkbPy83sqbfNh63VgFnCpkSTULAcq52z8xM7raRDCiTJTu/FK/BJGgE
dJcFQ8MgZJOuYgFKcMVyQ6j2FGbhDI0zQTK1+TAPNRG4ixiF7h7wqDT9Ugw=
-----END ED25519 CERT-----
master-key-ed25519 yp0fwtp4aa/VMyZJGz8vN7Km3zYet1YBZwqZEk1CwHI
platform Tor 0.3.4.0-alpha-dev on Linux
...
```
```
% curl --header "Accept-Encoding: deflate" 128.31.0.39:9131/tor/server/fp/9695DFC35FFEB861329B9F1AB04C46397020CE31
[ compressed data ]
```
```
% curl --header "Accept-Encoding: x-zstd" 128.31.0.39:9131/tor/server/fp/9695DFC35FFEB861329B9F1AB04C46397020CE31
[ uncompressed data, same as 'identity' ]
% curl --header "Accept-Encoding: x-tor-lzma" 128.31.0.39:9131/tor/server/fp/9695DFC35FFEB861329B9F1AB04C46397020CE31
[ uncompressed data, same as 'identity' ]
```Tor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25679Default for TOR_RUST_DEPENDENCIES is wrong?2020-06-27T13:53:46ZNick MathewsonDefault for TOR_RUST_DEPENDENCIES is wrong?Try building Tor using the tor-rust-dependencies submodule, without actually setting TOR_RUST_DEPENDENCIES. It's supposed to work, but it doesn't: it looks at the wrong directory.Try building Tor using the tor-rust-dependencies submodule, without actually setting TOR_RUST_DEPENDENCIES. It's supposed to work, but it doesn't: it looks at the wrong directory.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25691Bridges don't work: Non-fatal assertion !(exit_ei == NULL) failed in onion_pi...2020-06-27T13:53:46ZteorBridges don't work: Non-fatal assertion !(exit_ei == NULL) failed in onion_pick_cpath_exitWhen running bridges-min and bridges+ipv6-min in chutney on macOS 10.13, Apple clang 9.0.0 with Xcode 9.2:
```
Apr 03 08:16:13.578 [info] circuit_predict_and_launch_new: Have 0 clean circs (0 internal), need another exit circ.
Apr 03 0...When running bridges-min and bridges+ipv6-min in chutney on macOS 10.13, Apple clang 9.0.0 with Xcode 9.2:
```
Apr 03 08:16:13.578 [info] circuit_predict_and_launch_new: Have 0 clean circs (0 internal), need another exit circ.
Apr 03 08:16:13.578 [info] choose_good_exit_server_general: Found 1 servers that might support 0/0 pending connections.
Apr 03 08:16:13.579 [info] choose_good_exit_server_general: Chose exit server '$2E832C796F35B96C3854941B01FF4E51E0968E24~test002r at 127.0.0.1'
Apr 03 08:16:13.580 [warn] tor_bug_occurred_: Bug: src/or/circuitbuild.c:2390: onion_pick_cpath_exit: Non-fatal assertion !(exit_ei == NULL) failed. (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.585 [warn] Bug: Non-fatal assertion !(exit_ei == NULL) failed in onion_pick_cpath_exit at src/or/circuitbuild.c:2390. Stack trace: (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.586 [warn] Bug: 0 tor 0x00665f83 log_backtrace + 67 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.587 [warn] Bug: 1 tor 0x006e0ad7 tor_bug_occurred_ + 503 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.587 [warn] Bug: 2 tor 0x0011843d circuit_establish_circuit + 18621 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.588 [warn] Bug: 3 tor 0x00186560 circuit_launch_by_extend_info + 992 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.589 [warn] Bug: 4 tor 0x0017f868 circuit_build_needed_circs + 3784 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.590 [warn] Bug: 5 tor 0x0044b33c second_elapsed_callback + 1468 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.591 [warn] Bug: 6 tor 0x0075b2f1 periodic_timer_cb + 129 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.592 [warn] Bug: 7 libevent-2.1.6.dylib 0x0104f6f3 event_process_active_single_queue + 1289 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.593 [warn] Bug: 8 libevent-2.1.6.dylib 0x0104bf12 event_base_loop + 1109 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.594 [warn] Bug: 9 tor 0x00449fd9 do_main_loop + 3289 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.595 [warn] Bug: 10 tor 0x00453990 tor_run_main + 704 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.596 [warn] Bug: 11 tor 0x006585a7 tor_main + 71 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.597 [warn] Bug: 12 tor 0x000a3546 main + 38 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.598 [warn] Bug: 13 libdyld.dylib 0xa75576e1 start + 1 (on Tor 0.3.4.0-alpha-dev 3df954549232bf55)
Apr 03 08:16:13.599 [info] circuit_mark_for_close_: Circuit 0 (id: 2) marked for close at src/or/circuitbuild.c:479 (orig reason: -2, new reason: 0)
Apr 03 08:16:13.600 [info] circuit_free_: Circuit 0 (id: 2) has been freed.
```
Other networks also log this bug but don't fail.
```
$ clang --version
Apple LLVM version 9.0.0 (clang-900.0.39.2)
Target: x86_64-apple-darwin17.3.0
...
```Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25692onion_extend_cpath: Non-fatal assertion info || client failed.2020-06-27T13:53:46ZNick Mathewsononion_extend_cpath: Non-fatal assertion info || client failed.When running "make test-network-all", I see a bunch of these errors:
```
Apr 02 18:46:57.375 [warn] Bug: Non-fatal assertion info || client failed in onion_extend_cpath at src/or/circuitbuild.c:2772. Stack trace: (on Tor 0.3.4.0-alpha-d...When running "make test-network-all", I see a bunch of these errors:
```
Apr 02 18:46:57.375 [warn] Bug: Non-fatal assertion info || client failed in onion_extend_cpath at src/or/circuitbuild.c:2772. Stack trace: (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(log_backtrace+0x43) [0x55a0c255ee03] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(tor_bug_occurred_+0xb9) [0x55a0c257a3c9] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(circuit_establish_circuit+0x732) [0x55a0c24b2ae2] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(circuit_launch_by_extend_info+0x8c) [0x55a0c24c487c] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(circuit_build_needed_circs+0x2e7) [0x55a0c24c4ef7] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(+0x8e078) [0x55a0c2430078] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /lib64/libevent-2.0.so.5(event_base_loop+0x7a9) [0x7f2fa8e2df19] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(do_main_loop+0x245) [0x55a0c2430bf5] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(tor_run_main+0x1015) [0x55a0c24330b5] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(tor_main+0x3a) [0x55a0c242b79a] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(main+0x19) [0x55a0c242b529] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /lib64/libc.so.6(__libc_start_main+0xea) [0x7f2fa7468f2a] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Bug: /home/nickm/src/tor/src/or/tor(_start+0x2a) [0x55a0c242b57a] (on Tor 0.3.4.0-alpha-dev 386116d52ac5f869)
Apr 02 18:46:57.375 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
```
I don't seem to get this on 0.3.3, and neither does Teor.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25705Refactor circuit_build_failed to separate build vs path failures2020-06-27T13:53:45ZMike PerryRefactor circuit_build_failed to separate build vs path failuresWe should not give up on the network, our TLS conn, or our guard in the event of path failures (which can happen if we're low on mds, and/or if the user set a bunch of path-restricting torrc options).
I think this might want to be a bac...We should not give up on the network, our TLS conn, or our guard in the event of path failures (which can happen if we're low on mds, and/or if the user set a bunch of path-restricting torrc options).
I think this might want to be a backport. It should also handle legacy/trac#25347.Tor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25732Rust files not all included with Tor.2020-06-27T13:53:44ZNick MathewsonRust files not all included with Tor.We broke our "make dist" when we added strings.rs, and it remains broken now. We need to include all of our .rs files in our tarball, or we can't build.We broke our "make dist" when we added strings.rs, and it remains broken now. We need to include all of our .rs files in our tarball, or we can't build.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25824Integrate circuit max_cell_queue_size killer with DoS heartbeats2022-10-11T23:39:49ZRoger DingledineIntegrate circuit max_cell_queue_size killer with DoS heartbeatsWe just merged legacy/trac#25226 so relays can kill circuits that queue up too many cells.
But we're nervous about picking a threshold that isn't super high, since there's no feedback about whether relays are hitting this event in the w...We just merged legacy/trac#25226 so relays can kill circuits that queue up too many cells.
But we're nervous about picking a threshold that isn't super high, since there's no feedback about whether relays are hitting this event in the wild: the logs are protocol-warn, so nobody, not us not them, will even know if it happens.
teor suggested that we could tie the circuit killing into the DoS heartbeat logs. Something like "and I killed x circuits that had too many cells queued".
This sounds to me like a great idea.Tor: 0.3.3.x-finalDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/25857::/128 is not the IPv6 equivalent of 0.0.0.0/02021-07-22T16:20:51ZTrac::/128 is not the IPv6 equivalent of 0.0.0.0/0The [man page of tor](https://gitweb.torproject.org/tor.git/tree/doc/tor.1.txt#n1837) states that "::/128" is the IPv6 equivalent of IPv4's "0.0.0.0/0" and that is not correct.
The equivalent of "0.0.0.0/0" in IPv6 is "::/0"
The IPv4 e...The [man page of tor](https://gitweb.torproject.org/tor.git/tree/doc/tor.1.txt#n1837) states that "::/128" is the IPv6 equivalent of IPv4's "0.0.0.0/0" and that is not correct.
The equivalent of "0.0.0.0/0" in IPv6 is "::/0"
The IPv4 equivalent of "::/128" would be "0.0.0.0/32".
https://en.wikipedia.org/wiki/IPv6_address#Unicast_addresses
**Trac**:
**Username**: CTassisFTor: 0.3.3.x-finalDamian JohnsonDamian Johnsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25912CID 1435130: Incorrect expression (COPY_PASTE_ERROR)2020-06-27T13:53:38ZGeorge KadianakisCID 1435130: Incorrect expression (COPY_PASTE_ERROR)Seems like legacy/trac#23693 caused the following coverity warning:
```
** CID 1435130: Incorrect expression (COPY_PASTE_ERROR)
/src/or/router.c: 153 in dup_onion_keys()
________________________________________________________________...Seems like legacy/trac#23693 caused the following coverity warning:
```
** CID 1435130: Incorrect expression (COPY_PASTE_ERROR)
/src/or/router.c: 153 in dup_onion_keys()
________________________________________________________________________________________________________
*** CID 1435130: Incorrect expression (COPY_PASTE_ERROR)
/src/or/router.c: 153 in dup_onion_keys()
147 tor_assert(key);
148 tor_assert(last);
149 tor_mutex_acquire(key_lock);
150 if (onionkey)
151 *key = crypto_pk_copy_full(onionkey);
152 else
>>> CID 1435130: Incorrect expression (COPY_PASTE_ERROR)
>>> "last" in "*last = NULL" looks like a copy-paste error.
153 *last = NULL;
154 if (lastonionkey)
155 *last = crypto_pk_copy_full(lastonionkey);
156 else
157 *last = NULL;
158 tor_mutex_release(key_lock);
```
Perhaps this new `*last = NULL;` should have been `*key = NULL`.Tor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25998FetchUselessDescriptors also stops Tor from going idle2021-07-22T16:20:51ZteorFetchUselessDescriptors also stops Tor from going idleTor: 0.3.3.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/26052man page still says CacheIPv4DNS is on by default2020-06-27T13:53:28ZRoger Dingledineman page still says CacheIPv4DNS is on by defaultin legacy/trac#24050 we made the SocksPort CacheIPv4DNS flag off by default, but we never fixed the man page to say it's off by default.in legacy/trac#24050 we made the SocksPort CacheIPv4DNS flag off by default, but we never fixed the man page to say it's off by default.Tor: 0.3.3.x-finalRoger DingledineRoger Dingledinehttps://gitlab.torproject.org/tpo/core/tor/-/issues/26170Core Tor releases typo2021-07-22T16:20:51ZTracCore Tor releases typoIt says 0.3.3 end of life is on `On or after Mar 22, 2018` but that is the day that it should be released.
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases?version=40
**Trac**:
**Username**: Dbryrtfb...It says 0.3.3 end of life is on `On or after Mar 22, 2018` but that is the day that it should be released.
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases?version=40
**Trac**:
**Username**: DbryrtfbcbhgfTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/26271client failed in onion_extend_cpath on Illumos/JoyentSmartOS2020-06-27T13:53:18ZTracclient failed in onion_extend_cpath on Illumos/JoyentSmartOSTor 0.3.3.6 (git-7dd0813e783ae16e) running on SunOS with Libevent 2.1.8-stable, OpenSSL 1.0.2o, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
on SunOS 5.11 joyent_20180524T002819Z i86pc i386 i86pc Solaris
and getting lots of these:
```
...Tor 0.3.3.6 (git-7dd0813e783ae16e) running on SunOS with Libevent 2.1.8-stable, OpenSSL 1.0.2o, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
on SunOS 5.11 joyent_20180524T002819Z i86pc i386 i86pc Solaris
and getting lots of these:
```
Jun 02 19:18:57.000 [warn] tor_bug_occurred_(): Bug: src/or/circuitbuild.c:2772: onion_extend_cpath: Non-fatal assertion info || client failed. (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: Non-fatal assertion info || client failed in onion_extend_cpath at src/or/circuitbuild.c:2772. Stack trace: (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'log_backtrace+0x47 [0x5cf7e7] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'tor_bug_occurred_+0xbb [0x5ea9db] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'circuit_establish_circuit+0x8bb [0x51954b] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'circuit_launch_by_extend_info+0x84 [0x52c7b4] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'circuit_build_needed_circs+0x2f6 [0x52ce76] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'second_elapsed_callback+0x3b8 [0x4916c8] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/lib/libevent-2.1.so.6.0.2'event_process_active_single_queue+0x372 [0xfffffc7fec883c32] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/lib/libevent-2.1.so.6.0.2'event_base_loop+0x5bf [0xfffffc7fec88471f] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'do_main_loop+0x214 [0x492184] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'tor_run_main+0x26d [0x49367d] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'tor_main+0x42 [0x48cbf2] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'main+0x1e [0x48caae] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'_start_crt+0x83 [0x48c913] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Bug: /opt/local/bin/tor'_start+0x18 [0x48c878] (on Tor 0.3.3.6 7dd0813e783ae16e)
Jun 02 19:18:57.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
```
I already checked legacy/trac#25692 but it seems the fix is already part of 3.3.6 7dd0813e783ae16e. "make test" ran with 0 errors, as well as the compile.
**Trac**:
**Username**: ruebezahlTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/26455use correct CARGO_HOME in test_rust.sh2020-06-27T13:53:08ZTaylor Yuuse correct CARGO_HOME in test_rust.sh`make check` currently doesn't seem to work with `--enable-rust` without `--enable-cargo-online-mode`.
It looks like cargo expects `CARGO_HOME` to point to the `.cargo` directory itself, not the directory containing it. Builds seem to ...`make check` currently doesn't seem to work with `--enable-rust` without `--enable-cargo-online-mode`.
It looks like cargo expects `CARGO_HOME` to point to the `.cargo` directory itself, not the directory containing it. Builds seem to work anyway because we `cd` to a directory where cargo can find a `.cargo` directory, even though we set `CARGO_HOME` incorrectly.
This might be making Jenkins builds fail too:
https://jenkins.torproject.org/job/tor-ci-linux-master-rust/ARCHITECTURE=i386,SUITE=sid/lastBuild/console
```
20:04:05 FAIL: src/test/test_rust.sh
20:04:05 ===========================
20:04:05
20:04:05 error: attempting to make an HTTP request, but --frozen was specified
20:04:05 error: attempting to make an HTTP request, but --frozen was specified
```
This incarnation of this bug seems to be in the fix for legacy/trac#26258, but similar problems seem to exist in releases as far back as 0.3.1.Tor: 0.3.3.x-finalTaylor YuTaylor Yuhttps://gitlab.torproject.org/tpo/core/tor/-/issues/26470WARN: Saying "HTTP/1.0 405 Method Not Allowed\r\n\r\n" WARN: connection_mark...2020-06-27T13:53:07ZTracWARN: Saying "HTTP/1.0 405 Method Not Allowed\r\n\r\n" WARN: connection_mark_unattached_ap_(): Bug: stream (marked at src/or/connection_edge.c:2551) sending two socks replies? (on Tor 0.3.3.5-rc 81d71f0d41adf0d8)WARN: Saying "HTTP/1.0 405 Method Not Allowed\r\n\r\n"
WARN: connection_mark_unattached_ap_(): Bug: stream (marked at src/or/connection_edge.c:2551) sending two socks replies? (on Tor 0.3.3.5-rc 81d71f0d41adf0d8)
**Trac**:
**Usernam...WARN: Saying "HTTP/1.0 405 Method Not Allowed\r\n\r\n"
WARN: connection_mark_unattached_ap_(): Bug: stream (marked at src/or/connection_edge.c:2551) sending two socks replies? (on Tor 0.3.3.5-rc 81d71f0d41adf0d8)
**Trac**:
**Username**: Tai683Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/26873FTBFS on GNU/Hurd: no PATH_MAX2020-06-27T13:52:49ZTracFTBFS on GNU/Hurd: no PATH_MAXPATH_MAX is undeclared on GNU/Hurd,
thus tor fails to compile since version 0.3.3
A build log of debian is available at [https://buildd.debian.org/status/fetch.php?pkg=tor&arch=hurd-i386&ver=0.3.4.5-rc-1&stamp=1531586376&raw=0]
The app...PATH_MAX is undeclared on GNU/Hurd,
thus tor fails to compile since version 0.3.3
A build log of debian is available at [https://buildd.debian.org/status/fetch.php?pkg=tor&arch=hurd-i386&ver=0.3.4.5-rc-1&stamp=1531586376&raw=0]
The appended patches replace `tor_snprintf` with `tor_asprintf`.
**Trac**:
**Username**: paulusASolTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/26913DataDirectoryGroupReadable enabled does not have effect2020-06-27T13:52:46ZTracDataDirectoryGroupReadable enabled does not have effectOn RedHat based systems the defaultrc includes DataDirectoryGroupReadable set to 1. But when starting up the daemon this is ignored and chmod of /var/lib/tor is set back to 0700.
This can be demostrated by the following test using vagra...On RedHat based systems the defaultrc includes DataDirectoryGroupReadable set to 1. But when starting up the daemon this is ignored and chmod of /var/lib/tor is set back to 0700.
This can be demostrated by the following test using vagrant:
```
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'centos/7'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'centos/7' is up to date...
==> default: Setting the name of the VM: tor-bug_default_1532356217662_9318
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2200
default: SSH username: vagrant
default: SSH auth method: private key
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: No guest additions were detected on the base box for this VM! Guest
default: additions are required for forwarded ports, shared folders, host only
default: networking, and more. If SSH fails on this machine, please install
default: the guest additions and repackage the box to continue.
default:
default: This is not an error message; everything may continue to work properly,
default: in which case you may ignore this message.
==> default: Rsyncing folder: /home/mh/fedora/tor-bug/ => /vagrant
==> default: Running provisioner: shell...
default: Running: inline script
default: Installing tor
default: Loaded plugins: fastestmirror
default: Determining fastest mirrors
default: * base: mirror.spreitzer.ch
default: * extras: mirror.spreitzer.ch
default: * updates: mirror.spreitzer.ch
default: Resolving Dependencies
default: --> Running transaction check
default: ---> Package tor.x86_64 0:0.3.3.9-1.el7 will be installed
default: --> Processing Dependency: torsocks for package: tor-0.3.3.9-1.el7.x86_64
default: --> Running transaction check
default: ---> Package torsocks.x86_64 0:2.2.0-1.el7.centos will be installed
default: --> Finished Dependency Resolution
default:
default: Dependencies Resolved
default:
default: ================================================================================
default: Package Arch Version Repository Size
default: ================================================================================
default: Installing:
default: tor x86_64 0.3.3.9-1.el7 maha-tor-latest 2.8 M
default: Installing for dependencies:
default: torsocks x86_64 2.2.0-1.el7.centos maha-tor-latest 65 k
default:
default: Transaction Summary
default: ================================================================================
default: Install 1 Package (+1 Dependent package)
default:
default: Total download size: 2.9 M
default: Installed size: 13 M
default: Downloading packages:
default: Public key for torsocks-2.2.0-1.el7.centos.x86_64.rpm is not installed
default: warning: /var/cache/yum/x86_64/7/maha-tor-latest/packages/torsocks-2.2.0-1.el7.centos.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID fe1432b1: NOKEY
default: --------------------------------------------------------------------------------
default: Total 1.4 MB/s | 2.9 MB 00:02
default: Retrieving key from https://copr-be.cloud.fedoraproject.org/results/maha/tor-latest/pubkey.gpg
default: Importing GPG key 0xFE1432B1:
default: Userid : "maha_tor-latest (None) <maha#tor-latest@copr.fedorahosted.org>"
default: Fingerprint: ddc6 1efd 56fa 03e5 e2d8 fa26 03f9 1145 fe14 32b1
default: From : https://copr-be.cloud.fedoraproject.org/results/maha/tor-latest/pubkey.gpg
default: Running transaction check
default: Running transaction test
default: Transaction test succeeded
default: Running transaction
default: Installing : torsocks-2.2.0-1.el7.centos.x86_64 1/2
default:
default: Installing : tor-0.3.3.9-1.el7.x86_64 2/2
default:
default: Verifying : torsocks-2.2.0-1.el7.centos.x86_64 1/2
default:
default: Verifying : tor-0.3.3.9-1.el7.x86_64 2/2
default:
default:
default: Installed:
default: tor.x86_64 0:0.3.3.9-1.el7
default:
default: Dependency Installed:
default: torsocks.x86_64 0:2.2.0-1.el7.centos
default:
default: Complete!
default:
default: ls -la /var/lib/tor
default: total 4
default: drwxr-x---. 2 toranon root 6 Jul 14 09:59 .
default: drwxr-xr-x. 29 root root 4096 Jul 23 14:31 ..
default:
default: Grep Data
default: /etc/tor/torrc:## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
default: /etc/tor/torrc:#DataDirectory /var/lib/tor
default: /usr/share/tor/defaults-torrc:DataDirectory /var/lib/tor
default: /usr/share/tor/defaults-torrc:DataDirectoryGroupReadable 1
default:
default: starting tor
default:
default: tor logs
default: -- Logs begin at Mon 2018-07-23 14:30:24 UTC, end at Mon 2018-07-23 14:31:08 UTC. --
default: Jul 23 14:31:07 localhost.localdomain systemd[1]: Starting Anonymizing overlay network for TCP...
default: Jul 23 14:31:08 localhost.localdomain tor[2563]: Jul 23 14:31:08.126 [notice] Tor 0.3.3.9 (git-45028085ea188baf) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2k-fips, Zlib 1.2.7, Liblzma N/A, and Libzstd N/A.
default: Jul 23 14:31:08 localhost.localdomain tor[2563]: Jul 23 14:31:08.127 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
default: Jul 23 14:31:08 localhost.localdomain tor[2563]: Jul 23 14:31:08.127 [notice] Read configuration file "/usr/share/tor/defaults-torrc".
default: Jul 23 14:31:08 localhost.localdomain tor[2563]: Jul 23 14:31:08.127 [notice] Read configuration file "/etc/tor/torrc".
default: Jul 23 14:31:08 localhost.localdomain tor[2563]: Jul 23 14:31:08.135 [warn] Fixing permissions on directory /var/lib/tor
default: Jul 23 14:31:08 localhost.localdomain tor[2563]: Configuration was valid
default: Jul 23 14:31:08 localhost.localdomain systemd[1]: Started Anonymizing overlay network for TCP.
default:
default: ls -la /var/lib/tor
default: total 4
default: drwx------. 2 toranon root 6 Jul 14 09:59 .
default: drwxr-xr-x. 29 root root 4096 Jul 23 14:31 ..
```
Using the following Vagrantfile:
```
$ cat Vagrantfile
script = <<-SCRIPT
curl -s -o /etc/yum.repos.d/maha-tor-latest-epel-7.repo https://copr.fedorainfracloud.org/coprs/maha/tor-latest/repo/epel-7/maha-tor-latest-epel-7.repo
echo Installing tor
yum install tor -y
echo 'Log debug stderr' >> /etc/tor/torrc
echo
echo ls -la /var/lib/tor
ls -la /var/lib/tor
echo
echo "Grep Data"
grep Data /etc/tor/torrc /usr/share/tor/defaults-torrc
echo
echo starting tor
systemctl start tor
echo
echo tor logs
journalctl -u tor -n 2000 --no-pager
echo
echo ls -la /var/lib/tor
ls -la /var/lib/tor
SCRIPT
Vagrant.configure("2") do |config|
config.vm.box = "centos/7"
config.vm.provision "shell", inline: script
end
```
**Trac**:
**Username**: mahaTor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/27410Bug: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed in ret...2020-06-27T13:52:21ZTracBug: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed in retry_all_socks_conn_waiting_for_desc at ../src/or/hs_client.c:268Sever running one v3 and one v2 hidden service and there is a bash script that test availability of those domains from time to time through curl. Bug warning is repeating.
v3 domain is not working at all but v2 is working fine.
```
Se...Sever running one v3 and one v2 hidden service and there is a bash script that test availability of those domains from time to time through curl. Bug warning is repeating.
v3 domain is not working at all but v2 is working fine.
```
Sep 02 06:26:05.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening new log file.
Sep 02 06:28:26.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 06:28:26.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 06:28:26.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 06:28:36.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:30:05.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 06:30:05.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 06:30:05.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 06:30:21.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:32:18.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:34:10.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:36:04.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 06:36:04.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 06:36:04.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 06:36:21.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:38:05.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 06:38:05.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 06:38:05.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 06:40:05.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 06:40:05.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 06:40:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 06:40:06.000 [warn] tor_bug_occurred_(): Bug: ../src/or/hs_client.c:268: retry_all_socks_conn_waiting_for_desc: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed. (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed in retry_all_socks_conn_waiting_for_desc at ../src/or/hs_client.c:268. Stack trace: (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/sbin/tor(log_backtrace+0x43) [0x55c6f6515873] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/sbin/tor(tor_bug_occurred_+0xb9) [0x55c6f6531109] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/sbin/tor(hs_client_dir_info_changed+0x106) [0x55c6f64f44f6] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/sbin/tor(+0x5208a) [0x55c6f63de08a] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x1f75c) [0x7f861da1175c] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7) [0x7f861da12227] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/sbin/tor(do_main_loop+0x2b4) [0x55c6f63e1624] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/sbin/tor(tor_run_main+0x1025) [0x55c6f63e3b05] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/sbin/tor(tor_main+0x3a) [0x55c6f63dc0ba] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/sbin/tor(main+0x19) [0x55c6f63dbe49] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f861c2191c1] (on Tor 0.3.3.9 )
Sep 02 06:40:06.000 [warn] Bug: /usr/sbin/tor(_start+0x2a) [0x55c6f63dbe9a] (on Tor 0.3.3.9 )
Sep 02 06:40:09.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 06:40:15.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:42:09.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:44:26.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 06:44:26.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 06:44:26.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 06:44:40.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:46:08.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:48:26.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 06:48:26.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 06:48:26.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 06:48:40.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:50:11.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:52:12.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:54:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 06:54:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 06:54:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 06:54:41.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:56:10.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 06:58:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 06:58:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 06:58:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 06:58:18.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:00:28.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:00:28.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:00:28.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:00:43.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:02:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:02:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:02:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:02:15.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:04:16.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:06:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:06:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:06:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:08:10.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 07:08:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:08:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:08:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:08:36.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:10:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:10:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:10:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:10:18.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:12:15.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:14:28.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:14:28.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:14:28.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:14:45.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:16:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:16:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:16:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:16:17.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:18:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:18:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:18:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:18:20.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:20:28.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:20:28.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:20:28.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:20:38.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:22:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:22:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:22:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:22:21.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:24:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:24:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:24:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:26:11.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 07:26:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:26:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:26:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:26:39.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:28:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:28:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:28:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:28:16.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:30:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:30:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:30:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:31:01.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:32:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:32:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:32:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:34:10.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 07:34:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:34:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:34:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:34:38.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:36:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:36:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:36:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:36:17.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:38:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:38:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:38:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:38:20.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:40:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:40:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:40:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:42:11.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 07:42:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:42:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:42:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:42:35.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:44:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:44:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:44:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:44:18.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:46:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:46:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:46:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:46:21.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:48:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:48:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:48:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:48:43.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:50:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:50:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:50:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:50:16.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:52:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:52:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:52:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:52:22.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:54:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:54:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:54:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:56:11.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 07:56:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:56:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:56:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:56:36.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 07:58:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 07:58:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 07:58:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 07:58:16.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:00:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:00:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:00:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:00:23.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:02:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:02:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:02:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:02:37.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 19 circuits open. I've sent 126.53 MB and received 77.24 MB.
Sep 02 08:02:37.000 [notice] Our hidden service received 2574 v2 and 4187 v3 INTRODUCE2 cells and attempted to launch 6776 rendezvous circuits.
Sep 02 08:04:11.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 08:04:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:04:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:04:28.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:04:38.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:06:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:06:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:06:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:06:17.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:08:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:08:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:08:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:08:21.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:10:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:10:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:10:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:12:12.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 08:12:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:12:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:12:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:12:38.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:14:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:14:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:14:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:14:18.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:16:14.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:18:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:18:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:18:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:18:42.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:20:11.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:22:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:22:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:22:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:22:22.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:24:28.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:24:28.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:24:28.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:24:43.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:26:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:26:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:26:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:26:18.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:28:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:28:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:28:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:28:28.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:30:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:30:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:30:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:32:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:32:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:32:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:32:06.000 [warn] tor_bug_occurred_(): Bug: ../src/or/hs_client.c:268: retry_all_socks_conn_waiting_for_desc: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed. (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed in retry_all_socks_conn_waiting_for_desc at ../src/or/hs_client.c:268. Stack trace: (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/sbin/tor(log_backtrace+0x43) [0x55c6f6515873] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/sbin/tor(tor_bug_occurred_+0xb9) [0x55c6f6531109] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/sbin/tor(hs_client_dir_info_changed+0x106) [0x55c6f64f44f6] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/sbin/tor(+0x5208a) [0x55c6f63de08a] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x1f75c) [0x7f861da1175c] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7) [0x7f861da12227] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/sbin/tor(do_main_loop+0x2b4) [0x55c6f63e1624] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/sbin/tor(tor_run_main+0x1025) [0x55c6f63e3b05] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/sbin/tor(tor_main+0x3a) [0x55c6f63dc0ba] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/sbin/tor(main+0x19) [0x55c6f63dbe49] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f861c2191c1] (on Tor 0.3.3.9 )
Sep 02 08:32:06.000 [warn] Bug: /usr/sbin/tor(_start+0x2a) [0x55c6f63dbe9a] (on Tor 0.3.3.9 )
Sep 02 08:32:12.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 08:32:20.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:34:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:34:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:34:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:36:11.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 08:36:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:36:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:36:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:36:42.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:38:10.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:40:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:40:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:40:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:40:23.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:42:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:42:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:42:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:42:39.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:44:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:44:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:44:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:44:18.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:46:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:46:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:46:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:47:02.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:48:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:48:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:48:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:48:50.000 [warn] tor_bug_occurred_(): Bug: ../src/or/hs_client.c:268: retry_all_socks_conn_waiting_for_desc: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed. (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed in retry_all_socks_conn_waiting_for_desc at ../src/or/hs_client.c:268. Stack trace: (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(log_backtrace+0x43) [0x55c6f6515873] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(tor_bug_occurred_+0xb9) [0x55c6f6531109] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(hs_client_dir_info_changed+0x106) [0x55c6f64f44f6] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(microdescs_add_list_to_cache+0x185) [0x55c6f63e5f35] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(microdescs_add_to_cache+0x292) [0x55c6f63e6402] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(connection_dir_reached_eof+0x19db) [0x55c6f64c293b] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(+0x10d249) [0x55c6f6499249] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(+0x5456e) [0x55c6f63e056e] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x1f6aa) [0x7f861da116aa] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7) [0x7f861da12227] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(do_main_loop+0x2b4) [0x55c6f63e1624] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(tor_run_main+0x1025) [0x55c6f63e3b05] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(tor_main+0x3a) [0x55c6f63dc0ba] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(main+0x19) [0x55c6f63dbe49] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f861c2191c1] (on Tor 0.3.3.9 )
Sep 02 08:48:50.000 [warn] Bug: /usr/sbin/tor(_start+0x2a) [0x55c6f63dbe9a] (on Tor 0.3.3.9 )
Sep 02 08:50:11.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 08:50:28.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:50:28.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:50:28.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:50:40.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:52:09.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:54:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:54:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:54:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:54:22.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:56:28.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:56:28.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:56:28.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:56:42.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 08:58:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 08:58:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 08:58:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 08:58:18.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 09:00:07.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 09:00:07.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 09:00:07.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 09:00:23.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 09:02:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 09:02:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 09:02:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 09:04:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 09:04:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 09:04:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 09:04:06.000 [warn] tor_bug_occurred_(): Bug: ../src/or/hs_client.c:268: retry_all_socks_conn_waiting_for_desc: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed. (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: Non-fatal assertion !(status == HS_CLIENT_FETCH_HAVE_DESC) failed in retry_all_socks_conn_waiting_for_desc at ../src/or/hs_client.c:268. Stack trace: (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/sbin/tor(log_backtrace+0x43) [0x55c6f6515873] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/sbin/tor(tor_bug_occurred_+0xb9) [0x55c6f6531109] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/sbin/tor(hs_client_dir_info_changed+0x106) [0x55c6f64f44f6] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/sbin/tor(+0x5208a) [0x55c6f63de08a] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x1f75c) [0x7f861da1175c] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7) [0x7f861da12227] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/sbin/tor(do_main_loop+0x2b4) [0x55c6f63e1624] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/sbin/tor(tor_run_main+0x1025) [0x55c6f63e3b05] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/sbin/tor(tor_main+0x3a) [0x55c6f63dc0ba] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/sbin/tor(main+0x19) [0x55c6f63dbe49] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f861c2191c1] (on Tor 0.3.3.9 )
Sep 02 09:04:06.000 [warn] Bug: /usr/sbin/tor(_start+0x2a) [0x55c6f63dbe9a] (on Tor 0.3.3.9 )
Sep 02 09:04:11.000 [notice] Tried for 120 seconds to get a connection to v3onion....................onion:80. Giving up. (waiting for rendezvous desc)
Sep 02 09:04:17.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 09:06:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 09:06:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 09:06:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 09:06:40.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 09:08:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 09:08:06.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 09:08:06.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 09:08:17.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 09:10:27.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Sep 02 09:10:27.000 [notice] Read configuration file "/etc/tor/tor1.cfg".
Sep 02 09:10:27.000 [notice] Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
Sep 02 09:10:42.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
Sep 02 09:12:10.000 [notice] Closed 1 streams for service v3onion....................onion for reason resolve failed. Fetch status: No more HSDir available to query.
```
**Trac**:
**Username**: cstestTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/27550hs-v3: Don't warn so loudly when tor is unable to decode a descriptor2020-06-27T13:52:15ZDavid Gouletdgoulet@torproject.orghs-v3: Don't warn so loudly when tor is unable to decode a descriptorWith legacy/trac#20700, we introduce client authorization making tor client without it trying to access a .onion with it to be unable to decode the descriptor. This leads to big warnings:
```
Sep 07 13:55:44.156 [info] handle_response_f...With legacy/trac#20700, we introduce client authorization making tor client without it trying to access a .onion with it to be unable to decode the descriptor. This leads to big warnings:
```
Sep 07 13:55:44.156 [info] handle_response_fetch_hsdesc_v3(): Received v3 hsdesc (body size 14111, status 200 ("OK"))
Sep 07 13:55:44.157 [warn] Encrypted service descriptor MAC check failed
Sep 07 13:55:44.157 [warn] Decrypting encrypted desc failed.
Sep 07 13:55:44.157 [warn] Service descriptor decryption failed.
Sep 07 13:55:44.157 [warn] Could not parse received descriptor as client.
...
```
We should definitely not print warning if decoding fails but maybe a "unable to use descriptor" instead and the rest at info level.
Second, there is the retry behavior. Two cases:
1) Tor is configured with client authorization for A.onion:
If we get the descriptor and unable to decode A.onion while we know we have a client authorization configured, I think we should make Tor stop and just tell the user that it didn't worked.
2) Tor doesn't have client authorization for A.onion
In that case, if the decoding fails, we should *probably* make Tor stop trying on all HSDir and instead go at notice level saying "Unable to access A.onion. Maybe you need authorization?" kind of message.
Failing to decode a descriptor now is imo highly unlikely so we could assume that in this case, chances are that you'll get a better descriptor at the next HSDir are thin!Tor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/27708Heap use-after-free on git master dbb0abc9f1a174efdb65d581f5dbe46dbad2ebb52020-06-27T13:52:10ZDavid Gouletdgoulet@torproject.orgHeap use-after-free on git master dbb0abc9f1a174efdb65d581f5dbe46dbad2ebb5I found this issue by setting an invalid `HiddenServiceDir` containing 2 level of directories for tor to create for which it can't do it leading to `options_act()` returning -1.
```
HiddenServiceDir /tmp/level1/level2
```
Here is the A...I found this issue by setting an invalid `HiddenServiceDir` containing 2 level of directories for tor to create for which it can't do it leading to `options_act()` returning -1.
```
HiddenServiceDir /tmp/level1/level2
```
Here is the ASAN output:
```
==10573==ERROR: AddressSanitizer: heap-use-after-free on address 0x61d000002948 at pc 0x55741b1f88d1 bp 0x7ffe0d70bc10 sp 0x7ffe0d70bc00
READ of size 8 at 0x61d000002948 thread T0
#0 0x55741b1f88d0 in or_options_free_ src/app/config/config.c:1005
#1 0x55741b2009af in config_free_all src/app/config/config.c:1034
#2 0x55741ad38034 in tor_free_all src/core/mainloop/main.c:3693
#3 0x55741ad38b6e in tor_run_main src/core/mainloop/main.c:4277
#4 0x55741ad2286b in tor_main src/feature/api/tor_api.c:164
#5 0x55741ad1d7cb in main src/app/main/tor_main.c:32
#6 0x7fc43440109a in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2409a)
#7 0x55741ad219e9 in _start (/home/dgoulet/Documents/git/tor/src/app/tor+0x9119e9)
0x61d000002948 is located 200 bytes inside of 2264-byte region [0x61d000002880,0x61d000003158)
freed by thread T0 here:
#0 0x7fc43614cb70 in free (/usr/lib/x86_64-linux-gnu/libasan.so.5+0xedb70)
#1 0x55741b23e3e7 in config_free_ src/app/config/confparse.c:871
#2 0x55741b1f8548 in or_options_free_ src/app/config/config.c:1026
#3 0x55741b22bbcc in options_init_from_string src/app/config/config.c:5487
#4 0x55741b22d540 in options_init_from_torrc src/app/config/config.c:5233
#5 0x55741ad37098 in tor_init src/core/mainloop/main.c:3540
#6 0x55741ad389c0 in tor_run_main src/core/mainloop/main.c:4275
#7 0x55741ad2286b in tor_main src/feature/api/tor_api.c:164
#8 0x55741ad1d7cb in main src/app/main/tor_main.c:32
#9 0x7fc43440109a in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2409a)
previously allocated by thread T0 here:
#0 0x7fc43614cf30 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.5+0xedf30)
#1 0x55741b3b378a in tor_malloc_ src/lib/malloc/malloc.c:45
#2 0x55741b3b3821 in tor_malloc_zero_ src/lib/malloc/malloc.c:71
#3 0x55741b22b294 in options_init_from_string src/app/config/config.c:5336
#4 0x55741b22d540 in options_init_from_torrc src/app/config/config.c:5233
#5 0x55741ad37098 in tor_init src/core/mainloop/main.c:3540
#6 0x55741ad389c0 in tor_run_main src/core/mainloop/main.c:4275
#7 0x55741ad2286b in tor_main src/feature/api/tor_api.c:164
#8 0x55741ad1d7cb in main src/app/main/tor_main.c:32
#9 0x7fc43440109a in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2409a)
SUMMARY: AddressSanitizer: heap-use-after-free src/app/config/config.c:1005 in or_options_free_
```
Logs shows:
```
Sep 14 10:20:00.000 [warn] Error creating directory /tmp/level1/level2: No such file or directory
Sep 14 10:20:00.000 [warn] Error loading rendezvous service keys
Sep 14 10:20:00.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.3.5.0-alpha-dev dbb0abc9f1a174ef)
```
What I can tell is that if `options_act()` returns -1, we'll inevitably end up in this situation so this isn't HS only. Kind of difficult to follow the stacktrace as the use-after-free points to a free(). I know that the pointer there is NULL at that time...Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/28419libtorrunner: memory leak in tor_runner error path2020-06-27T13:51:40ZTraclibtorrunner: memory leak in tor_runner error pathIn case execv fails, libtorrunner's child() leaks string-memory.
**Trac**:
**Username**: mergeIn case execv fails, libtorrunner's child() leaks string-memory.
**Trac**:
**Username**: mergeTor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/28619hs-v3: Do not close RP circuits when deleting an ephemeral service2021-09-30T13:25:26ZDavid Gouletdgoulet@torproject.orghs-v3: Do not close RP circuits when deleting an ephemeral serviceRelated to the OnionShare issue with v3:
https://lists.torproject.org/pipermail/tor-dev/2018-November/013556.html
The v2 subsystem doesn't close the RP circuits so our best move here is to do the same. The fix is trivial.Related to the OnionShare issue with v3:
https://lists.torproject.org/pipermail/tor-dev/2018-November/013556.html
The v2 subsystem doesn't close the RP circuits so our best move here is to do the same. The fix is trivial.Tor: 0.3.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/28973Disable TLS1.3 when openssl bug 7712 is present2022-03-07T00:00:01ZNick MathewsonDisable TLS1.3 when openssl bug 7712 is presentSee legacy/trac#28616 for the impact of the bug in tor; see https://github.com/openssl/openssl/issues/7712 for the openssl issue.See legacy/trac#28616 for the impact of the bug in tor; see https://github.com/openssl/openssl/issues/7712 for the openssl issue.Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/29244Travis permissions error: failed to write Cargo.lock2020-06-27T13:51:00ZteorTravis permissions error: failed to write Cargo.lockLet's monitor this error, and see if it happens again.
From https://trac.torproject.org/projects/tor/ticket/23576?replyto=24#comment:24
> {{{
> error: failed to write /home/travis/build/torproject/tor/tor-0.4.0.1-alpha-dev/src/rust/Car...Let's monitor this error, and see if it happens again.
From https://trac.torproject.org/projects/tor/ticket/23576?replyto=24#comment:24
> {{{
> error: failed to write /home/travis/build/torproject/tor/tor-0.4.0.1-alpha-dev/src/rust/Cargo.lock
>
> Caused by:
> failed to open: /home/travis/build/torproject/tor/tor-0.4.0.1-alpha-dev/src/rust/Cargo.lock
>
> Caused by:
> Permission denied (os error 13)
> }}}
> https://travis-ci.org/torproject/tor/jobs/486721901#L3634Tor: 0.3.3.x-finalNick MathewsonNick Mathewson