Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T13:56:38Zhttps://gitlab.torproject.org/legacy/trac/-/issues/334segmentation fault in controller code2020-06-13T13:56:38ZTracsegmentation fault in controller codeversion -- 0.1.2.1-alpha
gdb backtrace --
Core was generated by `/usr/sbin/tor'.
Program terminated with signal 11, Segmentation fault.
#0 handle_control_getinfo (conn=0x83c1580, len=<value optimized out>,
body=0x837bdd8 "stream-...version -- 0.1.2.1-alpha
gdb backtrace --
Core was generated by `/usr/sbin/tor'.
Program terminated with signal 11, Segmentation fault.
#0 handle_control_getinfo (conn=0x83c1580, len=<value optimized out>,
body=0x837bdd8 "stream-status\r\n") at control.c:1455
1455 if (CIRCUIT_IS_ORIGIN(circ))
(gdb) bt
#0 handle_control_getinfo (conn=0x83c1580, len=<value optimized out>,
body=0x837bdd8 "stream-status\r\n") at control.c:1455
#1 0x0807941c in connection_control_process_inbuf_v1 (conn=0x83c1580) at control.c:2414
#2 0x0807962d in connection_control_process_inbuf (conn=0x83c1580) at control.c:2609
#3 0x080672a6 in connection_process_inbuf (conn=0x89, package_partial=1) at connection.c:2066
#4 0x0806a0dd in connection_handle_read (conn=0x83c1580) at connection.c:1313
#5 0x0808d799 in conn_read_callback (fd=4, event=2, _conn=0x83c1580) at main.c:405
#6 0xb7d29c79 in event_base_priority_init () from /usr/lib/libevent-1.1a.so.1
#7 0xb7d29f65 in event_base_loop () from /usr/lib/libevent-1.1a.so.1
#8 0xb7d29dcb in event_loop () from /usr/lib/libevent-1.1a.so.1
#9 0xb7d29cb0 in event_dispatch () from /usr/lib/libevent-1.1a.so.1
#10 0x0808d397 in tor_main (argc=1, argv=0xbfef6724) at main.c:1164
#11 0x080acda2 in main (argc=Cannot access memory at address 0x89
) at tor_main.c:22
#12 0xb7c09ea8 in __libc_start_main () from /lib/tls/libc.so.6
#13 0x0804c781 in _start () at ../sysdeps/i386/elf/start.S:119
--
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: fookoowahttps://gitlab.torproject.org/legacy/trac/-/issues/335Malformed extendcircuit from a controller can crash Tor2020-06-13T13:56:39ZedmanmMalformed extendcircuit from a controller can crash TorIf the controller is naughty and doesn't follow the control-spec.txt for EXTENDCIRCUIT, it can crash Tor.
Tested with 0.1.1.23 and 0.1.2.1-alpha.
[edmanm@adrastea:~]$ telnet localhost 9051
Trying 127.0.0.1...
Connected to localhost.
Es...If the controller is naughty and doesn't follow the control-spec.txt for EXTENDCIRCUIT, it can crash Tor.
Tested with 0.1.1.23 and 0.1.2.1-alpha.
[edmanm@adrastea:~]$ telnet localhost 9051
Trying 127.0.0.1...
Connected to localhost.
Escape character is '!^]'.
authenticate
250 OK
extendcircuit 0 pasiphae thorforlife yargh
Connection closed by foreign host.
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000008
0x00029c78 in handle_control_extendcircuit (conn=0x1588160, len=20457776, body=0x4 <Address 0x4 out of bounds>) at control.c:1751
1751 if (get_purpose(smartlist_get(args,2), 1, &intended_purpose) < 0) {
(gdb) bt
#0 0x00029c78 in handle_control_extendcircuit (conn=0x1588160, len=20457776, body=0x4 <Address 0x4 out of bounds>) at control.c:1751
#1 0x0002d7cc in connection_control_process_inbuf_v1 (conn=0x1588160) at control.c:2417
#2 0x0002e158 in connection_control_process_inbuf (conn=0x1588160) at control.c:2609
#3 0x00020300 in connection_handle_read (conn=0x1588160) at connection.c:1313
#4 0x00040bd4 in conn_read_callback (fd=25165824, event=1, _conn=0xbffff348) at main.c:405
#5 0x00073ba0 in event_base_loop (base=0x500ac0, flags=0) at event.c:256
#6 0x00040830 in tor_main (argc=591304, argv=0xbffff808) at main.c:1164
#7 0x000019ec in _start (argc=3, argv=0xbffff808, envp=0xbffff818) at /SourceCache/Csu/Csu-57.0.82/crt.c:272
#8 0x00001890 in start ()
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/legacy/trac/-/issues/336controller gives us unnamed (ambiguous) nicknames2020-06-13T13:56:39ZRoger Dingledinecontroller gives us unnamed (ambiguous) nicknamesIt looks like the controller circ events mention nicknames of servers, even when
they are unnamed and there are multiple servers with that nickname. They should
be listing keyid.
[Automatically added by flyspray2trac: Operating System: ...It looks like the controller circ events mention nicknames of servers, even when
they are unnamed and there are multiple servers with that nickname. They should
be listing keyid.
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/legacy/trac/-/issues/337getinfo entry-guard should display nicknames2020-06-13T13:56:39ZAndrew Lewmangetinfo entry-guard should display nicknamesIn the controller, getinfo entry-guards displays:
getinfo entry-guards
250+entry-guards=
$445B04E58D03405934CD67937C404F97237BCD6F up
$16D48CCAB785608CD5683378BFC0A6C88A21C086 up
$F5A69E872302685259F1EDDAB3FD69FD9AA43C77 up
$8C727AB7F60F...In the controller, getinfo entry-guards displays:
getinfo entry-guards
250+entry-guards=
$445B04E58D03405934CD67937C404F97237BCD6F up
$16D48CCAB785608CD5683378BFC0A6C88A21C086 up
$F5A69E872302685259F1EDDAB3FD69FD9AA43C77 up
$8C727AB7F60FFB21E37C9D864079E73F31FD2F6A down 2006-09-20 20:50:25
$4DEC68FA337D184C67DD7112BA6AC40E2F6151EB up
$F6AECB92287C4864FE60D981FC39A8EBA8FCEC37 up
I'd like it to display nicknames.
[Automatically added by flyspray2trac: Operating System: Other Linux]https://gitlab.torproject.org/legacy/trac/-/issues/338dump stats uses keyid for IP2020-06-13T13:56:40ZAndrew Lewmandump stats uses keyid for IPSep 20 20:01:05.814 [notice] Service configured in "/var/lib/tor/hidden_service/":
Sep 20 20:01:05.814 [notice] Intro point at $370DBEAB52857D89333B66B4DDDA5AA2F95FADE1: circuit is open
Sep 20 20:01:05.814 [notice] Intro point at $B5...Sep 20 20:01:05.814 [notice] Service configured in "/var/lib/tor/hidden_service/":
Sep 20 20:01:05.814 [notice] Intro point at $370DBEAB52857D89333B66B4DDDA5AA2F95FADE1: circuit is open
Sep 20 20:01:05.814 [notice] Intro point at $B59573CCCED8E8A96B6DDA70C818F65CC3799532: circuit is open
Sep 20 20:01:05.814 [notice] Intro point at $8CCA8F718E687F2B38CAAECF114278ADE7ACC597: circuit is open
Should the keyids be nicknames?
[Automatically added by flyspray2trac: Operating System: Other Linux]https://gitlab.torproject.org/legacy/trac/-/issues/339getinfo address doesn't work2020-06-13T13:56:40ZAndrew Lewmangetinfo address doesn't workgetinfo address
552 Unrecognized key "address"
line 1524 of control.c states:
" } else if (!strcmp(question, "address")) {
uint32_t addr;
if (router_pick_published_address(get_options(), &addr) < 0)
return -1;
*answer...getinfo address
552 Unrecognized key "address"
line 1524 of control.c states:
" } else if (!strcmp(question, "address")) {
uint32_t addr;
if (router_pick_published_address(get_options(), &addr) < 0)
return -1;
*answer = tor_dup_addr(addr);
"
Is this getinfo address only for servers?
If so, the control-spec.txt doesn't state this.
[Automatically added by flyspray2trac: Operating System: Other Linux]https://gitlab.torproject.org/legacy/trac/-/issues/340WinXP VC++ Debug Error2020-06-13T13:56:40ZTracWinXP VC++ Debug ErrorA few days ago I installed the tor 0.1.1.23 bundle on WinXP SP2 (XP2500+, 1gb).
I configured it as a middle-man only server. It's behind a NAT router.
Today I found a MS VC++ Debug Library error on my desktop:
Debug Error!
Program...A few days ago I installed the tor 0.1.1.23 bundle on WinXP SP2 (XP2500+, 1gb).
I configured it as a middle-man only server. It's behind a NAT router.
Today I found a MS VC++ Debug Library error on my desktop:
Debug Error!
Program: D:\Net\Tor\tor.exe
This application has requested the runtime to terminate it in an unusual way
Please contact the application's support team for more information
I clicked on Retry to "debug" and got the standard XP fault window. Unfortunately
I neglected to save the appcompat file containing the details.
Vidalia seemed to be hung after this. I terminated Vidalia, restarted it (which
restarted tor) and all is running fine again.
Not much to go on, I know. I'll add details if it happens again.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: torsrv-ishttps://gitlab.torproject.org/legacy/trac/-/issues/341Mac OS X: bad permissions for log file2020-06-13T13:56:41ZTracMac OS X: bad permissions for log fileFollowing Apple guidelines, the location of Tor log file is incorrect (should be in /var/log/). A link is made from /var/log/tor to //Library/Tor/var/log/tor.
However, permissions are wrong when compared to other system logs and applicat...Following Apple guidelines, the location of Tor log file is incorrect (should be in /var/log/). A link is made from /var/log/tor to //Library/Tor/var/log/tor.
However, permissions are wrong when compared to other system logs and application Console.app cannot read it. File should be owned by root:admin
and permissions set to -rw-r-----
[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]
**Trac**:
**Username**: Steff-XAndrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/342No connections after start of next interval of AccountingStart?2020-06-13T13:56:41ZTracNo connections after start of next interval of AccountingStart?The server 'roundabout' started a new interval on 4th Oct. 00:00.
By this time no traffic amount is logged as related to Tor (as of 4th Oct. 18:38) although notices.log
shows the messages that the server should be waked up at 08:05:24 l...The server 'roundabout' started a new interval on 4th Oct. 00:00.
By this time no traffic amount is logged as related to Tor (as of 4th Oct. 18:38) although notices.log
shows the messages that the server should be waked up at 08:05:24 local time.
torrc has the following settings:
AccountingStart month 4 00:00
AccountingMax 145 GB
The file /var/log/tor/notices.log shows the following:
---snip---
Oct 04 00:00:00.011 [notice] accounting_set_wakeup_time(): Configured hibernation. This interval began at 2006-10-04 00:00:00; the scheduled wake-up time is 2006-10-04 08:05:24; we expect to exhaust our quota for this interval around 2006-11-03 20:43:24; the next interval begins at 2006-11-04 00:00:00 (all times local)
Oct 04 00:00:01.031 [notice] consider_hibernation(): Commencing hibernation. We will wake up at 2006-10-04 08:05:24 local time.
Oct 04 00:00:01.031 [notice] hibernate_go_dormant(): Going dormant. Blowing away remaining connections.
Oct 04 00:26:28.771 [notice] I learned some more directory information, but not enough to build a circuit.
Oct 04 00:56:57.609 [notice] I learned some more directory information, but not enough to build a circuit.
[....]
Oct 04 07:44:40.899 [notice] I learned some more directory information, but not enough to build a circuit.
Oct 04 08:15:10.531 [notice] I learned some more directory information, but not enough to build a circuit.
[....]
Oct 04 17:30:22.398 [notice] I learned some more directory information, but not enough to build a circuit.
Oct 04 18:00:54.076 [notice] I learned some more directory information, but not enough to build a circuit.
Oct 04 18:31:24.745 [notice] I learned some more directory information, but not enough to build a circuit.
---snap---
[....] means the messages repeated with different timestamps.
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: Maschi0.1.2.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/344tor terminates when running out of memory2020-06-13T13:56:42ZTractor terminates when running out of memoryI am running a tor 0.1.1.24-1~~sarge.1 server on a virtual server (OpenVZ).
One thing about OpenVZ is that the amount of memory available to the virtual machine varies all the time.
The server shuts down when it runs out of memory:
Logf...I am running a tor 0.1.1.24-1~~sarge.1 server on a virtual server (OpenVZ).
One thing about OpenVZ is that the amount of memory available to the virtual machine varies all the time.
The server shuts down when it runs out of memory:
Logfile entry:
Oct xx xx:xx:xx.xxx [err] _tor_realloc(): Out of memory. Dying.
I would like tor to keep running when it runs out of memory - perhaps it can just close a few connections,
stop accepting new connections for a while, discard some buffers etc?
Tor terminating because it runs out of memory is not listed at
http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#head-43d0c843cb6c453ad1231c48c11196a46fae9540
so I think perhaps this is a bug?
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: snpost 0.2.0.xNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/346memory leak in router_rebuild_store() in routerlist.c2020-06-13T13:56:42ZTracmemory leak in router_rebuild_store() in routerlist.ctor/src/or % cat routerlist.c.diff
268c268
< smartlist_t *lst = smartlist_create();
---
> smartlist_t *lst;
283d282
< smartlist_free(lst);
321,322d319
< smartlist_free(old_routers);
< smartlist_free(routers);
333a331...tor/src/or % cat routerlist.c.diff
268c268
< smartlist_t *lst = smartlist_create();
---
> smartlist_t *lst;
283d282
< smartlist_free(lst);
321,322d319
< smartlist_free(old_routers);
< smartlist_free(routers);
333a331,332
> smartlist_free(old_routers);
> smartlist_free(routers);
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: fookoowahttps://gitlab.torproject.org/legacy/trac/-/issues/347Some controller signals only work on unix2020-06-13T13:56:43ZRoger DingledineSome controller signals only work on unixcontrol_signal_check() and control_signal_act hard-code the
signal numbers to be the ones used in unix.
But handle_control_signal() uses the system-defined values for them.
One of these behaviors is wrong.
E.g., USR1 and USR2 (among p...control_signal_check() and control_signal_act hard-code the
signal numbers to be the ones used in unix.
But handle_control_signal() uses the system-defined values for them.
One of these behaviors is wrong.
E.g., USR1 and USR2 (among possibly others) don't work on OS X from the
controller.
[Automatically added by flyspray2trac: Operating System: All]0.1.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/348Excessive loggin at warning2020-06-13T13:56:43ZTracExcessive loggin at warningActual version is 23, not 24. Installed with vidalia package pre-made for Mac Os X.
Problem: I'm getting LOTS of log messages like:
Oct 25 08:17:16 stbmac Tor[14520]: add_nickname_list_to_smartlist(): Nickname list includes 'serifos' w...Actual version is 23, not 24. Installed with vidalia package pre-made for Mac Os X.
Problem: I'm getting LOTS of log messages like:
Oct 25 08:17:16 stbmac Tor[14520]: add_nickname_list_to_smartlist(): Nickname list includes 'serifos' which is known but down.\n
Oct 25 08:17:17 stbmac Tor[14520]: add_nickname_list_to_smartlist(): Nickname list includes 'lefkada' which is known but down.\n
These go away if I tell my system to stop using tor. I get these every time
something on my system that pays attention to my HTTP proxy settings tries
to open a connection.
In my config file, I have EntryNodes and ExitNodes set to a large set of
high bandwidth nodes located on my continent (as an attempt to make Tor run
faster -- it was too slow out of the box with no config help).
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: keybounce0.1.2.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/349getinfo network-status sometimes returns an incomplete list2020-06-13T13:56:44Zedmanmgetinfo network-status sometimes returns an incomplete listSometimes Tor's response to a "getinfo network-status" does not appear to include all known OR identities.
Some servers may not be included in the returned list, even though Tor has built circuits through them. Sometimes
the returned l...Sometimes Tor's response to a "getinfo network-status" does not appear to include all known OR identities.
Some servers may not be included in the returned list, even though Tor has built circuits through them. Sometimes
the returned list is entirely empty, even though Tor has built circuits and displayed its happy "Tor has
successfully opened a circuit" message.
Here is an example:
getinfo network-status
250-network-status=autonomynodev2=$EFE988B0EF6A708F5BB6A843AC507604D0C38239 KB=$C938A72F7E0333CEF5AA7C0B45FC74EF4E02F55D HaschMichMaedc
hen=$F9D4EC6EAC081C3F26BF703932B07BB1B161F22F histor2=$3276923C1617879D3246133BD37111A661461382 hppie=$BBEB4939DF13BAC358DF49608C3B760A
A6047EAB $D8632EAE2A5CA7BA147AB5489D43B5E2E80C37D7 $02FF7F59145E4917321739947585C757B22B4008 $1783E1CD818BB74FB20FE46E7317FBC26D13172E
$519C8B8E1A51F3D2593B6675A9768D83F9F041CB $999C4E1F995A0714E7D64E8A6CD09AC4490E72D6
250 OK
getinfo circuit-status
250+circuit-status=
7 BUILT freetux4ever,enterprise,utcluj
5 BUILT freetux4ever,spinell,waabbeel
4 BUILT myrandomnode,spinell,Tonga
3 BUILT myrandomnode,l3cht3rn3t,idbsgetyrubdgretyrw
.
250 OK
Tor returned a list of ten servers and has currently built four circuits using nine distinct servers. Doing a
"getinfo desc/id/<keyid>" for each of the non-Named servers above told me they have the following nicknames:
nonec549299e43~$D8632EAE2A5CA7BA147AB5489D43B5E2E80C37D7
QuePuedo~$02FF7F59145E4917321739947585C757B22B4008
kazol~$1783E1CD818BB74FB20FE46E7317FBC26D13172E
hiball~$519C8B8E1A51F3D2593B6675A9768D83F9F041CB
farse~$999C4E1F995A0714E7D64E8A6CD09AC4490E72D6
We see that the set of servers returned by "getinfo network-status" and the set of servers through which we
have built circuits are even disjoint, in this case.
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/legacy/trac/-/issues/350infinite loop on evil controlport input2020-06-13T13:56:44ZRoger Dingledineinfinite loop on evil controlport inputecho -ne "authenticate\r\nsignal newnym\r\nquit\r\n" | telnet localhost 9051
telnet seems to replace the first \n with a \0. I'm not sure why. But when
it does, Tor gets stuck in a loop in find_crlf_on_buf().
r8843 contains a fix to ma...echo -ne "authenticate\r\nsignal newnym\r\nquit\r\n" | telnet localhost 9051
telnet seems to replace the first \n with a \0. I'm not sure why. But when
it does, Tor gets stuck in a loop in find_crlf_on_buf().
r8843 contains a fix to make Tor not die. Is this the right fix? Is there more
to fix?
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/legacy/trac/-/issues/351_circuit_mark_for_close(): Reason 9 out of range at command.c:3782020-06-13T13:56:44ZTrac_circuit_mark_for_close(): Reason 9 out of range at command.c:378Hi,
On server roundabout in notices.log the following messages appears more or less regularly:
---snip---
Oct 31 20:24:00.374 [warn] _circuit_mark_for_close(): Reason 9 out of range at command.c:378
---snap---
The server is connectable...Hi,
On server roundabout in notices.log the following messages appears more or less regularly:
---snip---
Oct 31 20:24:00.374 [warn] _circuit_mark_for_close(): Reason 9 out of range at command.c:378
---snap---
The server is connectable and in use (tested with tcpdump) although it is not listed on http://torstat.xenobite.eu/ anymore.
Regards,
Joerg
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: Maschihttps://gitlab.torproject.org/legacy/trac/-/issues/352Vidalia wont start2020-06-13T13:56:44ZTracVidalia wont startAfter instaling the Vidalia download I receive the following error -
vidalia.exe
vidalia.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
P. S. I have a saved screen image that shows the exact ...After instaling the Vidalia download I receive the following error -
vidalia.exe
vidalia.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
P. S. I have a saved screen image that shows the exact error, if that will help.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: hexadecimatorAndrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/353Tor-0.1.2.2-alpha-win32 wont do .onion2020-06-13T13:56:45ZTracTor-0.1.2.2-alpha-win32 wont do .onionI tried to use the Tor-0.1.2.2-alpha-win32 package and all seemed to work as normal but...
I was unable to connect to .onion sites.
At first i thought i did something wrong but after degrading to 0.1.1.24 with unaltered config i was abl...I tried to use the Tor-0.1.2.2-alpha-win32 package and all seemed to work as normal but...
I was unable to connect to .onion sites.
At first i thought i did something wrong but after degrading to 0.1.1.24 with unaltered config i was able to.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: TriMoonAndrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/354Web based config/status interface2020-06-13T13:56:45ZTracWeb based config/status interfaceI think it would be very beneficial to everyone using tor to have a web based config/report functionality built into tor.
The most logical URL would then be "config.onion" and "status.onion".
This will eliminate all the different client...I think it would be very beneficial to everyone using tor to have a web based config/report functionality built into tor.
The most logical URL would then be "config.onion" and "status.onion".
This will eliminate all the different clients used to control tor.
Ofcourse the control port should remain operational for a while to let users have an option to adjust and shift to the new way...
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: TriMoonhttps://gitlab.torproject.org/legacy/trac/-/issues/355tor server crashes after an hour2020-06-13T13:56:46ZTractor server crashes after an hourI've set up a tor server with both the latest stable and newest alpha versions. Both crash after about the same amount of time. The error in the log is:
Nov 03 23:19:06:199 [Error] do_main_loop(): libevent call with win32 failed: Invalid...I've set up a tor server with both the latest stable and newest alpha versions. Both crash after about the same amount of time. The error in the log is:
Nov 03 23:19:06:199 [Error] do_main_loop(): libevent call with win32 failed: Invalid argument [WSAEINVAL ] [10022]
In the alpha version there was a similar error related to libevent.
I saw libevent mentioned in the wiki on reporting a bug, but it didn't tell me how I would update something like that.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: darkmagessAndrew LewmanAndrew Lewman