Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:01:51Zhttps://gitlab.torproject.org/legacy/trac/-/issues/982Crash in closing tls connection2020-06-13T14:01:51ZTracCrash in closing tls connectionHappens seemingly at random after a long go of running.
"""
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you ar...Happens seemingly at random after a long go of running.
"""
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/libz.so.1...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /usr/lib/libevent-1.3e.so.1...done.
Loaded symbols for /usr/lib/libevent-1.3e.so.1
Reading symbols from /lib/libssl.so.0.9.8...done.
Loaded symbols for /lib/libssl.so.0.9.8
Reading symbols from /lib/libcrypto.so.0.9.8...done.
Loaded symbols for /lib/libcrypto.so.0.9.8
Reading symbols from /lib/libpthread.so.0...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/libnsl.so.1...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/librt.so.1...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libresolv.so.2...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib/libnss_compat.so.2...done.
Loaded symbols for /lib/libnss_compat.so.2
Reading symbols from /lib/libnss_nis.so.2...done.
Loaded symbols for /lib/libnss_nis.so.2
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_mdns4_minimal.so.2...done.
Loaded symbols for /lib/libnss_mdns4_minimal.so.2
Reading symbols from /lib/libnss_dns.so.2...done.
Loaded symbols for /lib/libnss_dns.so.2
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Core was generated by `/usr/sbin/tor'.
Program terminated with signal 11, Segmentation fault.
[New process 16346]
[New process 23317]
[New process 23318]
[New process 23320]
[New process 23319]
#0 0x00007f9792a80693 in CRYPTO_add_lock () from /lib/libcrypto.so.0.9.8
(gdb) bt
#0 0x00007f9792a80693 in CRYPTO_add_lock () from /lib/libcrypto.so.0.9.8
#1 0x00007f9792aebc29 in EVP_PKEY_free () from /lib/libcrypto.so.0.9.8
#2 0x00007f9792dd8771 in ssl_cert_free () from /lib/libssl.so.0.9.8
#3 0x00007f9792dd71d8 in SSL_free () from /lib/libssl.so.0.9.8
#4 0x00000000004b6ab3 in tor_tls_free (tls=0x2159fa0) at tortls.c:922
#5 0x00000000004280bf in _connection_free (conn=0x50720d0) at connection.c:388
#6 0x000000000046093c in close_closeable_connections () at main.c:602
#7 0x0000000000461033 in second_elapsed_callback (fd=<value optimized out>, event=<value optimized out>, args=<value optimized out>)
at main.c:1094
#8 0x00007f9792ff867d in event_base_loop () from /usr/lib/libevent-1.3e.so.1
#9 0x00000000004619c6 in do_main_loop () at main.c:1435
#10 0x0000000000461c15 in tor_main (argc=1, argv=<value optimized out>) at main.c:2060
#11 0x00007f97922a65a6 in __libc_start_main () from /lib/libc.so.6
#12 0x0000000000407469 in _start ()
(gdb) info frame 4
Stack frame at 0x7fff9b642140:
rip = 0x4b6ab3 in tor_tls_free (tortls.c:922); saved rip 0x4280bf
called by frame at 0x7fff9b642180, caller of frame at 0x7fff9b642120
source language c.
Arglist at 0x7fff9b642118, args: tls=0x2159fa0
Locals at 0x7fff9b642118, Previous frame's sp is 0x7fff9b642140
Saved registers:
rbx at 0x7fff9b642130, rip at 0x7fff9b642138
(gdb) f 4
#4 0x00000000004b6ab3 in tor_tls_free (tls=0x2159fa0) at tortls.c:922
922 tortls.c: No such file or directory.
in tortls.c
(gdb) p *tls
$1 = {node = {hte_next = 0x0, hte_hash = 31986572}, context = 0x7f97883ce9f0, ssl = 0x7a04e30, socket = 1382, address = 0x7c344f0 "[scrubbed]",
state = TOR_TLS_ST_OPEN, isServer = 1, wasV2Handshake = 1, got_renegotiate = 0, wantwrite_n = 0, last_write_count = 130436,
last_read_count = 9660, negotiated_callback = 0, callback_arg = 0x0}
"""
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: neoeinsteinTor: 0.2.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/943Tor's once-per-second events are not quite once-per-second?2020-06-13T14:01:27ZRoger DingledineTor's once-per-second events are not quite once-per-second?Mar 16 11:07:43.655 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:44.659 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:45.663 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar...Mar 16 11:07:43.655 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:44.659 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:45.663 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:46.667 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:47.671 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:48.675 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:49.676 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:50.679 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
Mar 16 11:07:51.683 [debug] QtDebugMsg: torcontrol: Control Event: 650 BW 0 0
My 'bw' events are getting sent out slightly more than one second
apart. Didn't we try to send them out every second? More broadly,
is libevent calling our once-a-second events every 1.004 seconds or
the like?
Maybe that evtimer_add() call in second_elapsed_callback() should be at
the beginning? That seems a bit more fragile in the case where it takes
a whole second to process stuff. But if it takes any non-trivial amount
of time to process stuff, then that function isn't reliably getting
called once a second. How big a problem is that?
[Automatically added by flyspray2trac: Operating System: All]Tor: 0.2.2.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/928With BridgeRelay 1 and ORPort 0, things go bad2020-06-13T14:01:17ZRoger DingledineWith BridgeRelay 1 and ORPort 0, things go badA while ago Vidalia set my BridgeRelay to 1 but left my ORPort off. This
caused my Tor to make all sorts of weird decisions about what it would
contact, what it would fetch, etc. After a while my Tor became useless
because it didn't have...A while ago Vidalia set my BridgeRelay to 1 but left my ORPort off. This
caused my Tor to make all sorts of weird decisions about what it would
contact, what it would fetch, etc. After a while my Tor became useless
because it didn't have enough descriptors to make a circuit, and it didn't
care to get any more.
We fixed the Vidalia bug (I think), but if a user sets their config this
way they will end up sad. We should explore why this is, and tighten up
the checks inside Tor.
[Automatically added by flyspray2trac: Operating System: All]Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/919If you hup tor while it's hibernating, it rebinds its ports2020-06-13T14:01:13ZRoger DingledineIf you hup tor while it's hibernating, it rebinds its portsIt looks like retry_listeners() and retry_all_listeners() do not care
whether we're hibernating. In main.c, retry-all-listeners is only called if
if (!we_are_hibernating() && time_to_check_listeners < now) {
whereas in config.c it do...It looks like retry_listeners() and retry_all_listeners() do not care
whether we're hibernating. In main.c, retry-all-listeners is only called if
if (!we_are_hibernating() && time_to_check_listeners < now) {
whereas in config.c it does not check if we_are_hibernating. Sounds like that's
the place to fix it.
[Automatically added by flyspray2trac: Operating System: All]Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/911Authorities assign Running flag to hibernating relays?2020-06-13T14:06:17ZRoger DingledineAuthorities assign Running flag to hibernating relays?Mikeperry noted that it looks like authorities are assigning the Running
flag if a relay has been reachable within the past however many minutes,
even if the relay published its latest descriptor with "hibernating 1"
in it.
Even if so, ...Mikeperry noted that it looks like authorities are assigning the Running
flag if a relay has been reachable within the past however many minutes,
even if the relay published its latest descriptor with "hibernating 1"
in it.
Even if so, it isn't a big deal, since those latest descriptors will claim
a bandwidth of 0, and so clients will avoid them. But still, worth fixing
at some point.
[Automatically added by flyspray2trac: Operating System: All]Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/792libevent "error" causes Tor not to start at all2020-06-13T14:06:45ZTraclibevent "error" causes Tor not to start at allThis is only tested on Windows Vista with Service Pack 1 and all updates except Windows Search 4.0
Tor 0.2.0.30 stable version was released officially a few days ago, but upon upgrading or uninstalling/reinstalling, the following messag...This is only tested on Windows Vista with Service Pack 1 and all updates except Windows Search 4.0
Tor 0.2.0.30 stable version was released officially a few days ago, but upon upgrading or uninstalling/reinstalling, the following messages always showed up 100% of the time.
Aug 03 19:44:21.798 [Notice] Tor v0.2.0.30 (r15956). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows "Longhorn" Service Pack 1 [workstation] {terminal services, single user})
Aug 03 19:44:21.936 [Error] Error from libevent: evsignal_init: socketpair: No error
First of all this should not be experimental software since it is a stable release, and how come I am unable to start Tor especially when the "error" is actually "No error"?
[Automatically added by flyspray2trac: Operating System: Windows Vista]
**Trac**:
**Username**: coshanTor: 0.2.2.x-finalNick MathewsonNick Mathewson