Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:10:11Zhttps://gitlab.torproject.org/legacy/trac/-/issues/34199torsocks irssi weird bug2020-06-13T16:10:11ZTractorsocks irssi weird bugDepending on the arguments to torsocks the output varies even though it shouldn't
case-1: torsocks irssi
`/connect oftc` gives following error
Irssi: Unable to connect server irc.oftc.net port 6697 [Interrupted system call]
case 2: tor...Depending on the arguments to torsocks the output varies even though it shouldn't
case-1: torsocks irssi
`/connect oftc` gives following error
Irssi: Unable to connect server irc.oftc.net port 6697 [Interrupted system call]
case 2: torsocks -d irssi
`/connect oftc` works as expected
I don't think there should be difference in output just because logging is enabled. This just might be the "torsocks uncertainty principle". I think we are onto something. Below I've attached the log dumped on the terminal.
1589343629 DEBUG torsocks[22051]: Logging subsytem initialized. Level 5, file (null), time 1 (in init_logging() at torsocks.c:303)
1589343629 DEBUG torsocks[22051]: Config file not provided by TORSOCKS_CONF_FILE. Using default /etc/torsocks.conf (in config_file_read() at config-file.c:543)
1589343629 DEBUG torsocks[22051]: Config file setting tor address to 127.0.0.1 (in conf_file_set_tor_address() at config-file.c:298)
1589343629 DEBUG torsocks[22051]: Config file setting tor port to 9050 (in conf_file_set_tor_port() at config-file.c:254)
1589343629 DEBUG torsocks[22051]: [config] Onion address range set to 127.42.42.0/24 (in set_onion_info() at config-file.c:108)
1589343629 DEBUG torsocks[22051]: Config file /etc/torsocks.conf opened and parsed. (in config_file_read() at config-file.c:572)
1589343629 DEBUG torsocks[22051]: [fclose] Close caught for fd 3 (in tsocks_fclose() at fclose.c:45)
1589343629 DEBUG torsocks[22051]: [onion] Pool init with subnet 127.42.42.0 and mask 24 (in onion_pool_init() at onion.c:104)
1589343629 DEBUG torsocks[22051]: [onion] Pool initialized with base 0, max_pos 255 and size 8 (in onion_pool_init() at onion.c:132)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
**Trac**:
**Username**: crabhttps://gitlab.torproject.org/legacy/trac/-/issues/34041Discord sent me an email listing my real ip as login location2020-06-13T18:36:28ZTracDiscord sent me an email listing my real ip as login locationI logged in to discord using tor and then got an email from discord saying someone had logged in to discord and giving my REAL IP address.
**Trac**:
**Username**: Camillia124I logged in to discord using tor and then got an email from discord saying someone had logged in to discord and giving my REAL IP address.
**Trac**:
**Username**: Camillia124https://gitlab.torproject.org/legacy/trac/-/issues/30775Crash in close_or_reextend_intro_circ() (not released)2020-06-13T15:42:11ZGeorge KadianakisCrash in close_or_reextend_intro_circ() (not released)There is a UAF in:
```
if (!TO_CIRCUIT(intro_circ)->marked_for_close) {
circuit_change_purpose(TO_CIRCUIT(intro_circ),
CIRCUIT_PURPOSE_C_INTRODUCE_ACKED);
circuit_mark_for_close(TO_CIRCUIT(intro_cir...There is a UAF in:
```
if (!TO_CIRCUIT(intro_circ)->marked_for_close) {
circuit_change_purpose(TO_CIRCUIT(intro_circ),
CIRCUIT_PURPOSE_C_INTRODUCE_ACKED);
circuit_mark_for_close(TO_CIRCUIT(intro_circ), END_CIRC_REASON_FINISHED);
}
/* Close the related rendezvous circuit. */
rend_circ = hs_circuitmap_get_rend_circ_client_side(
intro_circ->hs_ident->rendezvous_cookie);
```
exact same bug class as #30773.Tor: 0.4.1.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/30773New bug class: Accessing rend_data/hs_ident after marking for close a circuit2020-06-13T15:42:10ZGeorge KadianakisNew bug class: Accessing rend_data/hs_ident after marking for close a circuitSee #30771 for an example of this issue:
```
circuit_mark_for_close(TO_CIRCUIT(circ), END_CIRC_REASON_FINISHED);
/* close any other intros launched in parallel */
rend_client_close_other_intros(rend_data_get_pk_digest(ci...See #30771 for an example of this issue:
```
circuit_mark_for_close(TO_CIRCUIT(circ), END_CIRC_REASON_FINISHED);
/* close any other intros launched in parallel */
rend_client_close_other_intros(rend_data_get_pk_digest(circ->rend_data,
NULL));
```
It seems to be caused by a bad interaction between #29034 and #28780, plus some naughty v2 code. The v2 code marks the circuit as closed and then tries to access rend_data out of it, but because of #28780 the mark for close repurposes the circuit to a padding circuit instead, and then because #29034 we also clean its rend_data. This causes the crash.
We should make sure that this pattern is impossible in other parts of the code, so that we don't assert out again, or even worse access freed memory.Tor: 0.4.1.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/30711Torbutton: Unexpected error on new identity.2020-06-16T01:04:36ZTracTorbutton: Unexpected error on new identity.Hey guys,
Have been experiencing this after latest update. Everything worked fine before . Also i cannot open menu tool bar at all. Seems like an empty click when clicking it.
Everything is installed correctly. As before.
Here is the...Hey guys,
Have been experiencing this after latest update. Everything worked fine before . Also i cannot open menu tool bar at all. Seems like an empty click when clicking it.
Everything is installed correctly. As before.
Here is the error i get for new identity.
Torbutton: Unexpected error on new identity: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: chrome://torbutton/content/torbutton.js :: torbutton_do_new_identity :: line 1126" data: no]
**Trac**:
**Username**: denucaahttps://gitlab.torproject.org/legacy/trac/-/issues/29236After updating tor to 8.0.5, socks5 started to not work2020-06-13T16:10:05ZTracAfter updating tor to 8.0.5, socks5 started to not workI usually use socks5 in Adium messenger, but when i updated tor to new version Adium start to give the error - Error: Connection failed
In tor logs i found those -
1/30/19, 20:16:31.821 [WARN] Fetching socks handshake failed. Closing.
...I usually use socks5 in Adium messenger, but when i updated tor to new version Adium start to give the error - Error: Connection failed
In tor logs i found those -
1/30/19, 20:16:31.821 [WARN] Fetching socks handshake failed. Closing.
1/30/19, 20:16:31.821 [WARN] socks5: parsing failed - invalid user/pass authentication message.
1/30/19, 20:16:31.821 [WARN] Fetching socks handshake failed. Closing.
1/30/19, 20:16:37.680 [WARN] socks5: parsing failed - invalid user/pass authentication message.
1/30/19, 20:16:37.680 [WARN] Fetching socks handshake failed. Closing.
1/30/19, 20:16:37.680 [WARN] socks5: parsing failed - invalid user/pass authentication message.
I never had this before, all have worked perfectly. Immediately after the update, everything stopped working. I tried all, i installed tor/messenger and updated os, but nothing helped.
Help!
**Trac**:
**Username**: bugiguimanDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/28772DNS resolver at DNSPort stops working after some time, while tor is working. ...2020-06-13T15:35:20ZTracDNS resolver at DNSPort stops working after some time, while tor is working. Only restart helps.Hello. I am tor user more than 6 years. And always this problem existed. Now I am totally tired and decided to fill a bug. I am using always latest versions, now at 0.3.5.5 and on android the same, latest 0.3.* version.
I use DNSPort o...Hello. I am tor user more than 6 years. And always this problem existed. Now I am totally tired and decided to fill a bug. I am using always latest versions, now at 0.3.5.5 and on android the same, latest 0.3.* version.
I use DNSPort option and route all my DNS traffic to it. After tor is connected, it is working well, but after some time (2-5-10 hours), it stop to work and return no IP address to any DNS request, while the tor itself continue working, log don't show anything relevant. DNS requests resolve only internally through socks port.
This happens many years to me, and only restarting tor helps to get my DNS back.
I even tried to open multiple DNSresolvers, like
DNSPort 127.0.0.2:53
DNSPort 127.0.0.3:53
DNSPort 127.0.0.4:53
and put them all to /etc/resolv.conf, and it helped to keep it running more long, but anyway after some time they all stops resolving.
On android I have the same issue. I rerouted all DNS traffic to it, and after some hours only restarting to service works. I even thought to write some script, if domain fails to resolve, restart to service...
Please help! DNSPort resolver must recreate it's circuits if they fails. and don't wait for hard reset.
Thank you!
**Trac**:
**Username**: toruser787Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/26932Soft assert in HS3 with vanguards ([warn] Invalid signature for service descr...2020-06-13T15:45:22ZGeorge KadianakisSoft assert in HS3 with vanguards ([warn] Invalid signature for service descriptor signing key: expired)I recently got the following soft assert on my HSv3 with latest master:
```
Jul 22 09:05:41.000 [warn] Invalid signature for service descriptor signing key: expired
Jul 22 09:05:41.000 [warn] tor_bug_occurred_(): Bug: src/feature/hs/hs_...I recently got the following soft assert on my HSv3 with latest master:
```
Jul 22 09:05:41.000 [warn] Invalid signature for service descriptor signing key: expired
Jul 22 09:05:41.000 [warn] tor_bug_occurred_(): Bug: src/feature/hs/hs_descriptor.c:2367: hs_desc_encode_descriptor: Non-fatal assertion !(ret < 0) failed. (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: Non-fatal assertion !(ret < 0) failed in hs_desc_encode_descriptor at src/feature/hs/hs_descriptor.c:2367. Stack trace: (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(log_backtrace_impl+0x47) [0x7f9979f5b437] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(tor_bug_occurred_+0xbe) [0x7f9979f56d0e] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(hs_desc_encode_descriptor+0xb2) [0x7f9979e5dba2] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(hs_service_run_scheduled_events+0x1a75) [0x7f9979e64ac5] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(+0x51fb1) [0x7f9979dc4fb1] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(+0x593b1) [0x7f9979dcc3b1] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x7fc) [0x7f99793f63dc] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(do_main_loop+0x203) [0x7f9979dc8e13] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(tor_run_main+0x2a5) [0x7f9979dca325] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(tor_main+0x3a) [0x7f9979dc364a] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(main+0x19) [0x7f9979dc33b9] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f99785e92b1] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
Jul 22 09:05:41.000 [warn] Bug: ./tor/src/app/tor(_start+0x2a) [0x7f9979dc340a] (on Tor 0.3.5.0-alpha-dev e2b744ce38edb890)
```
I'm suspecting it might have to do with the #25552 fix because the code changed there is relevant to this bug, altho I don't see how it can cause this bug.
Based on the logs, it seems like my HSv3 kept that descriptor around for about 56 hours when the descriptor signing key cert lifetime is 54 hours (see `HS_DESC_CERT_LIFETIME`).Tor: 0.3.5.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/20103Crash on OpenBSD: tor invoked from Tor Browser 6.0.42020-06-13T15:01:21ZattilaCrash on OpenBSD: tor invoked from Tor Browser 6.0.4While testing an update to the (proposed) TBB port for OpenBSD both I and my partner in torbsd.crime were able to get the instance of tor started by TBB to dump core, but not reliably.
We're using tor 0.2.8.7 under OpenBSD-current (Sept...While testing an update to the (proposed) TBB port for OpenBSD both I and my partner in torbsd.crime were able to get the instance of tor started by TBB to dump core, but not reliably.
We're using tor 0.2.8.7 under OpenBSD-current (Sept 5 snapshot). I've built myself a package for amd64 from the OpenBSD port with debugging symbols, so I can see what's going on. Under -current you do:
```
$ cd /usr/ports/net/tor
$ env DEBUG="-ggdb -O0" INSTALL_STRIP= make repackage
```
and install the resulting `/usr/ports/packages/amd64/all/tor-0.2.8.7.tgz` package.
Other than that I made no changes to tor itself. The core dump happened both with the standard package (no debug syms) and my package with debug syms.
We die in nodelist.c:836 at the call to the SL_ADD_NEW_IPV6_AP() macro because `node->rs` appears to be an invalid pointer (`node->ri` is fine):
```
(gdb) where
#0 0x000013438bc334a2 in tor_addr_family (a=0x1345c7c3ff58) at address.h:155
#1 0x000013438bc3501c in tor_addr_is_null (addr=0x1345c7c3ff58)
at src/common/address.c:871
#2 0x000013438bc3526e in tor_addr_is_valid (addr=0x1345c7c3ff58,
for_listening=0) at src/common/address.c:932
#3 0x000013438bb1575f in node_get_all_orports (node=0x1345c21f6000)
at src/or/nodelist.c:836
#4 0x000013438bc29a20 in node_is_a_configured_bridge (node=0x1345c21f6000)
at src/or/entrynodes.c:1871
#5 0x000013438bc2b74a in any_bridge_supports_microdescriptors ()
at src/or/entrynodes.c:2486
#6 0x000013438bb0d2ef in we_use_microdescriptors_for_circuits (
options=0x134681d2f7a0) at src/or/microdesc.c:924
#7 0x000013438bb0d3e9 in usable_consensus_flavor () at src/or/microdesc.c:961
#8 0x000013438bb102e8 in networkstatus_consensus_is_bootstrapping (
now=1473280922) at src/or/networkstatus.c:1249
#9 0x000013438bc019b2 in find_dl_schedule (dls=0x13438c0185d0,
options=0x134681d2f7a0) at src/or/directory.c:3732
#10 0x000013438bc020d0 in download_status_reset (dls=0x13438c0185d0)
at src/or/directory.c:3950
#11 0x000013438bb114bc in networkstatus_set_current_consensus (
consensus=0x13468873f000 "network-status-version 3 microdesc\nvote-status consensus\nconsensus-method 20\nvalid-after 2016-09-07 20:00:00\nfresh-until 2016-09-07 21:00:00\nvalid-until 2016-09-07 23:00:00\nvoting-delay 300 300\nclient"..., flavor=0x1345e6fb8470 "microdesc", flags=0) at src/or/networkstatus.c:1679
#12 0x000013438bbfba02 in connection_dir_client_reached_eof (
conn=0x1346506c2500) at src/or/directory.c:2009
#13 0x000013438bbfda9a in connection_dir_reached_eof (conn=0x1346506c2500)
at src/or/directory.c:2471
#14 0x000013438bbd32e9 in connection_reached_eof (conn=0x1346506c2500)
at src/or/connection.c:4841
#15 0x000013438bbd058d in connection_handle_read_impl (conn=0x1346506c2500)
at src/or/connection.c:3526
#16 0x000013438bbd05d9 in connection_handle_read (conn=0x1346506c2500)
at src/or/connection.c:3541
#17 0x000013438bb031ec in conn_read_callback (fd=-1, event=2,
_conn=0x1346506c2500) at src/or/main.c:803
#18 0x0000134603284cbe in event_base_loop ()
from /usr/local/lib/libevent_core.so.1.1
#19 0x000013438bb06397 in run_main_loop_once () at src/or/main.c:2543
#20 0x000013438bb064da in run_main_loop_until_done () at src/or/main.c:2589
#21 0x000013438bb062b7 in do_main_loop () at src/or/main.c:2515
#22 0x000013438bb0a0e5 in tor_main (argc=16, argv=0x7f7ffffc01b8)
at src/or/main.c:3646
#23 0x000013438bb01f3f in main (argc=16, argv=0x7f7ffffc01b8)
at src/or/tor_main.c:30
(gdb) up
#1 0x000013438bc3501c in tor_addr_is_null (addr=0x1345c7c3ff58)
at src/common/address.c:871
871 switch (tor_addr_family(addr)) {
(gdb) up
#2 0x000013438bc3526e in tor_addr_is_valid (addr=0x1345c7c3ff58,
for_listening=0) at src/common/address.c:932
932 return !tor_addr_is_null(addr);
(gdb) up
#3 0x000013438bb1575f in node_get_all_orports (node=0x1345c21f6000)
at src/or/nodelist.c:836
836 SL_ADD_NEW_IPV6_AP(node->rs, ipv6_orport, sl, valid);
(gdb) print node->rs
$16 = (routerstatus_t *) 0x1345c7c3ff00
(gdb) print *node->rs
Cannot access memory at address 0x1345c7c3ff00
(gdb) print node->ri
$18 = (routerinfo_t *) 0x134596a7aa00
(gdb) print *node->ri
$19 = {cache_info = {signed_descriptor_body = 0x0, annotations_len = 73,
signed_descriptor_len = 2223,
signed_descriptor_digest = "§À[º`?ø/\023\005ò\223»Q\004\223j\204íÌ",
identity_digest = "\232h¸Z\0021\217N~\207ò\202\2009ûÕ×[\001B",
published_on = 1473266407,
extra_info_digest = "¡ce8ÃÆ]ü\204^mà *º\220\021\205¹ä",
extra_info_digest256 = "¥m\n\231\234\003\230ý\021|ã\035hÊ\025b2 0ÐÐk/\217à\233ò\235\005ÇÇî", signing_key_cert = 0x1346133eb100, ei_dl_status = {
next_attempt_at = 1473280814, n_download_failures = 0 '\0',
n_download_attempts = 0 '\0', schedule = DL_SCHED_GENERIC,
want_authority = DL_WANT_ANY_DIRSERVER,
increment_on = DL_SCHED_INCREMENT_FAILURE},
saved_location = SAVED_IN_CACHE, saved_offset = 0, routerlist_index = 0,
last_listed_as_valid_until = 0, do_not_cache = 0, is_extrainfo = 0,
extrainfo_is_bogus = 0, send_unencrypted = 0},
nickname = 0x13459bfe5820 "NYCBUG0", addr = 1114571284, or_port = 9001,
dir_port = 9030, ipv6_addr = {family = 0 '\0', addr = {dummy_ = 0,
in_addr = {s_addr = 0}, in6_addr = {__u6_addr = {
__u6_addr8 = '\0' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0,
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}}}, ipv6_orport = 0,
onion_pkey = 0x13465a3d8d20, identity_pkey = 0x134674ecf280,
onion_curve25519_pkey = 0x134643b73920, cert_expiration_time = 1473872400,
platform = 0x134643b739a0 "Tor 0.2.9.2-alpha on FreeBSD",
bandwidthrate = 10240000, bandwidthburst = 15360000,
bandwidthcapacity = 7341056, exit_policy = 0x134674ecfd40,
ipv6_exit_policy = 0x0, uptime = 3, declared_family = 0x134674ecffb0,
contact_info = 0x134643b79780 "Admin <mirror-admin AT nycbug DOT org>",
is_hibernating = 0, caches_extra_info = 0, allow_single_hop_exits = 0,
wants_to_be_hs_dir = 1, policy_is_reject_star = 1,
needs_retest_if_added = 0, supports_tunnelled_dir_requests = 1,
omit_from_vote = 0, purpose = 2 '\002'}
(gdb) print node
$20 = (const node_t *) 0x1345c21f6000
(gdb) print *node
$21 = {ht_ent = {hte_next = 0x0, hte_hash = 1201906925}, nodelist_idx = 0,
identity = "\232hZ\0021\217N~\207202\2009[\001B", md = 0x13463eac4500,
ri = 0x134596a7aa00, rs = 0x1345c7c3ff00, is_running = 1, is_valid = 1,
is_fast = 1, is_stable = 1, is_possible_guard = 1, is_exit = 0,
is_bad_exit = 0, is_hs_dir = 0, name_lookup_warned = 0, rejects_all = 0,
using_as_guard = 0, ipv6_preferred = 0, country = 5, last_reachable = 0,
last_reachable6 = 0}
```
I wish I had more details to offer so far that's all I have.
I've changed my [malloc.conf(5)](http://man.openbsd.org/OpenBSD-current/man5/malloc.conf.5) settings since the crash to see if any of the new debug features in
OpenBSD's [malloc(3)](http://man.openbsd.org/OpenBSD-current/man3/malloc.3) implementation will catch anything (maybe use after free?):
```
attila@rotfl:~ 18:$ ls -l /etc/malloc.conf
lrwxr-xr-x 1 root wheel 5 Sep 7 16:55 /etc/malloc.conf -> CFGJU
```
I've restarted and am hoping to cause this to occur again. Will update this ticket if I learn anything else. Bug me on IRC if you want (I'm attila on #tor-dev).Tor: 0.2.8.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/19926BUG warning in connection_ap_attach_pending: waiting for rendezvous desc :*2020-06-13T15:36:10ZcypherpunksBUG warning in connection_ap_attach_pending: waiting for rendezvous desc :*connection_ap_attach_pending: Bug: 0x613000b8d680 is no longer in circuit_wait. Its current state is waiting for rendezvous desc. Why is it on pending_entry_connections? (on Tor 0.2.9.1-alpha f6c7e131a1ceb178)
Yeah, why?connection_ap_attach_pending: Bug: 0x613000b8d680 is no longer in circuit_wait. Its current state is waiting for rendezvous desc. Why is it on pending_entry_connections? (on Tor 0.2.9.1-alpha f6c7e131a1ceb178)
Yeah, why?Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/19466Memory leak while parsing a crafted torrc2020-06-13T14:58:50ZTracMemory leak while parsing a crafted torrcThere is a memory leak while tor parses a crafted config.
~ # tor --verify-config -f $CRAFTED_TORRC
Jun 20 15:59:36.509 [notice] Tor v0.2.7.6 running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2h and Zlib 1.2.8.
Jun 20 15:59:36.5...There is a memory leak while tor parses a crafted config.
~ # tor --verify-config -f $CRAFTED_TORRC
Jun 20 15:59:36.509 [notice] Tor v0.2.7.6 running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2h and Zlib 1.2.8.
Jun 20 15:59:36.531 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 20 15:59:36.531 [notice] Read configuration file "/tmp/afl/out/AFL0/crashes/id:000041,sig:06,src:000000,op:havoc,rep:32".
Jun 20 15:59:36.553 [warn] The abbreviation 'no' is deprecated. Please use 'NodeFamily' instead
Jun 20 15:59:36.571 [warn] Entry 'kltorpc ' in NodeFamily is malformed. Discarding entire list.
Jun 20 15:59:36.572 [warn] Entry 'kltorpc ' in NodeFamily is malformed. Discarding entire list.
Jun 20 15:59:36.572 [err] Reading config failed--see warnings above.
=================================================================
==28441==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 0x4eb568 in malloc (/usr/bin/tor+0x4eb568)
#1 0x9fbc6b in tor_malloc_ /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/common/util.c:171:12
#2 0x9c7b82 in smartlist_new /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/common/container.c:34:21
#3 0x7e73fe in options_init_from_string /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/config.c:4720:7
#4 0x7e4f09 in options_init_from_torrc /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/config.c:4524:12
#5 0x52cf11 in tor_init /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/main.c:2709:7
#6 0x52e2a6 in tor_main /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/main.c:3271:7
#7 0x51c51d in main /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/tor_main.c:30:11
#8 0x444018 in _start (/usr/bin/tor+0x444018)
Indirect leak of 128 byte(s) in 1 object(s) allocated from:
#0 0x4eb568 in malloc (/usr/bin/tor+0x4eb568)
#1 0x9fbc6b in tor_malloc_ /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/common/util.c:171:12
#2 0x9fc050 in tor_malloc_zero_ /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/common/util.c:197:18
#3 0x9fc050 in tor_calloc_ /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/common/util.c:235
#4 0x9c7c0d in smartlist_new /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/common/container.c:37:14
#5 0x7e73fe in options_init_from_string /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/config.c:4720:7
#6 0x7e4f09 in options_init_from_torrc /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/config.c:4524:12
#7 0x52cf11 in tor_init /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/main.c:2709:7
#8 0x52e2a6 in tor_main /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/main.c:3271:7
#9 0x51c51d in main /tmp/portage/net-misc/tor-0.2.7.6/work/tor-0.2.7.6/src/or/tor_main.c:30:11
#10 0x444018 in _start (/usr/bin/tor+0x444018)
SUMMARY: AddressSanitizer: 144 byte(s) leaked in 2 allocation(s).
**Trac**:
**Username**: asarubboTor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/18303Serious and extremely annoying bug2016-02-11T18:57:29ZTracSerious and extremely annoying bugHi, Tor Button have a serious bug. I use Windows 7 x64.
It prevent to maximize the window and freeze screen and display driver. The only page Tor Browser can be maximized is "about:tor" because it set this flag
**extensions.torbutton.st...Hi, Tor Button have a serious bug. I use Windows 7 x64.
It prevent to maximize the window and freeze screen and display driver. The only page Tor Browser can be maximized is "about:tor" because it set this flag
**extensions.torbutton.startup_resize_period** to false
all other pages set the flag to true and start the bug to cause the freeze.
the issue is described here.
https://gitweb.torproject.org/torbutton.git/tree/src/chrome/content/torbutton.js?id=a6f8dcec3bc11bcfc9ded64943051e2408ee9190#n3598
and here
https://trac.torproject.org/projects/tor/ticket/16725
But it is SIX months old.
Really Is it so difficult add a line of code to set the flag to false when the user open a new tab?
I spent half hour EVERY TIME to fix the issue after every system freeze and sometimes I have to reinstall Tor Browser from scratch to solve.
Thank you very much
**Trac**:
**Username**: Blissethttps://gitlab.torproject.org/legacy/trac/-/issues/10517Fail to launch FteProxy (pre-compilled bundles)2020-06-13T18:34:45ZTracFail to launch FteProxy (pre-compilled bundles)To prepare a trip in china, i decided to try differents pluggable transports, to check if these were working well (at least with an uncensored connection). I tried the Tor official pluggable transports bundle (with obsfproxy and flashpro...To prepare a trip in china, i decided to try differents pluggable transports, to check if these were working well (at least with an uncensored connection). I tried the Tor official pluggable transports bundle (with obsfproxy and flashproxy) and it worked well, than i tried to launch the FteProxy pluggable transports bundle, but it didn't worked. When i start Vidalia, the progression bar stays blocked on "Starting", and on "Parsing GEOIP IPv6 file .\Data\Tor\geoip6." in the journal.
I don't know why it doesn't work, because there is no error message or bug signaled, it justs freeze and seems loads. I already has the problem with the regular tor browser bundle in another computer, but i resolved the problem by deleting all the browser bundles and download another one.
Maybe it's provoqued by the new version of Tor (3.5, with Tor Launcher instead of Vidalia), i don't know.
However i hope this bug is resolvable (but everything is, right ?).
Thanks to reply !
**Trac**:
**Username**: Azertherionhttps://gitlab.torproject.org/legacy/trac/-/issues/9911HSDir flag is never assigned/displayed to a relay2020-06-13T18:06:08ZTracHSDir flag is never assigned/displayed to a relaySimply put,
There's a bug where a HSDir flagged relay never has its icon displayed in both detail and search result views.
**Trac**:
**Username**: f3ndotSimply put,
There's a bug where a HSDir flagged relay never has its icon displayed in both detail and search result views.
**Trac**:
**Username**: f3ndotPhilipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/9832Crashes with latest Chrome beta - 30.0.1599.59 beta2020-06-13T16:37:34ZTracCrashes with latest Chrome beta - 30.0.1599.59 betaExtension crashes with latest Chrome beta. It cannot be enabled. Reinstalling didn't affect it. This is the latest https-everywhere-2013.8.17.crx .
Which worked in the previous Chrome beta 30.0.1599.37.
The previous release https-every...Extension crashes with latest Chrome beta. It cannot be enabled. Reinstalling didn't affect it. This is the latest https-everywhere-2013.8.17.crx .
Which worked in the previous Chrome beta 30.0.1599.37.
The previous release https-everywhere-2013.8.16.crx also crashes, so either there's a bug in the new Chrome or the extension isn't compatible with it.
**Trac**:
**Username**: widefoxPeter EckersleyPeter Eckersleyhttps://gitlab.torproject.org/legacy/trac/-/issues/9808WinXP 32bit SP3 Strange quirk/shortcut bug2015-04-24T17:11:54ZTracWinXP 32bit SP3 Strange quirk/shortcut bugRunning the latest Vidalia Relay Bundle, as of 9/23/2013. When its running, if you start notepad (start-->run-->notepad) a shortcut to torrc (Docment and Settings\johndoe\Application Data\Tor\torrc) for the account is created in Start M...Running the latest Vidalia Relay Bundle, as of 9/23/2013. When its running, if you start notepad (start-->run-->notepad) a shortcut to torrc (Docment and Settings\johndoe\Application Data\Tor\torrc) for the account is created in Start Menu (Document and Settings\All Users\Start Menu). Process Monitor (from Microsoft/Sysinternals) says windows explorer (windows\system32\explorer.exe) created the file. Why? Idk.
**Trac**:
**Username**: smallproblemErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/9519HTTPS Everywhere (Chrome) hangs2020-06-13T16:37:28ZTracHTTPS Everywhere (Chrome) hangsWhen trying to connect to yelp.com or yp.com
the HTTPS Everywhere extension hangs.
Using SRWare Iron Version 28.0.1550.1 (210100)
and HTTPS Everywhere Chrome v2013.8.16
**Trac**:
**Username**: MannardWhen trying to connect to yelp.com or yp.com
the HTTPS Everywhere extension hangs.
Using SRWare Iron Version 28.0.1550.1 (210100)
and HTTPS Everywhere Chrome v2013.8.16
**Trac**:
**Username**: MannardPeter EckersleyPeter Eckersleyhttps://gitlab.torproject.org/legacy/trac/-/issues/8912TBB: Firefox not starting.2020-06-15T23:15:42ZTracTBB: Firefox not starting.When trying to start and use the TOR Browser Bundle the Vidalia Control Panel will open and appear to connect properly but after a few seconds the program just closes and no browser appears. I have tried on multiple different versions of...When trying to start and use the TOR Browser Bundle the Vidalia Control Panel will open and appear to connect properly but after a few seconds the program just closes and no browser appears. I have tried on multiple different versions of the TBB, updated all of my drivers, restarted my computer multiple times, and tried to install it to a USB drive and run it from there. Nothing works!
I run a 64-bit Windows 7 OS
## Logs when Vidalia connects, before it closes
May 19 14:36:43.859 [Notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on Windows 7.
May 19 14:36:43.859 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
May 19 14:36:43.859 [Notice] Read configuration file "L:\Tor Browser\Data\Tor\torrc".
May 19 14:36:43.859 [Notice] Initialized libevent version 2.0.21-stable using method win32. Good.
May 19 14:36:43.860 [Notice] Opening Socks listener on 127.0.0.1:9150
May 19 14:36:43.860 [Notice] Opening Control listener on 127.0.0.1:9151
May 19 14:36:44.075 [Notice] Parsing GEOIP file .\Data\Tor\geoip.
May 19 14:36:46.896 [Notice] No AES engine found; using AES_* functions.
May 19 14:36:46.896 [Notice] This OpenSSL has a good implementation of counter mode; using it.
May 19 14:36:46.896 [Notice] OpenSSL OpenSSL 1.0.0k 5 Feb 2013 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
May 19 14:36:46.896 [Notice] Reloaded microdescriptor cache. Found 3527 descriptors.
May 19 14:36:46.896 [Notice] We now have enough directory information to build circuits.
May 19 14:36:46.896 [Notice] Bootstrapped 80%: Connecting to the Tor network.
May 19 14:36:46.896 [Notice] New control connection opened.
May 19 14:36:48.574 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 2 circuits open. I've sent 0 kB and received 0 kB.
May 19 14:36:48.574 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
May 19 14:36:49.008 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
May 19 14:36:52.594 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
May 19 14:36:52.595 [Notice] Bootstrapped 100%: Done.
**Trac**:
**Username**: MCklassicTorBrowserBundle 2.3.x-stablehttps://gitlab.torproject.org/legacy/trac/-/issues/8580Internal Error,Tor Guard Success Rates VERY high2020-06-13T14:28:28ZTracInternal Error,Tor Guard Success Rates VERY high[Sat Mar 23 18:06:09 2013] Tor Software Error - The Tor software encountered an internal bug. Please report the following error message to the Tor developers at bugs.torproject.org: "pathbias_count_build_success(): Bug: Unexpectedly high...[Sat Mar 23 18:06:09 2013] Tor Software Error - The Tor software encountered an internal bug. Please report the following error message to the Tor developers at bugs.torproject.org: "pathbias_count_build_success(): Bug: Unexpectedly high successes counts (255.375000/236.375000) for guard ndnr1=6330CCF8FEED2EF9B12FCF6688E2577C65522BA4
"
**Trac**:
**Username**: branefreezTor: 0.2.4.x-finalMike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/7453[CHROME] Icon in toolbar disappears randomly2020-06-13T16:28:34Zcypherpunks[CHROME] Icon in toolbar disappears randomlyThe HTTPS Everywhere icon in Chrome disappears randomly, running 2012.10.31 on most recent stable Chrome version, on Mac OS 10.8
There is a fix, to disable the extension then re enable it. It happens every other dayThe HTTPS Everywhere icon in Chrome disappears randomly, running 2012.10.31 on most recent stable Chrome version, on Mac OS 10.8
There is a fix, to disable the extension then re enable it. It happens every other dayDan AuerbachDan Auerbach