Trac issues
https://gitlab.torproject.org/legacy/trac/-/issues
2020-06-13T14:01:05Z
https://gitlab.torproject.org/legacy/trac/-/issues/902
It appears there is a bug in the intersection of the bandwidthrate and accoun...
2020-06-13T14:01:05Z
Trac
It appears there is a bug in the intersection of the bandwidthrate and accountingmax
It appears there is a bug in the intersection of the bandwidthrate and
accountingmax when set to ridiculously high levels (999 TB).
But perhaps also at lower settings (9 GB).
Jan 05 19:10:54.773 [notice] Configured hibernation. This ...
It appears there is a bug in the intersection of the bandwidthrate and
accountingmax when set to ridiculously high levels (999 TB).
But perhaps also at lower settings (9 GB).
Jan 05 19:10:54.773 [notice] Configured hibernation. This interval began at 2009-01-05 12:21:00; the scheduled
wake-up time was 2009-01-05 12:21:00; we expect to exhaust our quota for this interval around 2009-01-06 12:21:00;
the next interval begins at 2009-01-06 12:21:00 (all times local)
Jan 05 19:12:10.984 [notice] Received reload signal (hup). Reloading config.
Jan 05 19:12:10.988 [notice] Tor 0.2.0.32 (r17346) opening log file.
AccountingStart day 12:21
AccountingMax 5 GB
BandwidthRate 20000
BandwidthBurst 21000
`Low traffic` is the result
20000*3600*24 is less than 5 GB?
[Automatically added by flyspray2trac: Operating System: Fedora Core Linux]
**Trac**:
**Username**: udo
https://gitlab.torproject.org/legacy/trac/-/issues/903
Crash when runnig as Service
2020-06-13T14:01:05Z
Trac
Crash when runnig as Service
When used as a service it terminates unexpectantly with either error 1064 or 1067 without any warning.
This happends as the service tries to start, everytime.
Torrc found here : http://pastebin.com/f514929fb
When run as a regular progr...
When used as a service it terminates unexpectantly with either error 1064 or 1067 without any warning.
This happends as the service tries to start, everytime.
Torrc found here : http://pastebin.com/f514929fb
When run as a regular program it doesn't get any errors.
The regular program and service uses the same torrc.
OS: win XP.
memory : 1GB
no other errors are registerd at or near the time the service stops.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: zerak
https://gitlab.torproject.org/legacy/trac/-/issues/904
When we fail to decrypt an onionskin, we never reply
2020-06-13T14:01:06Z
Roger Dingledine
When we fail to decrypt an onionskin, we never reply
On my bridge:
Jan 06 13:06:06.447 [debug] router_set_status(): Marking router 'moria1/128.31.0
.34' as up.
Jan 06 13:06:06.447 [debug] circuit_n_conn_done(): or_conn to moria1/128.31.0.34
, status=1
Jan 06 13:06:06.447 [debug] circuit_n...
On my bridge:
Jan 06 13:06:06.447 [debug] router_set_status(): Marking router 'moria1/128.31.0
.34' as up.
Jan 06 13:06:06.447 [debug] circuit_n_conn_done(): or_conn to moria1/128.31.0.34
, status=1
Jan 06 13:06:06.447 [debug] circuit_n_conn_done(): Found circ, sending create ce
ll.
Jan 06 13:06:06.447 [debug] circuit_send_next_onion_skin(): First skin; sending
create cell.
Jan 06 13:06:06.449 [debug] circuit_deliver_create_cell(): Chosen circID 23991.
Jan 06 13:06:06.449 [debug] append_cell_to_circuit_queue(): Made a circuit activ
e.
Jan 06 13:06:06.449 [info] circuit_send_next_onion_skin(): First hop: finished s
ending CREATE cell to 'moria1'
Jan 06 13:06:06.449 [info] command_process_netinfo_cell(): Got good NETINFO cell
from 128.31.0.34; OR connection is now open, using protocol version 2
...
Jan 06 13:06:36.449 [info] circuit_expire_building(): Abandoning circ 128.31.0.3
4:9001:23991 (state 0:doing handshakes, purpose 5)
Jan 06 13:06:36.449 [info] exit circ (length 1, exit moria1): $FFCB46DB1339DA846
74C70D7CB586434C4370441(waiting for keys)
Jan 06 13:06:36.449 [info] circuit_build_failed(): Our circuit failed to get a r
esponse from the first hop (128.31.0.34:9001). I'm going to try to rotate to a b
etter connection.
Jan 06 13:06:36.449 [info] connection_ap_fail_onehop(): Closing onehop stream to
'$FFCB46DB1339DA84674C70D7CB586434C4370441/128.31.0.34' because the OR conn jus
t failed.
On moria1 at the same time:
Jan 06 13:06:06.447 [info] tor_tls_read(): Got a TLS renegotiation from "128.31.
0.34"
Jan 06 13:06:06.447 [info] command_process_versions_cell(): Negotiated version 2
with 128.31.0.34; sending NETINFO.
Jan 06 13:06:06.449 [info] command_process_netinfo_cell(): Got good NETINFO cell
from 128.31.0.34; OR connection is now open, using protocol version 2
Jan 06 13:06:06.491 [info] onion_skin_server_handshake(): Couldn't decrypt onion
skin: client may be using old onion key
Shouldn't moria1 be sending something back to indicate failure?
[Automatically added by flyspray2trac: Operating System: All]
0.2.1.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/905
ServerDNSRandomizeCase config option without effect
2020-06-13T14:01:06Z
Trac
ServerDNSRandomizeCase config option without effect
My Tor exit gw always randomizes cases in dns queries. Setting "ServerDNSRandomizeCase 0" has no effect. I checked with
v0.2.1.8-alpha (r17523) and v0.2.1.10-alpha (r17969).
[Automatically added by flyspray2trac: Operating System: All]...
My Tor exit gw always randomizes cases in dns queries. Setting "ServerDNSRandomizeCase 0" has no effect. I checked with
v0.2.1.8-alpha (r17523) and v0.2.1.10-alpha (r17969).
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Falo
0.2.1.11-alpha
Nick Mathewson
Nick Mathewson
https://gitlab.torproject.org/legacy/trac/-/issues/906
crash in getinfo_helper_dir <- handle_control_getinfo <- connection_control_p...
2020-06-13T14:01:07Z
Trac
crash in getinfo_helper_dir <- handle_control_getinfo <- connection_control_process_inbuf
in version 0.1.2.19 (btw, please add more versions to the input box?)
(ubuntu 8.04 amd64, tor 0.1.2.19-2)
tor crashed:
#0 0x000000000042ba6f in getinfo_helper_dir (control_conn=<value optimized out>,
question=0x139a7f0 "dir/serve...
in version 0.1.2.19 (btw, please add more versions to the input box?)
(ubuntu 8.04 amd64, tor 0.1.2.19-2)
tor crashed:
#0 0x000000000042ba6f in getinfo_helper_dir (control_conn=<value optimized out>,
question=0x139a7f0 "dir/server/fp/DCA644B81B06B83F86F6A76EC6974627380C6865", answer=0x7fff6a16a990) at control.c:1281
1281 control.c: No such file or directory.
in control.c
(gdb) bt
#0 0x000000000042ba6f in getinfo_helper_dir (control_conn=<value optimized out>,
question=0x139a7f0 "dir/server/fp/DCA644B81B06B83F86F6A76EC6974627380C6865", answer=0x7fff6a16a990) at control.c:1281
#1 0x0000000000430a1f in handle_control_getinfo (conn=0xc48730, len=<value optimized out>, body=<value optimized out>) at control.c:1618
#2 0x0000000000431cd1 in connection_control_process_inbuf (conn=0xc48730) at control.c:2449
#3 0x000000000042261f in connection_handle_read (conn=0xc48730) at connection.c:1465
#4 0x00000000004460a0 in conn_read_callback (fd=<value optimized out>, event=<value optimized out>, _conn=<value optimized out>) at main.c:422
#5 0x00007f416113bf41 in event_base_loop (base=0x6d5de0, flags=<value optimized out>) at event.c:331
#6 0x0000000000445ceb in tor_main (argc=1, argv=<value optimized out>) at main.c:1270
#7 0x00007f4160df11c4 in __libc_start_main () from /lib/libc.so.6
#8 0x00000000004068f9 in _start ()
I have the core file, if you need more info tell me what to write in gdb -c core etc
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: limcoretor
https://gitlab.torproject.org/legacy/trac/-/issues/907
HardwareAccel isn't used
2020-06-13T14:01:08Z
Trac
HardwareAccel isn't used
Log shows me:
[info] crypto_global_init(): Initializing OpenSSL via tor_tls_init().
but crypto.c says:
if (useAccel < 0) {
log_info(LD_CRYPTO, "Initializing OpenSSL via tor_tls_init().");
}
if (useAccel > 0) {
l...
Log shows me:
[info] crypto_global_init(): Initializing OpenSSL via tor_tls_init().
but crypto.c says:
if (useAccel < 0) {
log_info(LD_CRYPTO, "Initializing OpenSSL via tor_tls_init().");
}
if (useAccel > 0) {
log_info(LD_CRYPTO, "Initializing OpenSSL engine support.");
ENGINE_load_builtin_engines();
if (!ENGINE_register_all_complete())
return -1;
So no HardwareAccel even though torrc says:
HardwareAccel 1
This is Fedora 10 on VIA EK8000. Tor 0.2.0.32, built with source and spec from tor.eff site.
[Automatically added by flyspray2trac: Operating System: Fedora Core Linux]
**Trac**:
**Username**: udo
https://gitlab.torproject.org/legacy/trac/-/issues/908
User Agent Switcher resets Torbutton's spoofed user agent
2009-03-13T07:31:21Z
Trac
User Agent Switcher resets Torbutton's spoofed user agent
In Debian with Iceweasel 3.0.4-1 the Addon Torbutton (1.2.0) does not change the User Agent of the Browser.
Other Addons I'm using: AdBlock Plus (1.0.1), RefControl (0.8.11), Mouse Gestures Redox (2.0.2) and
User Agent Switcher (0.6.1...
In Debian with Iceweasel 3.0.4-1 the Addon Torbutton (1.2.0) does not change the User Agent of the Browser.
Other Addons I'm using: AdBlock Plus (1.0.1), RefControl (0.8.11), Mouse Gestures Redox (2.0.2) and
User Agent Switcher (0.6.11). I tested, if the user agent is changed if the last mentioned addon is disabled -
but this had no effect:
Always my same full User Agent is shown like this:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4) Gecko/2008112309 Iceweasel/3.0.4 (Debian-3.0.4-1)
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: rollanothernumber
https://gitlab.torproject.org/legacy/trac/-/issues/909
Cookie Privacy not restored
2009-02-20T04:29:30Z
Trac
Cookie Privacy not restored
My usual configuration of Privacy Setting is "Accept cookies from sites" and "Keep until: I close Firefox". When switching
to tor using torbutton and back again the setting is not restored but to the default value "Keep until: they expir...
My usual configuration of Privacy Setting is "Accept cookies from sites" and "Keep until: I close Firefox". When switching
to tor using torbutton and back again the setting is not restored but to the default value "Keep until: they expire".
That's annoying and might be a security risk if the cookies are not strictly separated.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: leviathan
https://gitlab.torproject.org/legacy/trac/-/issues/910
"LANG" not replaced in navigator.appVersion
2009-02-20T09:07:35Z
Trac
"LANG" not replaced in navigator.appVersion
"LANG" doesn't seem to be replaced in navigator.appVersion (it's replaced in appName instead).
check value of navigator.appVersion when running torbutton to see
[Automatically added by flyspray2trac: Operating System: All]
**Trac**: ...
"LANG" doesn't seem to be replaced in navigator.appVersion (it's replaced in appName instead).
check value of navigator.appVersion when running torbutton to see
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: pointlessreg
https://gitlab.torproject.org/legacy/trac/-/issues/911
Authorities assign Running flag to hibernating relays?
2020-06-13T14:06:17Z
Roger Dingledine
Authorities 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-final
https://gitlab.torproject.org/legacy/trac/-/issues/912
Tor says "data cell dropped, unknown stream", no furter usage of Tor possible
2020-06-13T14:01:10Z
Trac
Tor says "data cell dropped, unknown stream", no furter usage of Tor possible
It is the third time this happens to me on this computer.
Tor was running all smooth on the computer, but today I am not able to connect to any website through Tor.
It looks pretty normal and Firefox already shows the favicon when out o...
It is the third time this happens to me on this computer.
Tor was running all smooth on the computer, but today I am not able to connect to any website through Tor.
It looks pretty normal and Firefox already shows the favicon when out of nowhere Firefox acts
like someone pressed the reload button. The connection to the site is halted and then Firefox tries to reconnect.
This happens before the page content is rendered in the browser so I don't know how much data was already processed
till the reconnection happens.
At the same time this "reconnect" happens, the Tor log says:
[Info] connection_edge_process_relay_cell(): data cell dropped, unknown stream.
(about 30 times in a row on [Info] verbosity.
I've attached 2 logs. One at [Info] and one at [Debug]. In both cases, Tor was started through Vidalia.
After the onion went green (Tor was connected) I waited some seconds and tried to open blog.fefe.de in
Firefox (Fefes Blog was chosen because it consists of one large html page without pictures - beside the favicon).
Last time this problem occurred I had to do a clean reinstall of the Vidalia Bundle to make it disappear.
The problem occurred with different versions of the 2.1.x branch.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: knappo
https://gitlab.torproject.org/legacy/trac/-/issues/913
panther compile warnings 0.2.1.11-alpha
2020-06-13T14:01:10Z
Roger Dingledine
panther compile warnings 0.2.1.11-alpha
In file included from container.c:14:
compat.h:257: warning: duplicate `const'
The line in question is DECLARE_CTYPE_FN()
Perhaps it is looking at this?
extern const uint32_t const TOR_##name##_TABLE[];
[Automatically added by flyspr...
In file included from container.c:14:
compat.h:257: warning: duplicate `const'
The line in question is DECLARE_CTYPE_FN()
Perhaps it is looking at this?
extern const uint32_t const TOR_##name##_TABLE[];
[Automatically added by flyspray2trac: Operating System: OSX 10.3 Panther]
Nick Mathewson
Nick Mathewson
https://gitlab.torproject.org/legacy/trac/-/issues/914
When the clock jumps, Tor will trigger CIRCUIT_ESTABLISHED
2009-01-31T11:09:16Z
Steven Murdoch
When the clock jumps, Tor will trigger CIRCUIT_ESTABLISHED
When Tor detects that the clock has jumped, it will destroy
existing circuits and create new ones (or/circuitbuild.c:737).
Once Tor has created new circuits, it will trigger the same
events as would happen if Tor had established its fir...
When Tor detects that the clock has jumped, it will destroy
existing circuits and create new ones (or/circuitbuild.c:737).
Once Tor has created new circuits, it will trigger the same
events as would happen if Tor had established its first
circuit, including sending the CIRCUIT_ESTABLISHED control event
and BOOTSTRAP_STATUS_DONE bootstrap event (or/circuitbuild.c:682)
Vidalia/Tor Browser Bundle uses CIRCUIT_ESTABLISHED to launch Firefox
and Pidgin. So when this scenario occurs, there will the two
instances running. This would be confusing to users.
I'm not sure whether this is best fixed in Vidalia or Tor.
The specification on CIRCUIT_ESTABLISHED is not very clear on
whether it should be generated multiple times.
"Tor is able to establish circuits for client use. This event will
only be sent if we just built a circuit that changed our mind --
that is, prior to this event we didn't know whether we could
establish circuits."
Proposal 137 indicates that currently Tor does not send BOOTSTRAP_STATUS_DONE
more than once (although "monotonically" could be interpreted as
monotonically non-decreasing rather than monotonically increasing.
"Current Tor versions enter these phases in order, monotonically;
future Tors MAY revisit earlier stages."
[Automatically added by flyspray2trac: Operating System: All]
Steven Murdoch
Steven Murdoch
https://gitlab.torproject.org/legacy/trac/-/issues/915
Directory authority retries parsing incorrect vote infinitely
2020-06-13T14:01:11Z
Karsten Loesing
Directory authority retries parsing incorrect vote infinitely
This morning, I found gabelmoo filling its logs with these warnings
(info-level logs only included where it seemed useful):
Jan 22 11:19:46.397 [notice] Tor 0.2.1.11-alpha (r18193) opening log file.
[...]
Jan 23 01:50:01.080 [notice] Ti...
This morning, I found gabelmoo filling its logs with these warnings
(info-level logs only included where it seemed useful):
Jan 22 11:19:46.397 [notice] Tor 0.2.1.11-alpha (r18193) opening log file.
[...]
Jan 23 01:50:01.080 [notice] Time to vote.
Jan 23 01:50:01.108 [notice] Choosing valid-after time in vote as 2009-01-23 01:00:00:
consensus_set=1, last_interval=3600
Jan 23 01:50:01.359 [notice] Vote posted.
Jan 23 01:50:19.559 [warn] Got a vote from an authority (nickname rgnx, address
208.83.223.34) with authority key ID 0F06AD141
ABB617AEA5A51663BB2F295DCB13521. This key ID is not recognized. Known v3 key IDs are: E2A2AF570166665D738736D0DD58169CC61D8A8B, 14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4, E8A9C45EDE6D711294FADF8E7951F4DE6CA56B58, 27B6B5996C426270A5C95488AA5BCEB6BCC86956, 81349FC1F2DBA2C2C11B45CB9706637D480AB913, 585769C78764D58426B8B52B6651A5A71137189A
Jan 23 01:50:59.743 [notice] Uploaded a vote to dirserver 80.190.246.100:80
Jan 23 01:50:59.866 [notice] Uploaded a vote to dirserver 194.109.206.212:80
Jan 23 01:51:00.072 [notice] Uploaded a vote to dirserver 128.31.0.34:9031
Jan 23 01:51:00.161 [notice] Uploaded a vote to dirserver 216.224.124.114:9030
Jan 23 01:51:12.885 [notice] Uploaded a vote to dirserver 86.59.21.38:80
Jan 23 01:52:31.246 [notice] Time to fetch any votes that we're missing.
Jan 23 01:52:31.246 [notice] We're missing votes from 2 authorities. Asking every other
authority for a copy.
Jan 23 01:52:31.452 [info] connection_dir_client_reached_eof(): Got votes (size 913169)
from server 86.59.21.38:80
Jan 23 01:52:31.508 [warn] Error decoding descriptor digest "UpcKF+KfBAgnHr+IyNP009-01-2"
Jan 23 01:52:31.522 [warn] Error reading network-status vote: signature does not match.
Jan 23 01:52:31.524 [warn] Couldn't parse vote: length was 457268
Jan 23 01:52:31.533 [warn] Error decoding descriptor digest "UpcKF+KfBAgnHr+IyNP009-01-2"
Jan 23 01:52:31.547 [warn] Error reading network-status vote: signature does not match.
Jan 23 01:52:31.548 [warn] Couldn't parse vote: length was 457268
Jan 23 01:52:31.557 [warn] Error decoding descriptor digest "UpcKF+KfBAgnHr+IyNP009-01-2"
Jan 23 01:52:31.571 [warn] Error reading network-status vote: signature does not match.
Jan 23 01:52:31.572 [warn] Couldn't parse vote: length was 457268
[...]
Jan 23 12:03:23.635 [warn] Error decoding descriptor digest "UpcKF+KfBAgnHr+IyNP009-01-2"
Jan 23 12:03:23.648 [warn] Error reading network-status vote: signature does not match.
Jan 23 12:03:23.650 [warn] Couldn't parse vote: length was 457268
This problem recurred at a rate of about 42 times per second (!) until I
killed it at 12:03. gabelmoo was unresponsive at that time: Tor weather
reported it couldn't ping it, gabelmoo didn't vote, and the Tor process had
to be killed with -9.
In the last votes that gabelmoo wrote (at 00:55), there is the correct line
that probably should have been parsed:
r Unnamed St3/Fe5maZRmmctLe/Mh9jU0rYk UpcKF+KfBAgnHr+IyNPOYbOzMCA 2009-01-22 13:10:15
99.21.76.207 9001 9030
The first question is where the ten characters # in
"UpcKF+KfBAgnHr+IyNP##########009-01-2" went missing.
The second, and more important question is why gabelmoo tries to re-parse
the incorrect vote over and over again.
[Automatically added by flyspray2trac: Operating System: Other Linux]
https://gitlab.torproject.org/legacy/trac/-/issues/916
0.2.0.33 doesn't compile on FC8 64-bit
2020-06-13T14:01:11Z
Roger Dingledine
0.2.0.33 doesn't compile on FC8 64-bit
Reported by John Thompson:
It won't compile for me here (Fedora8 64bit). tor-0.2.32 compiled fine,
however, and 0.2.0.33 built fine on my NetBSD box. See attached log.
In file included from buffers.c:17:
or.h: In function 'TO_OR_CONN'...
Reported by John Thompson:
It won't compile for me here (Fedora8 64bit). tor-0.2.32 compiled fine,
however, and 0.2.0.33 built fine on my NetBSD box. See attached log.
In file included from buffers.c:17:
or.h: In function 'TO_OR_CONN':
or.h:1102: warning: implicit declaration of function 'log'
or.h:1102: warning: incompatible implicit declaration of built-in function 'log'
or.h:1102: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1102: error: (Each undeclared identifier is reported only once
or.h:1102: error: for each function it appears in.)
or.h:1102: error: 'LD_BUG' undeclared (first use in this function)
or.h:1102: error: too many arguments to function 'log'
or.h: In function 'TO_DIR_CONN':
or.h:1107: warning: incompatible implicit declaration of built-in function 'log'
or.h:1107: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1107: error: 'LD_BUG' undeclared (first use in this function)
or.h:1107: error: too many arguments to function 'log'
or.h: In function 'TO_EDGE_CONN':
or.h:1112: warning: incompatible implicit declaration of built-in function 'log'
or.h:1112: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1112: error: 'LD_BUG' undeclared (first use in this function)
or.h:1112: error: too many arguments to function 'log'
or.h: In function 'TO_CONTROL_CONN':
or.h:1117: warning: incompatible implicit declaration of built-in function 'log'
or.h:1117: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1117: error: 'LD_BUG' undeclared (first use in this function)
or.h:1117: error: too many arguments to function 'log'
or.h: In function 'TO_OR_CIRCUIT':
or.h:1945: warning: incompatible implicit declaration of built-in function 'log'
or.h:1945: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1945: error: 'LD_BUG' undeclared (first use in this function)
or.h:1945: error: too many arguments to function 'log'
or.h: In function 'TO_ORIGIN_CIRCUIT':
or.h:1950: warning: incompatible implicit declaration of built-in function 'log'
or.h:1950: error: 'LOG_ERR' undeclared (first use in this function)
or.h:1950: error: 'LD_BUG' undeclared (first use in this function)
or.h:1950: error: too many arguments to function 'log'
buffers.c: In function 'chunk_new_with_alloc_size':
buffers.c:174: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:174: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:174: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:174: error: too many arguments to function 'log'
buffers.c: In function 'chunk_grow':
buffers.c:226: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:226: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:226: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:226: error: too many arguments to function 'log'
buffers.c: In function 'buf_shrink_freelists':
buffers.c:271: warning: implicit declaration of function 'log_info'
buffers.c:271: error: 'LD_MM' undeclared (first use in this function)
buffers.c:275: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:275: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:275: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:275: error: too many arguments to function 'log'
buffers.c:288: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:288: error: too many arguments to function 'log'
buffers.c: In function 'buf_dump_freelist_sizes':
buffers.c:306: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:306: error: 'LD_MM' undeclared (first use in this function)
buffers.c:306: error: too many arguments to function 'log'
buffers.c:317: error: too many arguments to function 'log'
buffers.c:320: error: too many arguments to function 'log'
buffers.c: In function 'buf_pullup':
buffers.c:373: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:373: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:373: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:373: error: too many arguments to function 'log'
buffers.c:381: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:381: error: too many arguments to function 'log'
buffers.c:393: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:393: error: too many arguments to function 'log'
buffers.c:406: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:406: error: too many arguments to function 'log'
buffers.c:411: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:411: error: too many arguments to function 'log'
buffers.c: In function 'buf_remove_from_front':
buffers.c:431: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:431: error: 'LOG_ERR' undeclared (first use in this function)
buffers.c:431: error: 'LD_BUG' undeclared (first use in this function)
buffers.c:431: error: too many arguments to function 'log'
buffers.c:433: warning: incompatible implicit declaration of built-in function '
log'
buffers.c:433: error: too many arguments to function 'log'
...
[Automatically added by flyspray2trac: Operating System: Fedora Core Linux]
0.2.1.x-final
Nick Mathewson
Nick Mathewson
https://gitlab.torproject.org/legacy/trac/-/issues/917
Nameserver probes can give strange results
2020-06-13T14:01:12Z
Nick Mathewson
Nameserver probes can give strange results
We should not actually retry nameserver probes, nor should we _ever_ reattach them to a new nameserver after
clear and resume.
Fortunately, the worst that happens here now is that we erroneously mark a down nameserver as up, retry it,
...
We should not actually retry nameserver probes, nor should we _ever_ reattach them to a new nameserver after
clear and resume.
Fortunately, the worst that happens here now is that we erroneously mark a down nameserver as up, retry it,
fail, and mark it down again. Still, that's pretty ugly.
[Automatically added by flyspray2trac: Operating System: All]
post 0.2.1.x
https://gitlab.torproject.org/legacy/trac/-/issues/918
bind to port 443 + wake from hibernation = exit
2020-06-13T14:01:13Z
Roger Dingledine
bind to port 443 + wake from hibernation = exit
<ioerror> Jan 28 22:05:50.644 [notice] Opening OR listener on 80.68.85.45:443
<ioerror> Jan 28 22:05:50.644 [warn] Could not bind to 80.68.85.45:443:
+Permission denied
<ioerror> Jan 28 22:05:50.645 [warn] Failed to parse/validate config...
<ioerror> Jan 28 22:05:50.644 [notice] Opening OR listener on 80.68.85.45:443
<ioerror> Jan 28 22:05:50.644 [warn] Could not bind to 80.68.85.45:443:
+Permission denied
<ioerror> Jan 28 22:05:50.645 [warn] Failed to parse/validate config: Failed
+to bind one of the listener ports.
Basically if you bind to port 443 directly, and then drop privs, that's fine.
When you hup, Tor will (should) correctly decide to leave that port alone since
it hasn't changed and it wouldn't be able to bind it again anyway.
But when we hibernate, and then come back, we can't bind it. Currently we die.
Option one, never close it in this case. Not great, since we want to be hibernating,
but not awful.
Option two, keep a separate root process around that can jumpstart Tor again. Ugh.
Option three, warn if this configuration is used, so the user can at least know.
How do we auto detect that it's a privileged port? Just "port < 1024"?
[Automatically added by flyspray2trac: Operating System: All]
Tor: unspecified
https://gitlab.torproject.org/legacy/trac/-/issues/919
If you hup tor while it's hibernating, it rebinds its ports
2020-06-13T14:01:13Z
Roger Dingledine
If you hup tor while it's hibernating, it rebinds its ports
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 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-final
https://gitlab.torproject.org/legacy/trac/-/issues/920
don't bundle libevent with Tor
2020-06-13T14:01:14Z
Trac
don't bundle libevent with Tor
Hi,
I am the maintainer of Tor in Gentoo Linux and we have an open report in our issues tracker: http://bugs.gentoo.org/show_bug.cgi?id=206969
The report states that the asynchronous DNS part of libevent is bundled with Tor, which is t...
Hi,
I am the maintainer of Tor in Gentoo Linux and we have an open report in our issues tracker: http://bugs.gentoo.org/show_bug.cgi?id=206969
The report states that the asynchronous DNS part of libevent is bundled with Tor, which is true (see src/or/evendns.{c,h}). This gives our security team and myself a headache as a security problem found in libevent has to be tracked in all messages that bundle it or just only parts. Please remove that bit and try to bring your modifications upstream to libevent if needed.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: V-Li
post 0.2.1.x
https://gitlab.torproject.org/legacy/trac/-/issues/921
clients avoid *all* authority types when avoiding any
2020-06-13T14:01:14Z
Roger Dingledine
clients avoid *all* authority types when avoiding any
Clients doing directory fetches avoid authorities of all types when trying
to avoid authorities of any type. So a client asking for a v3 consensus will
never ask moria2, because moria2 is an authority of some type. Similarly,
caches want...
Clients doing directory fetches avoid authorities of all types when trying
to avoid authorities of any type. So a client asking for a v3 consensus will
never ask moria2, because moria2 is an authority of some type. Similarly,
caches wanting a v3 consensus won't ask moria2, because it's not a v3
authority. Same goes for Tonga, our bridge authority.
See
is_trusted = router_digest_is_trusted_dir(status->identity_digest);
in router_pick_directory_server_impl() in routerlist.c
We should instead ask if it's a trusted dir for the type of authority
we're wondering about.
[Automatically added by flyspray2trac: Operating System: All]
post 0.2.1.x
https://gitlab.torproject.org/legacy/trac/-/issues/922
Problem upgrading to Tor stable Version 0.2.0.33
2020-06-13T14:01:14Z
Trac
Problem upgrading to Tor stable Version 0.2.0.33
I need some assistance please. I am a basic computer user but I have been
able to install Tor which I have been using daily for months now. My OS is
MacOsx Panther 10.3.9 and the Tor bundle installed is 0.2.0.31. The OS is
being operat...
I need some assistance please. I am a basic computer user but I have been
able to install Tor which I have been using daily for months now. My OS is
MacOsx Panther 10.3.9 and the Tor bundle installed is 0.2.0.31. The OS is
being operated from an external HD.
I am no longer able to upgrade to the latest Tor versions (0.2.0.33) because
as soon as I open the installer package of the new version I get the error
message:
The Installer package "vidalia-bundle - 0.2.0.33-0.10-ppc" cannot be
opened.
The Bill of Materials for this package was not found.
I have tried several times with the same result. I have tried
deleting the previous Tor, Privoxy and Vidalia (0.2.0.31) before
I install the new version but I still get the error message.In
another Tor forum I was advised to report this as a possible bug.
I have always upgraded to new stable versions of Tor this way.
The install.log shows only:
Feb 5 08:08:25 localhost : Vidalia - Tor - Privoxy - Torbutton Bundle Installation Log
Feb 5 08:08:25 localhost : Opened from: /Volumes/vidalia-bundle-0.2.0.33-0.1.10-ppc/vidalia-bundle-0.2.0.33-0.1.10-ppc.mpkg
Feb 5 08:08:25 localhost : Hardware Model: PowerMac6,4 @ 1249 MHz, 1024 MB
Feb 5 08:08:25 localhost : Running OS Build: 7W98
Feb 5 08:08:25 localhost : Installer Language: English
Thank you
Louis
[Automatically added by flyspray2trac: Operating System: OSX 10.3 Panther]
**Trac**:
**Username**: Louis
Andrew Lewman
Andrew Lewman
https://gitlab.torproject.org/legacy/trac/-/issues/923
Tor software exited unexpectedly
2020-06-13T14:01:15Z
Trac
Tor software exited unexpectedly
Tor does not start
Vadilia detected that the Tor software exited unexpectedly
Error from libevent: evsignal_init: socketpair: No error
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: serba
Tor does not start
Vadilia detected that the Tor software exited unexpectedly
Error from libevent: evsignal_init: socketpair: No error
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: serba
https://gitlab.torproject.org/legacy/trac/-/issues/924
Bundle installer fails: "The Bill of Materials for this package was not found."
2009-02-12T21:14:02Z
Trac
Bundle installer fails: "The Bill of Materials for this package was not found."
I'm having the same problem, on the same OS (MacOSX 10.3.9), reported by
Louis in the blog on January 29, 2009: The bundle installer fails to start,
saying:
The Installer package "vidalia-bundle-0.2.0.34-0.1.10-ppc" cannot be
...
I'm having the same problem, on the same OS (MacOSX 10.3.9), reported by
Louis in the blog on January 29, 2009: The bundle installer fails to start,
saying:
The Installer package "vidalia-bundle-0.2.0.34-0.1.10-ppc" cannot be
opened.
The Bill of Materials for this package was not found.
My current version was installed from
vidalia-bundle-0.2.0.30-0.1.6-panther.dmg.
The reply to Louis's note in the blog asked what /var/log/install.log
showed. Here are the complete entries from two attempts to run the
installer:
Feb 11 01:10:30 localhost : Vidalia - Tor - Privoxy - Torbutton Bundle Installation Log
Feb 11 01:10:30 localhost : Opened from: /Volumes/vidalia-bundle-0.2.0.34-0.1.10-ppc/vidalia-bundle-0.2.0.34-0.1.10-ppc.mpkg
Feb 11 01:10:30 localhost : Hardware Model: PowerMac4,4 @ 999 MHz, 768 MB
Feb 11 01:10:30 localhost : Running OS Build: 7W98
Feb 11 01:10:30 localhost : Installer Language: English
Feb 11 01:11:12 localhost : Vidalia - Tor - Privoxy - Torbutton Bundle Installation Log
Feb 11 01:11:12 localhost : Opened from: /Volumes/vidalia-bundle-0.2.0.34-0.1.10-ppc/vidalia-bundle-0.2.0.34-0.1.10-ppc.mpkg
Feb 11 01:11:12 localhost : Hardware Model: PowerMac4,4 @ 999 MHz, 768 MB
Feb 11 01:11:12 localhost : Running OS Build: 7W98
Feb 11 01:11:12 localhost : Installer Language: English
Here is Louis's original note:
Re: Installation latest version of Tor
On January 29th, 2009 Louis (not verified) said:
I need some assistance please. I am a basic computer user but I have
been able to install Tor which I have been using daily for months now.
My OS is MacOsx Panther 10.3.9 and the Tor bundle installed is 0.2.0.31.
The OS is being operated from an external HD.
I am no longer able to upgrade to the latest Tor versions (0.2.0.33)
because as soon as I open the installer package of the new version I get
the error message:
The Installer package "vidalia-bundle - 0.2.0.33-0.10-ppc" cannot be
opened.
The Bill of Materials for this package was not found.
I have tried several times with the same result. I have tried moving the
old Tor, Privoxy and Vidalia folders to the trash but I still get the error
message!. Am I doing something wrong? I have always upgraded to
new stable versions of Tor this way.
Thank you in advance for your help.
Louis
[Automatically added by flyspray2trac: Operating System: OSX 10.3 Panther]
**Trac**:
**Username**: torpor
Andrew Lewman
Andrew Lewman
https://gitlab.torproject.org/legacy/trac/-/issues/925
Tor fails badly when accept(2) returns EMFILE or ENFILE
2020-06-13T14:01:16Z
riastradh
Tor fails badly when accept(2) returns EMFILE or ENFILE
If accept(2) in connection_handle_listener_read returns EMFILE or
ENFILE, Tor logs a failure and returns to the event loop. The
listening socket remains ready for reading, however, so that Tor again
tries to accept a connection. This l...
If accept(2) in connection_handle_listener_read returns EMFILE or
ENFILE, Tor logs a failure and returns to the event loop. The
listening socket remains ready for reading, however, so that Tor again
tries to accept a connection. This leads to tens of thousands of
logged failures per second. Here is an excerpt from my syslog:
Feb 11 05:57:36 Tor[20415]: accept failed: Too many open files. Dropping incoming connection.
Feb 11 05:57:54 last message repeated 301536 times
Feb 11 05:57:54 Tor[20415]: Failing because we have 1765 connections already. Please raise your ulimit -n.
Feb 11 05:57:54 Tor[20415]: accept failed: Too many open files. Dropping incoming connection.
Feb 11 05:58:05 last message repeated 184158 times
Feb 11 05:58:05 Tor[20415]: Failing because we have 1765 connections already. Please raise your ulimit -n.
Feb 11 05:58:05 Tor[20415]: accept failed: Too many open files. Dropping incoming connection.
Feb 11 05:58:13 last message repeated 127556 times
Feb 11 05:58:13 Tor[20415]: Failing because we have 1765 connections already. Please raise your ulimit -n.
Feb 11 05:58:13 Tor[20415]: accept failed: Too many open files. Dropping incoming connection.
Feb 11 05:58:26 last message repeated 223556 times
Feb 11 05:58:26 Tor[20415]: Failing because we have 1765 connections already. Please raise your ulimit -n.
I don't know what the right thing to do here is, but spiking the CPU
and spraying log messages is not a very graceful mode of failure. One
way to mitigate the damage might be to close the listening socket,
which I believe won't be reopened until a minute later. This is no
worse for the Tor network than just wedging, and perhaps better, since
prospective connectors would be refused rather than silently forgotten
in a flurry of furious logging.
Also, it would be nice to document the number of file descriptors
generally required by a Tor relay, or a formula for computing it. For
example, is it proportional to the bandwidth and to the number of
relays in the Tor network? Or to the bandwidth and to the number of
users in the Tor network? This way, prospective operators of Tor
relays would not need to repeatedly restart their relays as they test
incremental bumps in the file descriptor ulimits, unless there is some
way to bump them without restarting the relay (but I doubt whether
there is).
(Apologies if this is duplicated: I hit !^A while editing this, in order
to move to the beginning of the line, but the obnoxious !@#!^%&%!^& web
form [and my obnoxiously colluding web browser] interpreted it to mean
something else for which I quickly hit the stop button. I don't know
what hitting !^A actually did.)
[Automatically added by flyspray2trac: Operating System: All]
Tor: unspecified
https://gitlab.torproject.org/legacy/trac/-/issues/926
Torbutton gives FILE_ACCESS_DENIED error on activation
2009-02-20T02:58:12Z
Trac
Torbutton gives FILE_ACCESS_DENIED error on activation
hi, i loaded up tor then Firefox then when i clicked on the tor button this message cam up (the link for it is below), thanks.
http://img252.imageshack.us/my.php?image=51553242sk8.png
[Automatically added by flyspray2trac: Operating Sy...
hi, i loaded up tor then Firefox then when i clicked on the tor button this message cam up (the link for it is below), thanks.
http://img252.imageshack.us/my.php?image=51553242sk8.png
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: squid_poo
https://gitlab.torproject.org/legacy/trac/-/issues/927
Tor silently dies since v0.2.0.33
2020-06-13T14:01:16Z
Trac
Tor silently dies since v0.2.0.33
Tor worked just fine for ages, but unfortunately v0.2.0.32 was last version to work at all.
After upgrading to v0.2.0.33 and later to v0.2.0.34 tor just silently dies. So i forced to roll back to v0.2.0.32
All versions was installed as ...
Tor worked just fine for ages, but unfortunately v0.2.0.32 was last version to work at all.
After upgrading to v0.2.0.33 and later to v0.2.0.34 tor just silently dies. So i forced to roll back to v0.2.0.32
All versions was installed as vidalia bundle on Windows 2000 Service Pack 4 server. Application log shows nothing about tor.
And tor own log dosn't help either. Below is two tor versions outputs, started from cmd line, so bundle config is not used.
v0.2.0.32 :
16:29:12
%%>>>H:\WinApp\TOR\Tor\tor
Feb 15 16:29:20.139 [notice] Tor v0.2.0.32 (r17346). This is experimental softwa
re. Do not rely on it for strong anonymity. (Running on Windows 2000 Service Pac
k 4 [server] {enterprise})
Feb 15 16:29:20.239 [notice] Configuration file "G:\Documents and Settings\Admin
istrator\Application Data\tor\torrc" not present, using reasonable defaults.
Feb 15 16:29:20.259 [notice] Initialized libevent version 1.4.7-stable using met
hod win32. Good.
Feb 15 16:29:20.259 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 15 16:29:22.342 [warn] Please upgrade! This version of Tor (0.2.0.32) is obs
olete, according to the directory authorities. Recommended versions are: 0.2.0.3
3,0.2.0.34,0.2.1.11-alpha,0.2.1.12-alpha
Feb 15 16:29:25.236 [notice] We now have enough directory information to build c
ircuits.
Feb 15 16:29:30.974 [notice] Tor has successfully opened a circuit. Looks like c
lient functionality is working.
v0.2.0.32 :
16:30:10
%%>>>H:\WinApp\TOR\Tor\tor
Feb 15 16:31:07.153 [notice] Tor v0.2.0.34 (r18423). This is experimental softwa
re. Do not rely on it for strong anonymity. (Running on Windows 2000 Service Pac
k 4 [server] {enterprise})
Feb 15 16:31:07.243 [notice] Configuration file "G:\Documents and Settings\Admin
istrator\Application Data\tor\torrc" not present, using reasonable defaults.
Feb 15 16:31:07.293 [notice] Initialized libevent version 1.4.9-stable using met
hod win32. Good.
Feb 15 16:31:07.293 [notice] Opening Socks listener on 127.0.0.1:9050
16:31:08
%%>>>H:\WinApp\TOR\Tor\
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: Pheamaph
https://gitlab.torproject.org/legacy/trac/-/issues/928
With BridgeRelay 1 and ORPort 0, things go bad
2020-06-13T14:01:17Z
Roger Dingledine
With BridgeRelay 1 and ORPort 0, things go bad
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...
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-final
https://gitlab.torproject.org/legacy/trac/-/issues/929
FAILURE to event_del (ev=0x9376e48) at event.c:806
2020-06-13T14:01:19Z
Trac
FAILURE to event_del (ev=0x9376e48) at event.c:806
Feb 21 08:50:09.922 [notice] Tor v0.2.1.12-alpha-dev (r18582).
Crash on failure with event_del (event.c 806) involvement.
# gdb /usr/bin/tor /var/lib/tor/data/core.25599
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
L...
Feb 21 08:50:09.922 [notice] Tor v0.2.1.12-alpha-dev (r18582).
Crash on failure with event_del (event.c 806) involvement.
# gdb /usr/bin/tor /var/lib/tor/data/core.25599
GNU gdb 6.8
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 "i686-pc-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.4.so.2...done.
Loaded symbols for /usr/lib/libevent-1.4.so.2
Reading symbols from /usr/lib/libssl.so.0.9.8...done.
Loaded symbols for /usr/lib/libssl.so.0.9.8
Reading symbols from /usr/lib/libcrypto.so.0.9.8...done.
Loaded symbols for /usr/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.so.2...done.
Loaded symbols for /lib/ld-linux.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
Core was generated by `/usr/bin/tor --runasdaemon 1'.
Program terminated with signal 11, Segmentation fault.
[New process 25599]
[New process 25612]
#0 event_del (ev=0x9376e48) at event.c:806
806 event.c: No such file or directory.
in event.c
(gdb) bt
#0 event_del (ev=0x9376e48) at event.c:806
#1 0x080e2741 in request_finished (req=0x9376e10, head=<value optimized out>) at eventdns.c:616
#2 0xb7ea53ce in event_base_loop (base=0x81430a0, flags=0) at event.c:387
#3 0xb7ea55b4 in event_loop (flags=0) at event.c:463
#4 0x080a9d75 in do_main_loop () at main.c:1435
#5 0x080aa00f in tor_main (argc=3, argv=0xbfe03114) at main.c:2060
#6 0x080e650e in main (argc=Cannot access memory at address 0x1b
) at tor_main.c:30
(gdb)
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: xiando
0.2.1.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/930
router_parse_entry_from_string (s=0x135 <Address 0x135 out of bounds>
2020-06-13T14:01:22Z
Andrew Lewman
router_parse_entry_from_string (s=0x135 <Address 0x135 out of bounds>
gdb bt below. tor 0.2.0.34-stable does not have this issue.
Feb 22 18:48:53.906 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fab760756e0 (LWP 18369)]
0x00007f...
gdb bt below. tor 0.2.0.34-stable does not have this issue.
Feb 22 18:48:53.906 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fab760756e0 (LWP 18369)]
0x00007fab74d11015 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00007fab74d11015 in raise () from /lib/libc.so.6
#1 0x00007fab74d12b83 in abort () from /lib/libc.so.6
#2 0x00007fab74d57a80 in ?? () from /lib/libc.so.6
#3 0x00000000004ad39d in memarea_drop_all (area=0x21a47f0) at memarea.c:102
#4 0x0000000000493c64 in router_parse_entry_from_string (s=0x135 <Address 0x135 out of bounds>, end=0x9a8 <Address 0x9a8 out of bounds>, cache_copy=1,
allow_annotations=295, prepend_annotations=0x135 <Address 0x135 out of bounds>) at routerparse.c:1438
#5 0x0000000000494eb4 in router_parse_list_from_string (s=0x7fff7e093e38, eos=0x7fab75ec6357 "", dest=0x21ecb10, saved_location=SAVED_NOWHERE,
want_extrainfo=0, allow_annotations=0, prepend_annotations=0x7fff7e093f70 "@downloaded-at 2009-02-22 23:48:56\n@source \"194.105.99.31\"\n")
at routerparse.c:1061
#6 0x000000000048cf05 in router_load_routers_from_string (
s=0x7fab75ebc614 "router che 81.233.224.95 443 0 80\nplatform Tor 0.2.0.33 (r18212) on Linux i686\nopt protocols Link 1 2 Circuit 1\npublished 2009-02-22 21:26:03\nopt fingerprint D5F2 C65F 4131 A146 8D5B 67A8 838A 9B7E D8"..., eos=0x0, saved_location=SAVED_NOWHERE, requested_fingerprints=0x2264440,
descriptor_digests=1, prepend_annotations=0x7fff7e093f70 "@downloaded-at 2009-02-22 23:48:56\n@source \"194.105.99.31\"\n") at routerlist.c:3500
#7 0x0000000000447b16 in connection_dir_client_reached_eof (conn=0x21a9440) at directory.c:1376
#8 0x00000000004486de in connection_dir_reached_eof (conn=0x21a9440) at directory.c:2041
#9 0x000000000042bde8 in connection_handle_read (conn=0x21a9440) at connection.c:2909
#10 0x0000000000461bc0 in conn_read_callback (fd=<value optimized out>, event=<value optimized out>, _conn=<value optimized out>) at main.c:456
#11 0x00007fab75a4e67d in event_base_loop () from /usr/lib/libevent-1.3e.so.1
#12 0x00000000004617a6 in do_main_loop () at main.c:1435
#13 0x00000000004619f5 in tor_main (argc=1, argv=<value optimized out>) at main.c:2060
#14 0x00007fab74cfc466 in __libc_start_main () from /lib/libc.so.6
#15 0x0000000000407469 in _start ()
[Automatically added by flyspray2trac: Operating System: Other Linux]
0.2.1.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/931
Socks Options in Torbutton 1.2 missed!
2009-03-13T07:34:16Z
Trac
Socks Options in Torbutton 1.2 missed!
On my Sytsem, the only way to use Privoxy and tor is to use SOCKS v4.
But Torbutton uses SOCKS v5 Option, and there is no way to change it to SOCKS v4.
Please add this possiblity in further versions of torbutton, so that I can use it to...
On my Sytsem, the only way to use Privoxy and tor is to use SOCKS v4.
But Torbutton uses SOCKS v5 Option, and there is no way to change it to SOCKS v4.
Please add this possiblity in further versions of torbutton, so that I can use it to.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Georgee
https://gitlab.torproject.org/legacy/trac/-/issues/932
Bridges report unbelievable numbers of clients
2020-06-13T14:01:23Z
Karsten Loesing
Bridges report unbelievable numbers of clients
During the evaluation of extra-info documents published by bridges it was
found that some bridges report unbelievable numbers of clients. As an
example, two subsequently published extra-info documents of the same bridge
look are as follo...
During the evaluation of extra-info documents published by bridges it was
found that some bridges report unbelievable numbers of clients. As an
example, two subsequently published extra-info documents of the same bridge
look are as follows (* denotes removed parts). Here, the first extra-info
document is the first such document that was published by this bridge.
extra-info *
published 2008-10-28 17:20:32
geoip-start-time 2008-10-25 23:07:16
geoip-client-origins de=936,us=704,cn=664,it=288,fr=208,ru=192,gb=144,*
extra-info *
published 2008-10-29 09:20:33
geoip-start-time 2008-10-27 09:07:01
geoip-client-origins ae=8,bg=8,cn=8,cz=8,de=8,dk=8,es=8,hk=8,in=8,it=8,*
The same bridge was running as a relay before 2008-10-28 with the last
router descriptor published at around 2008-10-27 14:00:00.
A possible (and even likely) explanation for the high numbers of clients is
that these clients contacted the bridge back when it was running as a
relay. When being reconfigured to run as a bridge, the bridge did not clear
its geoip cache and counted the relay clients as bridge clients. Only when
clearing the cache on 2008-10-27 09:07:01, the relay clients were removed
from the cache.
A solution to the described problem is that bridges do not include geoip
information in their extra-info documents if they have published a router
descriptor within the past few days, e.g., 3 days. These 3 (or whatever
fits here) days ensure that clients do not know about the bridge as a relay
anymore, but only as a bridge. This prevents both overcounting and
unwantedly revealing information about relay usage.
There is another phenomenon of a bridge that publishes both router
descriptors and bridge descriptors at the same time. In fact, it's not
forbidden to set 'PublishServerDescriptor v2,v3,bridge'. However, this
defeats the point of counting only bridge clients and including them in
extra-info documents. Should this behavior be changed, so that nodes can
publish either router descriptors or bridge descriptors, but not both?
[Automatically added by flyspray2trac: Operating System: All]
0.2.1.x-final
Karsten Loesing
Karsten Loesing
https://gitlab.torproject.org/legacy/trac/-/issues/933
MapAddress for domains?
2020-06-13T14:01:24Z
Trac
MapAddress for domains?
Would it be non-trivial to have the MapAddress option behave like TrackHostExits? That is, if an entry is like
MapAddress .rapidshare.com .rapidshare.com.exitpoint.exit
have it applied to rs1xx.rapidshare.com, rs223dt.rapidshare.com, rs...
Would it be non-trivial to have the MapAddress option behave like TrackHostExits? That is, if an entry is like
MapAddress .rapidshare.com .rapidshare.com.exitpoint.exit
have it applied to rs1xx.rapidshare.com, rs223dt.rapidshare.com, rs28tl2.rapidshare.com...
I already have such a line in my TORRC file; on start Tor doesn't complain, but apparently that line doesn't have any
effect.
My goal is to have all connections to rapidshare.com exit through the same exit point (that I've already defined with
a separate MapAddress line for rapidshare.com), regardless if I'm redirected.
The alternative would be to add 5000-odd MapAddress lines specifying every possible hostname given Rapidshare's
current naming convention (rs[None..None](../compare/None...None)+[a-z]+[None..None](../compare/None...None)?.rapidshare.com) , but I don't know how Tor would handle such a big
config file; my connections drop (flaky company proxy) often enough already...
I already have TrackHostExits enabled for both rapidshare.com and .rapidshare.com, so when rapidshare.com redirects
me to whatever.rapidshare.com Tor will reuse the existing circuit.
If the connection drops halfway, my download manager will remember having been redirected and will retry on
whatever.rapidshare.com. However, if it takes more than TrackHostExitsExpire seconds, Tor will assign this stream to
a new circuit with a different exit point (and Rapidshare will claim I've shared my account and lock it... T_T ).
Thanks for your consideration.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Aleph0
Tor: 0.2.3.x-final
Robert Hogan
Robert Hogan
https://gitlab.torproject.org/legacy/trac/-/issues/934
"Prevent session store from saving Tor loaded tabs" incorrect behaviour
2009-03-02T12:32:11Z
Trac
"Prevent session store from saving Tor loaded tabs" incorrect behaviour
When option "Prevent session store from saving Tor loaded tabs" is disabled, sessions does not restore at browser restart. And "Recently Closed Tabs" menu items does not shown.
Tor was disabled, non-tor sessions does not restore.
To repr...
When option "Prevent session store from saving Tor loaded tabs" is disabled, sessions does not restore at browser restart. And "Recently Closed Tabs" menu items does not shown.
Tor was disabled, non-tor sessions does not restore.
To reproduce bug: "Restore Defaults", then turn off "Prevent session store from saving Tor loaded tabs". Mozilla Firefox 3.0.6. Torbutton 1.2.0.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Shoorick
https://gitlab.torproject.org/legacy/trac/-/issues/935
"Restore Defaults" clean up normal (non-tor) browser settings
2018-03-10T14:47:38Z
Trac
"Restore Defaults" clean up normal (non-tor) browser settings
"Restore Defaults" clean up normal (non-tor) browser settings: proxy and content prefered language.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Shoorick
"Restore Defaults" clean up normal (non-tor) browser settings: proxy and content prefered language.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Shoorick
https://gitlab.torproject.org/legacy/trac/-/issues/936
Race in picking connections for create cell
2020-06-13T14:01:25Z
Roger Dingledine
Race in picking connections for create cell
Reported by lark.
I possible found edge case for doubling conns between two relays, the
one inbound and the one outbound for the node. It's can trigger if conns
launched by relays to each other at the same time, very precisely. Which ca...
Reported by lark.
I possible found edge case for doubling conns between two relays, the
one inbound and the one outbound for the node. It's can trigger if conns
launched by relays to each other at the same time, very precisely. Which can
happens for two relays with high uptime and fast speed, after
TIME_BEFORE_OR_CONN_IS_TOO_OLD.
```
--- connection_or.c.orig Thu Feb 5 00:42:22 2009
+++ connection_or.c Fri Mar 6 19:15:04 2009
-452,7 +452,7 @@
const or_connection_t *b,
int forgive_new_connections)
{
- int newer;
+ int newer, delta, inbound_a, outbound_b, prefer_conn_a;
/** Do not definitively deprecate a new connection with no circuits on it
* until this much time has passed. */
#define NEW_CONN_GRACE_PERIOD (15*60)
-461,15 +461,32 @@
return 0; /* A canonical connection is better than a non-canonical
* one, no matter how new it is or which has circuits. */
- newer = b->_base.timestamp_created < a->_base.timestamp_created;
+ inbound_a = tor_tls_is_server(a->tls);
+ outbound_b = !tor_tls_is_server(b->tls);
+ delta=(int)(a->_base.timestamp_created - b->_base.timestamp_created);
+ newer= delta > 0;
+
+ /* We prefer the "a" conn at equal conditions:
+ *
+ * if "a" is inbound from a node with higher identity key
+ * and created at the same time or later than outbound "b" conn;
+ *
+ * or
+ *
+ * if "a" newer than "b" for any other inbound-outbound
+ * combinations */
+ prefer_conn_a = ((newer && !(inbound_a && outbound_b)) ||
+ (inbound_a && outbound_b && delta >= 0 &&
+ a->circ_id_type == CIRC_ID_TYPE_LOWER));
+
if (
/* We prefer canonical connections regardless of newness. */
(!b->is_canonical && a->is_canonical) ||
/* If both have circuits we prefer the newer: */
- (b->n_circuits && a->n_circuits && newer) ||
+ (b->n_circuits && a->n_circuits && prefer_conn_a) ||
/* If neither has circuits we prefer the newer: */
- (!b->n_circuits && !a->n_circuits && newer))
+ (!b->n_circuits && !a->n_circuits && prefer_conn_a))
return 1;
/* If one has no circuits and the other does... */
```
[Automatically added by flyspray2trac: Operating System: All]
Tor: unspecified
https://gitlab.torproject.org/legacy/trac/-/issues/937
Tor does not support OpenSSL dynamic hardware engines
2020-06-13T14:01:26Z
coderman
Tor does not support OpenSSL dynamic hardware engines
NOTE: fix due in 0.2.2.x.
branch hardware_accel_improvements at git://git.torproject.org/~coderman/git/tor.git
The existing support for crypto acceleration in Tor via the HardwareAccel 1 option is not able to load dynamic engines.
For ...
NOTE: fix due in 0.2.2.x.
branch hardware_accel_improvements at git://git.torproject.org/~coderman/git/tor.git
The existing support for crypto acceleration in Tor via the HardwareAccel 1 option is not able to load dynamic engines.
For example, padlock acceleration with Via processors. See also http://archives.seul.org/or/talk/Dec-2008/msg00314.html
To fix this the src/common/crypto.c should be extended to attempt dynamic engine loading.
NOTE: I have fixed the engine name to "padlock"; robust support for this feature will require a config option
like "HardwareEngineName" or such.
In crypto_global_init():
if (useAccel > 0) {
ENGINE *e = NULL;
log_info(LD_CRYPTO, "Initializing OpenSSL engine support.");
ENGINE_load_builtin_engines();
ENGINE_register_all_complete();
e = ENGINE_by_id ("padlock");
if (!e) {
log_info(LD_CRYPTO, "Trying to load dynamic Padlock OpenSSL engine.");
e = try_load_engine ("padlock");
if (!e) {
log_info(LD_CRYPTO, "Unable to load Padlock OpenSSL engine.");
}
}
if (e) {
log_info(LD_CRYPTO, "Loaded Padlock OpenSSL engine, setting default ciphers.");
ENGINE_set_default (e, ENGINE_METHOD_ALL);
}
}
Where the try_load_engine for dynamic libs is:
/* Try to load a dynamic engine library. */
static ENGINE *
try_load_engine(const char *engine)
{
ENGINE *e = ENGINE_by_id ("dynamic");
if (e)
{
if (!ENGINE_ctrl_cmd_string (e, "SO_PATH", engine, 0)
|| !ENGINE_ctrl_cmd_string (e, "LOAD", NULL, 0))
{
ENGINE_free (e);
e = NULL;
}
}
return e;
}
Depending on VIA processor/stepping this results in:
Mar 08 06:32:00.473 [info] crypto_global_init(): Initializing OpenSSL engine support.
Mar 08 06:32:00.473 [info] crypto_global_init(): Loaded Padlock OpenSSL engine, setting default ciphers.
Mar 08 06:32:00.473 [info] Using default implementation for RSA
Mar 08 06:32:00.473 [info] Using default implementation for DH
Mar 08 06:32:00.473 [info] Using default implementation for RAND
Mar 08 06:32:00.473 [notice] Using OpenSSL engine VIA PadLock: RNG (not used) ACE2 PHE(8192) PMM [padlock] for SHA1
Mar 08 06:32:00.473 [info] Using default implementation for 3DES
Mar 08 06:32:00.473 [notice] Using OpenSSL engine VIA PadLock: RNG (not used) ACE2 PHE(8192) PMM [padlock] for AES
...
[Automatically added by flyspray2trac: Operating System: All]
post 0.2.1.x
coderman
coderman
https://gitlab.torproject.org/legacy/trac/-/issues/938
Outdated localizations
2009-03-09T14:31:51Z
Trac
Outdated localizations
Hi, i'm a member of BabelZilla and i've noticed that though there is a number (8 languages) of translations completed and released there
for TorButton, none of them are included in the latest xpi both on your site and on AMO.
I do under...
Hi, i'm a member of BabelZilla and i've noticed that though there is a number (8 languages) of translations completed and released there
for TorButton, none of them are included in the latest xpi both on your site and on AMO.
I do understand that the localization is not a priority but i hope that you'll find some time
to get the latest files and include them in the xpi on your site at least.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: sonickydon
https://gitlab.torproject.org/legacy/trac/-/issues/939
Our socket count is below zero
2020-06-13T14:01:26Z
Roger Dingledine
Our socket count is below zero
Running moria1 on 0.2.1.12-alpha-dev (r18691), it ran for a few weeks. Then
I !^c'ed it to move to 0.2.1.13-alpha, and its last words were
Mar 09 17:22:50.253 [warn] tor_close_socket(): Bug: Our socket count is below zero: -1. Please su...
Running moria1 on 0.2.1.12-alpha-dev (r18691), it ran for a few weeks. Then
I !^c'ed it to move to 0.2.1.13-alpha, and its last words were
Mar 09 17:22:50.253 [warn] tor_close_socket(): Bug: Our socket count is below zero: -1. Please submit a bug report.
[Automatically added by flyspray2trac: Operating System: All]
https://gitlab.torproject.org/legacy/trac/-/issues/940
Multiple Identity Support
2020-06-15T23:13:00Z
Mike Perry
Multiple Identity Support
Instead of a full toggle, it might be nice to provide the ability for Torbutton to toggle between
multiple identities during Tor usage. Basically, in this case, all cached items, form items,
history navigation, etc would be cleared, an...
Instead of a full toggle, it might be nice to provide the ability for Torbutton to toggle between
multiple identities during Tor usage. Basically, in this case, all cached items, form items,
history navigation, etc would be cleared, and cookies would be restored from a specific jar.
The user could potentially be able to name identities, and have a dropdown menu for switching between
them. It might also be nice to provide the same support for Non-Tor identities, but it should not
be possible to use Tor identities in Non-Tor and vice-versa.
[Automatically added by flyspray2trac: Operating System: All]
https://gitlab.torproject.org/legacy/trac/-/issues/941
circuit event lines sometimes miss verbose names
2020-06-13T14:01:26Z
Roger Dingledine
circuit event lines sometimes miss verbose names
In my Vidalia logs
Mar 12 20:18:31.186 [notice] QtWarningMsg: torcontrol: Improperly formatted
circuit: '16 EXTENDED $5A583B838FDC22246E046E1D4E108F41EFBAD175'
edmanm:#vidalia> those circ events are spec compliant, but they're annoying
...
In my Vidalia logs
Mar 12 20:18:31.186 [notice] QtWarningMsg: torcontrol: Improperly formatted
circuit: '16 EXTENDED $5A583B838FDC22246E046E1D4E108F41EFBAD175'
edmanm:#vidalia> those circ events are spec compliant, but they're annoying
since they don't include the nickname, even when you ask for verbose_names.
edmanm:#vidalia> i don't know why tor includes that with some circ events and
not others.
edmanm> when i say "usefeature verbose_names", tor gives me hops in circ
events as either "$id=nickname" for named relays or "$id~nickname" for
non-named relays.
edmanm> except in some cases, like the one you pasted above, all i get is
$id.
edmanm> that's the same format you get when you don't specify 'usefeature
verbose_names'. (i.e. just $id for non-named relays or just the nickname for
named relays)
[Automatically added by flyspray2trac: Operating System: All]
0.2.1.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/942
Torbutton @ babelzilla
2009-03-14T17:16:01Z
Trac
Torbutton @ babelzilla
First of all, excuse me for requesting a re-open for the previous bug i filed, i did that accidentally.
I can't find any easy way to contact you so i'm opening another bug just
to ensure that you want Torbutton removed from the Babelzi...
First of all, excuse me for requesting a re-open for the previous bug i filed, i did that accidentally.
I can't find any easy way to contact you so i'm opening another bug just
to ensure that you want Torbutton removed from the Babelzilla database.
It's obvious that you have forgot about the forum we host for Torbutton at
http://www.babelzilla.org/forum/index.php?showtopic=2340&st=0
and you could have used to notify your translators there but that's ok.
I've informed the translators that had registered there for Torbutton and i hope
they will join your own translation project.
PS
I could also act as an intermediate between you and babelzilla if you think that the structure is too complicated there.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: sonickydon
https://gitlab.torproject.org/legacy/trac/-/issues/943
Tor's once-per-second events are not quite once-per-second?
2020-06-13T14:01:27Z
Roger Dingledine
Tor'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-final
Nick Mathewson
Nick Mathewson
https://gitlab.torproject.org/legacy/trac/-/issues/944
Corrupted virtual disk image causes VM to hang
2009-03-16T20:07:31Z
coderman
Corrupted virtual disk image causes VM to hang
If the virtual disk used for persistent Tor state and other system data becomes corrupted
the VM is unable to detect failure to mount the volume. This will result in a VM that never
starts Tor and simply repeats the error "No such file o...
If the virtual disk used for persistent Tor state and other system data becomes corrupted
the VM is unable to detect failure to mount the volume. This will result in a VM that never
starts Tor and simply repeats the error "No such file or directory" for /var/log/tor/notices.log
Manual work around is to remove the state\hdd.img file. For installs this is located at
%PROGRAMFILES%\Tor VM\state\hdd.img
[Automatically added by flyspray2trac: Operating System: All]
coderman
coderman
https://gitlab.torproject.org/legacy/trac/-/issues/945
Vidalia config from previous install causes new Vidalia to hang
2011-01-24T09:24:41Z
coderman
Vidalia config from previous install causes new Vidalia to hang
If a previous Vidalia install has created a vidalia.conf in the local application data folder it
will contain a control port setting that will not connect to the VM instance of Tor. Tor VM should
detect if the existing vidalia.conf needs...
If a previous Vidalia install has created a vidalia.conf in the local application data folder it
will contain a control port setting that will not connect to the VM instance of Tor. Tor VM should
detect if the existing vidalia.conf needs to be replaced with a Tor VM default.
The manual work around is to move the %LOCALAPPDATA%\Vidalia\vidalia.conf elsewhere and restart.
EDIT: fixed; to be included in 0.0.2
[Automatically added by flyspray2trac: Operating System: All]
coderman
coderman
https://gitlab.torproject.org/legacy/trac/-/issues/946
Old Polipo config causes TorButton to hang (or anything using http proxy)
2009-03-27T04:48:36Z
coderman
Old Polipo config causes TorButton to hang (or anything using http proxy)
If an old polipo.txt config file exists in the local user data folder Polipo will
be configured with a parent proxy of localhost instead of the VM 10.10.10.1 address.
Manual workaround is to edit %LOCALAPPDATA%\Polipo\polipo.txt and com...
If an old polipo.txt config file exists in the local user data folder Polipo will
be configured with a parent proxy of localhost instead of the VM 10.10.10.1 address.
Manual workaround is to edit %LOCALAPPDATA%\Polipo\polipo.txt and comment/delete
the socksParentProxy and socksProxyType settings; Tor VM will transparently proxy
Polipo's TCP connections out.
EDIT: fixed; to be included in 0.0.2
[Automatically added by flyspray2trac: Operating System: All]
coderman
coderman
https://gitlab.torproject.org/legacy/trac/-/issues/947
Compress html pages with gzip
2020-06-13T14:01:28Z
Trac
Compress html pages with gzip
Here is another idea to speed up tor.
Compress html/css/javascript (basically any text/* mime types) pages at the exit node with gzip, even if the website itself does not support it.
Most browsers support gzip, even if they dont, they w...
Here is another idea to speed up tor.
Compress html/css/javascript (basically any text/* mime types) pages at the exit node with gzip, even if the website itself does not support it.
Most browsers support gzip, even if they dont, they wont request a gzip page anyway.
But must websites do not do gzip compression so waste bandwidth.
gzip can make html code upto 8 times smaller.
It would help with tor bandwidth and gzip is very fast.
I know html is probably the lowest bandwidth consumer tor has to worry about, but when your downloading at 2kb/sec it really does makes a difference if the page is 40kb or 8kb.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: tortor
https://gitlab.torproject.org/legacy/trac/-/issues/948
Crash on rendcommon.c:33
2020-06-13T14:01:28Z
Trac
Crash on rendcommon.c:33
Revision 19068. Crash. No log (latest "[notice] Performing bandwidth self-test...done.")
Core was generated by `/usr/bin/tor --runasdaemon 1'.
Program terminated with signal 11, Segmentation fault.
[New process 8760]
[New process 8775]
...
Revision 19068. Crash. No log (latest "[notice] Performing bandwidth self-test...done.")
Core was generated by `/usr/bin/tor --runasdaemon 1'.
Program terminated with signal 11, Segmentation fault.
[New process 8760]
[New process 8775]
#0 0x080b89e3 in rend_service_descriptor_free (desc=0x86c9040) at rendcommon.c:33
33 SMARTLIST_FOREACH(desc->successful_uploads, char *, c, tor_free(c););
(gdb) bt
#0 0x080b89e3 in rend_service_descriptor_free (desc=0x86c9040) at rendcommon.c:33
#1 0x080bef73 in rend_consider_services_upload (now=1237319764) at rendservice.c:545
#2 0x080a9774 in second_elapsed_callback (fd=-1, event=1, args=0x0) at main.c:1086
#3 0xb7f1c3ce in event_base_loop (base=0x81430b0, flags=0) at event.c:387
#4 0xb7f1c5b4 in event_loop (flags=0) at event.c:463
#5 0x080a9db5 in do_main_loop () at main.c:1435
#6 0x080aa04f in tor_main (argc=3, argv=0xbfd7b284) at main.c:2060
#7 0x080e67e6 in main (argc=Cannot access memory at address 0x11
) at tor_main.c:30
(gdb)
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: xiando
0.2.1.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/949
Tor server can't bind itself to a ip address and dies.
2020-06-13T14:01:29Z
Trac
Tor server can't bind itself to a ip address and dies.
I am using Tor version 0.2.0.34 (r18423).
I have set up Tor to bind the server to the localhost loopback and to a local network ip address.
By default the daemon is configured to start in runlevel 2 with S20tor.
When the system starts, t...
I am using Tor version 0.2.0.34 (r18423).
I have set up Tor to bind the server to the localhost loopback and to a local network ip address.
By default the daemon is configured to start in runlevel 2 with S20tor.
When the system starts, there is a race condition of the daemons on the same run-level and if the kernel
hasn't yet registered the ip address of the local network
interface because it's querying in dhcp mode,
tor puts a message on stdout on boot that it wasn't able to bind itself to the LAN address specified and dies.
This is very annoying,because I often start the system and then I don't find the expected instance of tor running,
even if the interface and the local ip address are working.
For me it's better if the started instance of tor,keep polling for specified ip address instead of die.
Also moving the name of the file to something like S90tor on all runlevels seems to help partially as the problem seems just to slightly
decrease.(this confirm the race condition problem)
I can't attach any log output as it does not output nothing relevant in the logs...it just dies.
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: mavior
weasel (Peter Palfrader)
weasel (Peter Palfrader)
https://gitlab.torproject.org/legacy/trac/-/issues/950
disabling torbutton clears preferences instead of resetting
2009-04-03T23:01:53Z
Trac
disabling torbutton clears preferences instead of resetting
I have a custom value in the general.useragent.override preference.
When enabling torbutton, it changes this value to "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16", which is intended and f...
I have a custom value in the general.useragent.override preference.
When enabling torbutton, it changes this value to "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16", which is intended and fine.
But when disabling torbutton again, it clears this value instead of resetting it to what's been in there before.
Related: when disabling torbutton, it also ENABLES the settings:
- privacy -> Remember what I enter in forms and the search bar
- privacy -> Remember what I've downloaded
- security -> Remember passwords for sites
Since I have these disabled also before enabling torbutton, enabling them confuses me and causes work.
I think torbutton should save the values of settings it changes and reset them to those instead of whatever values it thinks it should.
Thanks and keep up the awesome work!
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: ilf
https://gitlab.torproject.org/legacy/trac/-/issues/951
Add leak warning when clicking on downloadable files
2010-05-27T06:16:02Z
Trac
Add leak warning when clicking on downloadable files
running the decloak page http://decloak.net/decloak.html
attempts to download a Word document in firefox.
when i clicked "open with abiword" which was selected for me,
the document opened and decloak was able to get my ip address from ab...
running the decloak page http://decloak.net/decloak.html
attempts to download a Word document in firefox.
when i clicked "open with abiword" which was selected for me,
the document opened and decloak was able to get my ip address from abiword.
suggest adding a leak warning when people click downloadable links
or maybe (another option?) disable opening external applications or plugins upon download.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: keb
https://gitlab.torproject.org/legacy/trac/-/issues/952
Torbutton does not block access to non-default Tor-related ports
2018-10-19T20:54:31Z
Trac
Torbutton does not block access to non-default Tor-related ports
https://www.torproject.org/torbutton/design/
The 3.1 Browser overlay section on network.security.ports.banned
assumes that no one changes the default ports.
The tor(1) man page and config documentation on the website
gives those value...
https://www.torproject.org/torbutton/design/
The 3.1 Browser overlay section on network.security.ports.banned
assumes that no one changes the default ports.
The tor(1) man page and config documentation on the website
gives those values as defaults but does not warn users about
a torbutton dependency.
Is there a way to have torbutton check (perhaps only on install)
that the ports are as expected?
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: keb
https://gitlab.torproject.org/legacy/trac/-/issues/953
fail: Unmask Screen - Iframe JavaScript
2013-01-31T03:51:18Z
Trac
fail: Unmask Screen - Iframe JavaScript
torbutton seems to pass all the tests at
http://pseudo-flaw.net/content/tor/torbutton/
except this one:
http://pseudo-flaw.net/tor/torbutton/unmask-screen-iframe-javascript.html
my results:
original XPCNativeWrapper function retrieved
...
torbutton seems to pass all the tests at
http://pseudo-flaw.net/content/tor/torbutton/
except this one:
http://pseudo-flaw.net/tor/torbutton/unmask-screen-iframe-javascript.html
my results:
original XPCNativeWrapper function retrieved
Original Values: Actual Values:
availHeight 550 availHeight 900
availLeft 0 availLeft 0
availTop 0 availTop 0
availWidth 1000 availWidth 1440
colorDepth 24 colorDepth 24
height 550 height 900
left 0 left 0
pixelDepth 24 pixelDepth 24
top 0 top 0
width 1000 width 1440
comments from irc:
[18:34] <mikeperry> that screen thing is a regression
[18:34] <mikeperry> I wonder if its due to an FF3 change
i have firefox 3.0.7 on ubuntu
and i did not test this on earlier firefoxes.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: keb
https://gitlab.torproject.org/legacy/trac/-/issues/954
MacOS X installer fails to install Torbutton if Firefox is running
2009-03-27T12:10:10Z
Seth Schoen
MacOS X installer fails to install Torbutton if Firefox is running
When installing the MacOS X bundle I left Firefox running (having used it to download the bundle). I was not
prompted to exit Firefox and the installer didn't do anything to make Firefox exit.
The installer displayed a generic error m...
When installing the MacOS X bundle I left Firefox running (having used it to download the bundle). I was not
prompted to exit Firefox and the installer didn't do anything to make Firefox exit.
The installer displayed a generic error message because Firefox was already running. Torbutton was not
successfully installed. However, there was no indication from the installer that the Torbutton installation had
failed. In effect, it failed silently because the installer didn't explain the significance of the fact that Firefox was
running.
When Firefox was restarted, Torbutton was not present.
I was able to install cleanly with the MacOS X bundle installer if I quit Firefox before the installer reached the
Torbutton installation stage.
[Automatically added by flyspray2trac: Operating System: OSX 10.5 Leopard]
https://gitlab.torproject.org/legacy/trac/-/issues/955
Upgrading Tor on OS X fails, seen as older than installed
2009-03-27T13:08:30Z
Trac
Upgrading Tor on OS X fails, seen as older than installed
Running OS X 10.4.11 on an Intel based Macbook.
Have been having a small issue over several of the last alpha releases of Tor. When I go to try install a new version
of Tor the installer sees the version of the Tor bundle I am trying ...
Running OS X 10.4.11 on an Intel based Macbook.
Have been having a small issue over several of the last alpha releases of Tor. When I go to try install a new version
of Tor the installer sees the version of the Tor bundle I am trying to install as being older than the version I have
installed.
For example: I have 0.2.1.11 installed and trying to install 0.2.1.13. This throws up a warning in the installer saying
0.2.1.13 is older than the version I'm installing, when I ignore the warning and continue with the install it leaves
me with the original version despite saying the install was successful.
The only way I've found around this is to manually delete Vidialia / Privoxy and Tor as well as all associated files.
Using the included uninstaller script does not seem to remove enough of the bundle that the installer works.
I believe I first noticed this when trying to upgrade 0.2.1.9
[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]
**Trac**:
**Username**: torbert
https://gitlab.torproject.org/legacy/trac/-/issues/956
Updated Greek translation and AMO strings
2011-03-22T08:48:24Z
Trac
Updated Greek translation and AMO strings
I updated the Greek (el-GR) translation for Torbutton and since there's no other way ( or at least i can't see any)
I'm providing here the strings for the AMO page of the extension:
(please note that AMO lists Greek as "el" instead of e...
I updated the Greek (el-GR) translation for Torbutton and since there's no other way ( or at least i can't see any)
I'm providing here the strings for the AMO page of the extension:
(please note that AMO lists Greek as "el" instead of el-GR)
SHORT DESCRIPTION
Το Torbutton παρέχει ένα κουμπί για εύκολη και ασφαλή ενεργοποίηση/απενεργοποίηση χρήσης του δικτύου Tor από τον περιηγητή σας. Προς το παρόν είναι το μόνο πρόσθετο που διαχειρίζεται με ασφάλεια την περιήγηση μέσω δικτύου Tor χωρίς να επιτρέπει διαρροές IP, cookies, και γενικότερα απειλές για το απόρρητο σας.
LONG DESCRIPTION
Το Torbutton σας παρέχει ένα κουμπί για μπορείτε να ενεργοποιήσετε/απενεργοποιήσετε εύκολα τη χρήση του δικτύου Tor από τον περιηγητή σας. Από την έκδοση 1.1 και μετά, το Torbutton παρέχει εξελιγμένα χαρακτηριστικά απορρήτου και απομόνωσης της κατάστασης λειτουργίας του περιηγητή, που το καθιστούν την καλύτερη επιλογή για ασφαλή χρήση του δικτύου Tor από οποιοδήποτε άλλο γενικό πρόσθετο εναλλαγής διαμεσολαβητών. Μπορεί να συνδυαστεί με πρόσθετα πολλαπλής εναλλαγής διαμεσολαβητών για να παρέχει προστασία Tor όταν έχει επιλεχθεί ο διαμεσολαβητής Tor, αλλά παρακαλούμε δείτε τη σελίδα συχνών ερωτήσεων (FAQ - Αγγλικά) για πληροφορίες σχετικά με την παράλληλη χρήση βασιζόμενων σε φίλτρα πρόσθετων όπως το FoxyProxy.
Μπορεί επίσης να χρησιμοποιηθεί ανεξάρτητα από το δίκτυο Tor για γενικότερη διαχείριση του απορρήτου σας με κάποιο βοηθητικό διαμεσολαβητή όπως το privoxy ή τον polipo.
Για περισσότερες πληροφορίες, επισκεφθείτε την αρχική σελίδα του Torbutton και τισ σχυνές ερωτήσεις (FAQ) στη διεύθυνση: https://www.torproject.org/torbutton (Αγγλικά)
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: sonickydon
Runa Sandvik
Runa Sandvik
https://gitlab.torproject.org/legacy/trac/-/issues/957
v0.2.1.13-alpha crashing
2020-06-13T14:01:36Z
Trac
v0.2.1.13-alpha crashing
Tor v0.2.1.13-alpha (r18828) on Debian Lenny x86_64
My Blutmagie server process died dumping a core file. gdb backtrace output refers to eventdns.
anonymizer2:~# gdb /usr/sbin/tor ~debian-tor/.tor/core.20793
GNU gdb 6.8-debian
Copyrigh...
Tor v0.2.1.13-alpha (r18828) on Debian Lenny x86_64
My Blutmagie server process died dumping a core file. gdb backtrace output refers to eventdns.
anonymizer2:~# gdb /usr/sbin/tor ~debian-tor/.tor/core.20793
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: core file may not match specified executable file.
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/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 /usr/lib/libssl.so.0.9.8...done.
Loaded symbols for /usr/lib/libssl.so.0.9.8
Reading symbols from /usr/lib/libcrypto.so.0.9.8...done.
Loaded symbols for /usr/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/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
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
Core was generated by `/usr/sbin/tor'.
Program terminated with signal 6, Aborted.
[New process 20793]
[New process 20803]
[New process 20802]
[New process 20801]
[New process 20800]
[New process 20799]
[New process 20798]
[New process 20797]
[New process 20796]
[New process 20795]
[New process 20794]
#0 0x00007f99debe8ed5 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00007f99debe8ed5 in raise () from /lib/libc.so.6
#1 0x00007f99debea3f3 in abort () from /lib/libc.so.6
#2 0x00007f99debe1dc9 in __assert_fail () from /lib/libc.so.6
#3 0x00007f99df91c453 in ?? () from /usr/lib/libevent-1.3e.so.1
#4 0x00007f99df91c734 in event_add () from /usr/lib/libevent-1.3e.so.1
#5 0x0000000000496922 in evdns_request_transmit (req=0x7f99d0acee00)
at eventdns.c:482
#6 0x000000000049716a in evdns_requests_pump_waiting_queue ()
at eventdns.c:2168
#7 0x000000000049769a in reply_handle (req=0x7f99d36b3c00,
flags=<value optimized out>, ttl=<value optimized out>,
reply=<value optimized out>) at eventdns.c:826
#8 0x0000000000497f47 in nameserver_read (ns=0x7f99dff4e800)
at eventdns.c:1031
#9 0x00007f99df91cec1 in event_base_loop () from /usr/lib/libevent-1.3e.so.1
#10 0x000000000045f606 in do_main_loop () at main.c:1435
#11 0x000000000045f855 in tor_main (argc=1, argv=<value optimized out>)
at main.c:2060
#12 0x00007f99debd51a6 in __libc_start_main () from /lib/libc.so.6
#13 0x0000000000407689 in _start ()
(gdb)
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: Falo
0.2.1.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/958
web links clicked from a locally saved page don't work
2010-07-29T16:21:39Z
Trac
web links clicked from a locally saved page don't work
Some links to websites are on a html page stored on my disk. I display this page and when TOR is enabled through TorButton, a click on the links do not give anything.
The security options of TorButton are set as:
Block Tor access to ne...
Some links to websites are on a html page stored on my disk. I display this page and when TOR is enabled through TorButton, a click on the links do not give anything.
The security options of TorButton are set as:
Block Tor access to network from file://urls is NOT ticked
Block Non-Tor access to network from file://urls is NOT ticked
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: natol
https://gitlab.torproject.org/legacy/trac/-/issues/959
bodylen 501408 larger than 499999. Failing.
2020-06-13T14:01:36Z
Roger Dingledine
bodylen 501408 larger than 499999. Failing.
Tor directory authorities are refusing uploaded votes, since the votes
have grown larger than 500KB.
Mar 26 23:50:03.015 [warn] bodylen 501408 larger than 499999. Failing.
Mar 26 23:50:03.015 [warn] Invalid input from address '86.59.21....
Tor directory authorities are refusing uploaded votes, since the votes
have grown larger than 500KB.
Mar 26 23:50:03.015 [warn] bodylen 501408 larger than 499999. Failing.
Mar 26 23:50:03.015 [warn] Invalid input from address '86.59.21.38'. Closing.
moria1 (and others) have been doing this for the past 5 days, and the world
hasn't exploded. I think that's because the uploads are refused:
/** Maximum size, in bytes, for any directory object that we're accepting
* as an upload. */
#define MAX_DIR_UL_SIZE 500000
but then Tor falls back to fetching the votes, which succeeds:
/** Maximum size, in bytes, for any directory object that we've downloaded. */
#define MAX_DIR_DL_SIZE MAX_BUF_SIZE
Currently there are only four items that are uploaded:
/** A connection to a directory server: upload a server descriptor. */
#define DIR_PURPOSE_UPLOAD_DIR 8
/** A connection to a directory server: upload a rendezvous
* descriptor. */
#define DIR_PURPOSE_UPLOAD_RENDDESC 9
/** A connection to a directory server: upload a v3 networkstatus vote. */
#define DIR_PURPOSE_UPLOAD_VOTE 10
/** A connection to a directory server: upload a v3 consensus signature */
#define DIR_PURPOSE_UPLOAD_SIGNATURES 11
And once UPLOAD_DIR has finished, we limit the size of the objects we're
willing to add, in case we're attacked.
I think the right fix is to set MAX_DIR_UL_SIZE to MAX_BUF_SIZE also. Any
other fix will mean we reopen this bug in 18 months.
[Automatically added by flyspray2trac: Operating System: All]
https://gitlab.torproject.org/legacy/trac/-/issues/960
Tor believes bridges are offline at startup
2020-06-13T14:01:37Z
Andrew Lewman
Tor believes bridges are offline at startup
[07:42:32] < phobos> [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
[07:42:34] < phobos> lies
[07:43:17] < phobos> it's been doing this for 10 minutes
[07:43:29] < phobos> yet I can connect to the ...
[07:42:32] < phobos> [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
[07:42:34] < phobos> lies
[07:43:17] < phobos> it's been doing this for 10 minutes
[07:43:29] < phobos> yet I can connect to the bridges just fine
[07:45:56] < killerchicken_> heh
[07:46:09] < killerchicken_> if we could debug this, that would solve a lot of problem reports we had
[07:46:59] < phobos> forcing an app request through it makes it try
[07:47:03] < phobos> and succeed
[07:48:27] < killerchicken_> ah
[07:48:28] < killerchicken_> * are marked with purpose 'bridge' and are running. Else return 0.
[07:48:37] < killerchicken_> ups
[07:48:40] < killerchicken_> ./** Return 1 if any of our entry guards have descriptors that
[07:51:30] < killerchicken_> hm
[07:52:35] < killerchicken_> I'd love to debug this more, but it has to wait... Have you made a bug report?
[07:53:04] < phobos> on my to do list
[07:53:22] < killerchicken_> ok
[07:55:10] < killerchicken_> I think the problem is inside the any_bridge_descriptors_known() / choose_random_entry() logic
[07:55:37] < killerchicken_> I'll look at it more if nobody else finds the time. Can you please add this stuff from here to the bug?
Log file says:
ar 27 07:42:12.269 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Mar 27 07:42:23.309 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Mar 27 07:42:28.329 [Info] routerlist_remove_old_routers(): We have 1203 live routers and 0 old router descriptors.
Mar 27 07:42:28.334 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Mar 27 07:42:34.348 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Mar 27 07:42:45.388 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Mar 27 07:42:56.420 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Mar 27 07:43:07.461 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Mar 27 07:43:18.500 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Mar 27 07:43:29.541 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
forcing an app request through tor creates:
Mar 27 07:46:14.173 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Mar 27 07:46:16.197 [Notice] Application request when we're believed to be offline. Optimistically trying known bridges again.
Mar 27 07:46:16.210 [Info] connection_edge_process_inbuf(): data from edge while in 'waiting for circuit' state. Leaving it on buffer.
Mar 27 07:46:25.220 [Info] update_consensus_router_descriptor_downloads(): 3 router descriptors downloadable. 0 delayed; 1201 present (0 of those were in old_routers); 0 would_reject; 0 wouldnt_use; 0 in progress.
Mar 27 07:46:25.233 [Info] launch_router_descriptor_downloads(): There are not many downloadable routerdescs, but we haven't tried downloading descriptors recently. Downloading.
Mar 27 07:46:25.248 [Info] launch_router_descriptor_downloads(): Launching 1 request for 3 routers, 4 at a time
[Automatically added by flyspray2trac: Operating System: Other Linux]
Tor: 0.2.3.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/961
TotalTraffic option (upload+download)
2020-06-13T14:01:38Z
Trac
TotalTraffic option (upload+download)
Could a TotalTraffic option similar to AccountingMax be added?
I know, it isn't to hard to divide by two, but you usually need
to limit the sum of upload and download to not exceed your
traffic limit.
Maybe the description of Accounting...
Could a TotalTraffic option similar to AccountingMax be added?
I know, it isn't to hard to divide by two, but you usually need
to limit the sum of upload and download to not exceed your
traffic limit.
Maybe the description of AccountingMax should also be changed to
make it clear, if one, either upstream traffic or downstream
traffic exceeds the limit Tor will hibernate.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Athaba
Tor: 0.2.6.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/962
bandwidth change makes relay publish but authorities discard
2020-06-13T14:01:38Z
Roger Dingledine
bandwidth change makes relay publish but authorities discard
Apr 01 09:45:39.145 [info] dirserv_add_descriptor(): Added descriptor from 'fluxe3' (source: 78.47.18.110): Valid server updated.
Apr 01 18:52:28.976 [info] dirserv_add_descriptor(): Not replacing descriptor from 'fluxe3' (source: 78.47....
Apr 01 09:45:39.145 [info] dirserv_add_descriptor(): Added descriptor from 'fluxe3' (source: 78.47.18.110): Valid server updated.
Apr 01 18:52:28.976 [info] dirserv_add_descriptor(): Not replacing descriptor from 'fluxe3' (source: 78.47.18.110); differences are cosmetic.
shahn> I also reloaded it at 22:52 on April 1st
>what exactly did you change?
shahn> RelayBandwidthRate 150 KBytes (was at 10000 or something insanely high)
shahn> and RelayBandwidthBurst 200 KBytes (was at 15000)
> see options_transition_affects_descriptor() in config.c
> If
> * you changed your bandwidthrate but maxadvertisedbandwidth still
> * trumps, no need to republish.
> as part of an XXX
> then compare to router_differences_are_cosmetic()
> any differences between these two functions will cause bugs like yours.
> in the latter, it does
> /* Did bandwidth change a lot? */
> if ((r1->bandwidthcapacity < r2->bandwidthcapacity/2) ||
> (r2->bandwidthcapacity < r1->bandwidthcapacity/2))
> return 0;
> in the former, it says "did they change at all"
what the relay should do is make a new descriptor, and then call
router-differences-are-cosmetic on it, and revert if cosmetic.
that way we're using the same function, rather than trying to keep the
checks the same in both cases.
[Automatically added by flyspray2trac: Operating System: All]
Tor: 0.2.3.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/963
Allow caching as an option
2018-03-10T14:51:29Z
Mike Perry
Allow caching as an option
We probably should provide an option to allow full caching in Tor mode for censorship-only users.
[Automatically added by flyspray2trac: Operating System: All]
We probably should provide an option to allow full caching in Tor mode for censorship-only users.
[Automatically added by flyspray2trac: Operating System: All]
https://gitlab.torproject.org/legacy/trac/-/issues/964
Torbutton turns to disabled when firefox starts.
2009-04-12T06:14:39Z
Trac
Torbutton turns to disabled when firefox starts.
Why does TORBUTTON turns disable every time I start my firefox?
Even when I turn it unable, when a close firefox and open it again, its turned disabeld again..
I need some help.
Thanks
[Automatically added by flyspray2trac: Operatin...
Why does TORBUTTON turns disable every time I start my firefox?
Even when I turn it unable, when a close firefox and open it again, its turned disabeld again..
I need some help.
Thanks
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: brunieri
https://gitlab.torproject.org/legacy/trac/-/issues/965
Redo DNS tests when exit policy changes from reject *; avoid when policy chan...
2020-06-13T14:01:39Z
Sebastian Hahn
Redo DNS tests when exit policy changes from reject *; avoid when policy changes to reject *
> hm. I published my descriptor before doing DNS tests. Also, I'm rejecting all exit
traffic, and still do DNS tests. Isn't that supposed to be different?
<armadev> i've had a todo item for nick to not do dns tests if reject *:*. he didn...
> hm. I published my descriptor before doing DNS tests. Also, I'm rejecting all exit
traffic, and still do DNS tests. Isn't that supposed to be different?
<armadev> i've had a todo item for nick to not do dns tests if reject *:*. he didn't
want to put it in, though.
<armadev> i think that you would need to remember whether you did them, and if
not launch them, if exit policy changes from reject * to something else
> Can't we just redo them every time exit policy changes from reject to something?
<armadev> fine by me. open a flyspray, due 0.2.2.x?
> (in theory, we should probably redo them when the IP changes. This could mean
Laptop user in a new environment)
[Automatically added by flyspray2trac: Operating System: All]
Tor: unspecified
https://gitlab.torproject.org/legacy/trac/-/issues/966
Do positive DNS tests
2020-06-13T14:01:39Z
Sebastian Hahn
Do positive DNS tests
<armadev> yep. do we do some 'positive' dns tests too? that is, if we can't
resolve google or cnn or akamai, maybe we can't resolve anything.
<armadev> mikeperry found some relays that can't resolve anything
Maybe we should add some mor...
<armadev> yep. do we do some 'positive' dns tests too? that is, if we can't
resolve google or cnn or akamai, maybe we can't resolve anything.
<armadev> mikeperry found some relays that can't resolve anything
Maybe we should add some more tests to see if some well-known sites can
be resolved. Also, we should probably wait with publishing the descriptor
until DNS tests have run.
[Automatically added by flyspray2trac: Operating System: All]
Tor: unspecified
https://gitlab.torproject.org/legacy/trac/-/issues/967
Firefox crashed because of Torbutton
2009-06-12T06:55:36Z
Trac
Firefox crashed because of Torbutton
Hi,
I'm using Firefox 3.08 at Ubuntu Jaunty. Just loaded a new page and while this page was loading I activated Torbutton.
Then Firefox crashed. After restarting Firefox I got following message:
Torbutton crash state conflict! Please f...
Hi,
I'm using Firefox 3.08 at Ubuntu Jaunty. Just loaded a new page and while this page was loading I activated Torbutton.
Then Firefox crashed. After restarting Firefox I got following message:
Torbutton crash state conflict! Please file bug report with these four values: true,true,true,false
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: hias90
https://gitlab.torproject.org/legacy/trac/-/issues/968
Directory authority in private Tor network doesn't publish consensus
2020-06-13T14:01:40Z
Karsten Loesing
Directory authority in private Tor network doesn't publish consensus
Under certain circumstances a single directory authority in a private Tor
network does not manage to publish a consensus. For some reason the
directory adds itself to the list of trusted directory authorities *twice*.
The result is that ...
Under certain circumstances a single directory authority in a private Tor
network does not manage to publish a consensus. For some reason the
directory adds itself to the list of trusted directory authorities *twice*.
The result is that it thinks there are 2 directories and that a single
vote is not enough to publish a consensus.
The directory triggers the following warning:
Index: src/or/routerlist.c
===================================================================
--- src/or/routerlist.c (revision 19258)
+++ src/or/routerlist.c (working copy)
@@ -3706,6 +3706,18 @@
hostname = tor_strdup(address);
}
+ SMARTLIST_FOREACH(trusted_dir_servers, trusted_dir_server_t *, ent, {
+ if (ent->v3_identity_digest &&
+ !memcmp(v3_auth_digest, ent->v3_identity_digest, DIGEST_LEN))
+ log_warn(LD_CONFIG, "We already have a directory with the same "
+ "v3 identity digest %s, address %s, OR port %d, and Dir port %d. "
+ "Now we try to add one with address %s, OR port %d, and Dir port %d. "
+ "Something is wrong here!",
+ hex_str(ent->v3_identity_digest, DIGEST_LEN),
+ ent->address, ent->or_port, ent->dir_port,
+ hostname, or_port, dir_port);
+ });
+
ent = tor_malloc_zero(sizeof(trusted_dir_server_t));
ent->nickname = nickname ? tor_strdup(nickname) : NULL;
ent->address = hostname;
A workaround is to add a return statement to that loop. But it would be
better to find out why the directory adds itself to the list twice.
[Automatically added by flyspray2trac: Operating System: All]
Tor: 0.2.3.x-final
Sebastian Hahn
Sebastian Hahn
https://gitlab.torproject.org/legacy/trac/-/issues/969
Directory authorities have different opinions on MTBF and WFU
2020-06-13T14:01:41Z
Karsten Loesing
Directory authorities have different opinions on MTBF and WFU
It has turned out that directory authorities have very different opinions
on relays' MTBF (mean time between failure) and WFU (weighted fractional
uptime). The result is that they vote differently on Guard and Stable
flags:
http://freeh...
It has turned out that directory authorities have very different opinions
on relays' MTBF (mean time between failure) and WFU (weighted fractional
uptime). The result is that they vote differently on Guard and Stable
flags:
http://freehaven.net/~karsten/metrics/relayflags-2009-04-01.pdf
One reason might be false assumptions about running relays as reflected in
the router-stability files. If a relay is running, the corresponding MTBF
line contains the starting time. The starting time is used to include the
running session in MTBF and WFU calculation. An analysis of three
router-stability files shows that authorities think there are between 6K
and 24K relays currently running, which is wrong:
$ grep "MTBF" ides-2009-04-14 | grep "S=" | wc -l
24082
$ grep "MTBF" gabelmoo-2009-04-15 | grep "S=" | wc -l
9206
$ grep "MTBF" moria1-2009-04-15 | grep "S=" | wc -l
6395
These lines are never removed from router-stability files, so that whenever
these relays come back, they appear to be uber-stable which they of course
are not.
The problem lies in the fact that this starting time is only set to 0 in a
few edge cases using rep_hist_note_router_unreachable() in rephist.c. This
function should be called whenever a relay has gone offline, which is of
course difficult to know.
As a possible solution, Tor could check during maintenance when a relay was
contacted the last time. If this time lies more than twice the reachability
timeout in the past, the relay should be marked as unreachable in
rephist.c, too. A simple patch (with some code duplication from
dirserv_set_router_is_running() in dirserv.c) would look like this:
Index: src/or/rephist.c
===================================================================
--- src/or/rephist.c (revision 19341)
+++ src/or/rephist.c (working copy)
@@ -658,6 +658,22 @@
digestmap_iter_get(orhist_it, &d1, &or_history_p);
or_history = or_history_p;
+#define DOUBLE_REACHABLE_TIMEOUT (2*45*60)
+ /* If we are an authority, check if this router is still running. */
+ if (authority && !or_history->start_of_run) {
+ char time_buf[ISO_TIME_LEN+1];
+ routerinfo_t *router = router_get_by_digest(d1);
+ if (!router || (router_is_me(router) && we_are_hibernating()) ||
+ (!get_options()->AssumeReachable &&
+ before >= router->last_reachable + DOUBLE_REACHABLE_TIMEOUT)) {
+ format_iso_time(time_buf, before);
+ log_info(LD_DIR, "When cleaning the reputation history at %s, "
+ "we found that router %s is not running anymore.",
+ time_buf, hex_str(d1, DIGEST_LEN));
+ rep_hist_note_router_unreachable(d1, before);
+ }
+ }
+ /* Now decide if we want to keep it. */
remove = authority ? (or_history->total_run_weights < STABILITY_EPSILON &&
!or_history->start_of_run)
: (or_history->changed < before);
[Automatically added by flyspray2trac: Operating System: All]
Karsten Loesing
Karsten Loesing
https://gitlab.torproject.org/legacy/trac/-/issues/970
Recently closed tabs in Firefox
2009-06-12T06:55:55Z
Trac
Recently closed tabs in Firefox
When I use torbutton in firefox, history of recently closed tabs are still saved, during and after a tor-session.
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: buffedelic
When I use torbutton in firefox, history of recently closed tabs are still saved, during and after a tor-session.
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: buffedelic
https://gitlab.torproject.org/legacy/trac/-/issues/971
Tor Button fails to mask IP in "Shields UP"
2009-05-18T20:11:03Z
Trac
Tor Button fails to mask IP in "Shields UP"
I installed tor button from the Mozilla website, enebled it leaving all settings to defaults and went to
Shields Up to check it out and my IP address was the same as before I installed it. Talk about a false
sense of security.
Why doe...
I installed tor button from the Mozilla website, enebled it leaving all settings to defaults and went to
Shields Up to check it out and my IP address was the same as before I installed it. Talk about a false
sense of security.
Why doesn't tor button check to see if its working and warn if it isn't instead of
letting the user be rudely surprised when they check for themselves, or worse, if they don't check for
themselves...
FWIW I'm a newbie so the prob may be between my ears
Tor Button 1.2.0
Privoxy 3.0.8
Firefox 3.0.8 "Mozilla Firefox for Ubuntu canonical - 1.0"
Xubuntu 8.10, Linux Kernel 2.6.27-14 generic
Other active (not disabled) Firefox plugins:
Adblock Plus 0.7.5.4
BetterPrivacy 1.29
DownloadHelper 4.3
Sage 1.4.2
Ubuntu Firefox Modifications 0.6
United States English Dictionary 3.03
jek2bd = Just Enough Knowledge To Be Dangerous
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: jek2bd
https://gitlab.torproject.org/legacy/trac/-/issues/972
Tor Button fails to mask IP in "Shields UP" check
2009-04-21T22:07:17Z
Trac
Tor Button fails to mask IP in "Shields UP" check
I installed tor button from the Mozilla website, enabled it leaving all settings to defaults and went to
Shields Up to check it out. My IP address was the same as before I installed it. Talk about a false
sense of security.
Why doesn'...
I installed tor button from the Mozilla website, enabled it leaving all settings to defaults and went to
Shields Up to check it out. My IP address was the same as before I installed it. Talk about a false
sense of security.
Why doesn't tor button check to see if its actually working and warn if it isn't instead of
letting the user be rudely surprised when they check for themselves, or worse, if they don't check for
themselves...
FWIW I'm a newbie so the prob may be between my ears, I guess I naively expected it to work when it said it was
enabled and didn't complain otherwise.
Tor Button 1.2.0
Privoxy 3.0.8
Firefox 3.0.8 "Mozilla Firefox for Ubuntu canonical - 1.0"
Xubuntu 8.10, Linux Kernel 2.6.27-14 generic
Other active (not disabled) Firefox plugins:
Adblock Plus 0.7.5.4
BetterPrivacy 1.29
DownloadHelper 4.3
Sage 1.4.2
Ubuntu Firefox Modifications 0.6
United States English Dictionary 3.03
jek2bd = Just Enough Knowledge To Be Dangerous
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: jek2bd
https://gitlab.torproject.org/legacy/trac/-/issues/973
OSX uninstall script misses some files
2020-06-13T14:01:41Z
Andrew Lewman
OSX uninstall script misses some files
From: Danny Thomas <d.thomas@its.uq.edu.au>
To: tor-volunteer@torproject.org
Subject: OSX uninstall_tor_bundle.sh does not remove everything
Date: Tue, 21 Apr 2009 09:11:44 +1000
Sender: owner-tor-assistants@torproject.org
User-Agent: Th...
From: Danny Thomas <d.thomas@its.uq.edu.au>
To: tor-volunteer@torproject.org
Subject: OSX uninstall_tor_bundle.sh does not remove everything
Date: Tue, 21 Apr 2009 09:11:44 +1000
Sender: owner-tor-assistants@torproject.org
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
on https://www.torproject.org/docs/tor-doc-osx.html.en
4 corrections
should be hyphen in "/usr/bin/tor_resolve"
should be 'P' in "/Library/Receipts/privoxyconf.pkg/"
doesn't mention /Applications/Vidalia.app
doesn't mention /Library/Receipts/Vidalia.pkg
Unfortunately I forgot to check the version I was uninstalling but
am fairly confidant it was installed from
vidalia-bundle-0.2.0.34-0.1.10-universal.dmg
after manually finishing the uninstall, I installed
vidalia-bundle-0.2.1.14-rc-0.1.12-universal
and confirmed that its' uninstall script behaved the same,
i.e. the following items were left
it might be better saying to run /Library/Tor/uninstall_tor_bundle.sh
as that script deletes the directory you're in
"Tor and Privoxy are now completely removed from your system."
well that wasn't the case for me
first off the script reported errors and I've no idea whether these
prevented
items from being uninstalled or whether the script does not include
everything to be removed
bash-3.2# ./uninstall_tor_bundle.sh
ps: No user named 'ax'
. tor process appears to already be stopped
ps: No user named 'ax'
. privoxy process appears to already be stopped
./uninstall_tor_bundle.sh: line 123: /Library/Tor/package_list.txt: No
such file or directory
. Removing created user _tor
delete: Invalid Path
<dscl_cmd> DS Error: -14009 (eDSUnknownNodeName)
. Cleaning up
. Finished
after that I found the following were still there
so I manually deleted them
ls /Library/Vidalia/
CHANGELOG CREDITS README
ls -l /usr/bin/tor*
lrwxr-xr-x 1 root wheel 16 23 Jan 08:10 /usr/bin/tor -> /Library/Tor/tor
lrwxr-xr-x 1 root wheel 24 23 Jan 08:10 /usr/bin/tor-resolve ->
/Library/Tor/
ls -l /var/log/tor*
-rw-rw---- 1 root daemon 0 20 Jan 2008 /var/log/tor.log
bash-3.2# ls -alR /Library/Receipts/Priv*
/Library/Receipts/Privoxy.pkg:
total 0
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 94 root admin 3196 21 Apr 06:45 ..
drwxrwxr-x 6 root admin 204 23 Jan 08:10 Contents
/Library/Receipts/Privoxy.pkg/Contents:
total 96
drwxrwxr-x 6 root admin 204 23 Jan 08:10 .
drwxrwxr-x 3 root admin 102 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 40388 22 Nov 2006 Archive.bom
-rw-rw-r-- 1 root admin 1283 23 Jan 08:10 Info.plist
-rw-rw-r-- 1 root admin 8 22 Nov 2006 PkgInfo
drwxrwxr-x 16 root admin 544 23 Jan 08:10 Resources
/Library/Receipts/Privoxy.pkg/Contents/Resources:
total 200
drwxrwxr-x 16 root admin 544 23 Jan 08:10 .
drwxrwxr-x 6 root admin 204 23 Jan 08:10 ..
drwxrwxr-x 7 root admin 238 23 Jan 08:10 CVS
-rw-rw-r-- 1 root admin 1053 22 Nov 2006 Description.plist
-rwxrwxr-x 1 root admin 15623 22 Nov 2006 License.html
-rw-rw-r-- 1 root admin 40388 22 Nov 2006 Privoxy.bom
-rw-rw-r-- 1 root admin 864 22 Nov 2006 Privoxy.info
-rwxrwxr-x 1 root admin 2247 22 Nov 2006 Privoxy.post_install
-rwxrwxr-x 1 root admin 2693 22 Nov 2006 Privoxy.post_upgrade
-rwxrwxr-x 1 root admin 10 22 Nov 2006 Privoxy.pre_upgrade
-rw-rw-r-- 1 root admin 46 22 Nov 2006 Privoxy.sizes
-rwxrwxr-x 1 root admin 861 22 Nov 2006 ReadMe.txt
-rwxrwxr-x 1 root admin 2247 22 Nov 2006 postinstall
-rwxrwxr-x 1 root admin 2693 22 Nov 2006 postupgrade
-rwxrwxr-x 1 root admin 10 22 Nov 2006 preupgrade
-rwxrwxr-x 1 root admin 401 22 Nov 2006 welcome.txt
/Library/Receipts/Privoxy.pkg/Contents/Resources/CVS:
total 24
drwxrwxr-x 7 root admin 238 23 Jan 08:10 .
drwxrwxr-x 16 root admin 544 23 Jan 08:10 ..
drwxrwxr-x 2 root admin 68 23 Jan 08:10 Base
-rwxrwxr-x 1 root admin 0 22 Nov 2006 Baserev
-rwxrwxr-x 1 root admin 263 22 Nov 2006 Entries
-rwxrwxr-x 1 root admin 16 22 Nov 2006 Repository
-rwxrwxr-x 1 root admin 66 22 Nov 2006 Root
/Library/Receipts/Privoxy.pkg/Contents/Resources/CVS/Base:
total 0
drwxrwxr-x 2 root admin 68 23 Jan 08:10 .
drwxrwxr-x 7 root admin 238 23 Jan 08:10 ..
/Library/Receipts/PrivoxyConf.pkg:
total 0
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 94 root admin 3196 21 Apr 06:45 ..
drwxrwxr-x 6 root admin 204 23 Jan 08:10 Contents
/Library/Receipts/PrivoxyConf.pkg/Contents:
total 88
drwxrwxr-x 6 root admin 204 23 Jan 08:10 .
drwxrwxr-x 3 root admin 102 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 35268 3 Dec 12:07 Archive.bom
-rw-rw-r-- 1 root admin 1329 23 Jan 08:10 Info.plist
-rw-rw-r--@ 1 root admin 9 3 Dec 12:07 PkgInfo
drwxrwxr-x 5 root admin 170 23 Jan 08:10 Resources
/Library/Receipts/PrivoxyConf.pkg/Contents/Resources:
total 16
drwxrwxr-x 5 root admin 170 23 Jan 08:10 .
drwxrwxr-x 6 root admin 204 23 Jan 08:10 ..
drwxrwxr-x 3 root admin 102 23 Jan 08:10 en.lproj
-rw-rw-r--@ 1 root admin 17 3 Dec 12:07 package_version
-rwxrwxr-x 1 root admin 423 3 Dec 12:07 postflight
/Library/Receipts/PrivoxyConf.pkg/Contents/Resources/en.lproj:
total 8
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 5 root admin 170 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 387 3 Dec 12:07 Description.plist
bash-3.2# ls -al /Library/Receipts/Tor.pkg
total 0
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 92 root admin 3128 21 Apr 08:42 ..
drwxrwxr-x 6 root admin 204 23 Jan 08:10 Contents
bash-3.2# ls -alR /Library/Receipts/Tor.pkg
total 0
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 92 root admin 3128 21 Apr 08:42 ..
drwxrwxr-x 6 root admin 204 23 Jan 08:10 Contents
/Library/Receipts/Tor.pkg/Contents:
total 88
drwxrwxr-x 6 root admin 204 23 Jan 08:10 .
drwxrwxr-x 3 root admin 102 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 36008 3 Dec 12:07 Archive.bom
-rw-rw-r-- 1 root admin 1399 23 Jan 08:10 Info.plist
-rw-rw-r--@ 1 root admin 9 3 Dec 12:07 PkgInfo
drwxrwxr-x 9 root admin 306 23 Jan 08:10 Resources
/Library/Receipts/Tor.pkg/Contents/Resources:
total 48
drwxrwxr-x 9 root admin 306 23 Jan 08:10 .
drwxrwxr-x 6 root admin 204 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 3555 3 Dec 12:07 Tor_Uninstaller.applescript
drwxrwxr-x 7 root admin 238 23 Jan 08:10 documents
drwxrwxr-x 3 root admin 102 23 Jan 08:10 en.lproj
-rw-rw-r-- 1 root admin 53 3 Dec 12:07 package_list.txt
-rw-rw-r--@ 1 root admin 17 3 Dec 12:07 package_version
-rwxrwxr-x 1 root admin 1942 3 Dec 12:07 postflight
-rwxrwxr-x 1 root admin 4854 3 Dec 12:07 uninstall_tor_bundle.sh
/Library/Receipts/Tor.pkg/Contents/Resources/documents:
total 632
drwxrwxr-x 7 root admin 238 23 Jan 08:10 .
drwxrwxr-x 9 root admin 306 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 1305 3 Dec 12:07 AUTHORS.txt
drwxrwxr-x 11 root admin 374 23 Jan 08:10 Advanced
drwxrwxr-x 25 root admin 850 23 Jan 08:10 howto
-rw-rw-r-- 1 root admin 238952 3 Dec 12:07 tor-reference.pdf
-rw-rw-r-- 1 root admin 75588 3 Dec 12:07 tor-resolve.pdf
/Library/Receipts/Tor.pkg/Contents/Resources/documents/Advanced:
total 1032
drwxrwxr-x 11 root admin 374 23 Jan 08:10 .
drwxrwxr-x 7 root admin 238 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 341563 3 Dec 12:07 ChangeLog.txt
-rw-rw-r-- 1 root admin 5025 3 Dec 12:07 HACKING.txt
-rw-rw-r-- 1 root admin 2429 3 Dec 12:07 address-spec.txt
-rw-rw-r-- 1 root admin 64214 3 Dec 12:07 control-spec.txt
-rw-rw-r-- 1 root admin 19815 3 Dec 12:07 path-spec.txt
-rw-rw-r-- 1 root admin 35398 3 Dec 12:07 rend-spec.txt
-rw-rw-r-- 1 root admin 3339 3 Dec 12:07 socks-extensions.txt
-rw-rw-r-- 1 root admin 38209 3 Dec 12:07 tor-spec.txt
-rw-rw-r-- 1 root admin 2202 3 Dec 12:07 version-spec.txt
/Library/Receipts/Tor.pkg/Contents/Resources/documents/howto:
total 592
drwxrwxr-x 25 root admin 850 23 Jan 08:10 .
drwxrwxr-x 7 root admin 238 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 6172 3 Dec 12:07 stylesheet.css
-rw-rw-r-- 1 root admin 12010 3 Dec 12:07 tor-doc-osx.html.en
-rw-rw-r-- 1 root admin 12703 3 Dec 12:07 tor-doc-osx.html.es
-rw-rw-r-- 1 root admin 13522 3 Dec 12:07 tor-doc-osx.html.fr
-rw-rw-r-- 1 root admin 12545 3 Dec 12:07 tor-doc-osx.html.it
-rw-rw-r-- 1 root admin 13100 3 Dec 12:07 tor-doc-osx.html.pl
-rw-rw-r-- 1 root admin 17426 3 Dec 12:07 tor-doc-server.html.de
-rw-rw-r-- 1 root admin 3674 3 Dec 12:07 tor-doc-server.html.en
-rw-rw-r-- 1 root admin 4005 3 Dec 12:07 tor-doc-server.html.fr
-rw-rw-r-- 1 root admin 3996 3 Dec 12:07 tor-doc-server.html.it
-rw-rw-r-- 1 root admin 4043 3 Dec 12:07 tor-doc-server.html.pl
-rw-rw-r-- 1 root admin 4139 3 Dec 12:07 tor-doc-server.html.ru
-rw-rw-r-- 1 root admin 13830 3 Dec 12:07 tor-hidden-service.html.en
-rw-rw-r-- 1 root admin 14628 3 Dec 12:07 tor-hidden-service.html.es
-rw-rw-r-- 1 root admin 15816 3 Dec 12:07 tor-hidden-service.html.fr
-rw-rw-r-- 1 root admin 14471 3 Dec 12:07 tor-hidden-service.html.it
-rw-rw-r-- 1 root admin 15293 3 Dec 12:07 tor-hidden-service.html.pl
-rw-rw-r-- 1 root admin 20757 3 Dec 12:07 tor-hidden-service.html.ru
-rw-rw-r-- 1 root admin 13806 3 Dec 12:07 tor-hidden-service.html.zh-cn
-rw-rw-r-- 1 root admin 9267 3 Dec 12:07 tor-switchproxy.html.en
-rw-rw-r-- 1 root admin 9892 3 Dec 12:07 tor-switchproxy.html.es
-rw-rw-r-- 1 root admin 10000 3 Dec 12:07 tor-switchproxy.html.it
-rw-rw-r-- 1 root admin 10287 3 Dec 12:07 tor-switchproxy.html.pl
/Library/Receipts/Tor.pkg/Contents/Resources/en.lproj:
total 8
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 9 root admin 306 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 366 3 Dec 12:07 Description.plist
bash-3.2# ls -alR /Library/Receipts/torbutton.pkg
total 0
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 91 root admin 3094 21 Apr 08:44 ..
drwxrwxr-x 6 root admin 204 23 Jan 08:10 Contents
torbutton.pkg//Contents:
total 88
drwxrwxr-x 6 root admin 204 23 Jan 08:10 .
drwxrwxr-x 3 root admin 102 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 35293 3 Dec 12:07 Archive.bom
-rw-rw-r-- 1 root admin 1336 23 Jan 08:10 Info.plist
-rw-rw-r--@ 1 root admin 9 3 Dec 12:07 PkgInfo
drwxrwxr-x 4 root admin 136 23 Jan 08:10 Resources
torbutton.pkg//Contents/Resources:
total 8
drwxrwxr-x 4 root admin 136 23 Jan 08:10 .
drwxrwxr-x 6 root admin 204 23 Jan 08:10 ..
drwxrwxr-x 3 root admin 102 23 Jan 08:10 en.lproj
-rw-rw-r--@ 1 root admin 17 3 Dec 12:07 package_version
torbutton.pkg//Contents/Resources/en.lproj:
total 8
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 4 root admin 136 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 389 3 Dec 12:07 Description.plist
bash-3.2# ls -alR /Library/Receipts/Vidalia.pkg/
total 0
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 90 root admin 3060 21 Apr 08:45 ..
drwxrwxr-x 6 root admin 204 23 Jan 08:10 Contents
/Library/Receipts/Vidalia.pkg//Contents:
total 88
drwxrwxr-x 6 root admin 204 23 Jan 08:10 .
drwxrwxr-x 3 root admin 102 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 35970 3 Dec 12:07 Archive.bom
-rw-rw-r-- 1 root admin 1585 23 Jan 08:10 Info.plist
-rw-rw-r--@ 1 root admin 9 3 Dec 12:07 PkgInfo
drwxrwxr-x 5 root admin 170 23 Jan 08:10 Resources
/Library/Receipts/Vidalia.pkg//Contents/Resources:
total 16
drwxrwxr-x 5 root admin 170 23 Jan 08:10 .
drwxrwxr-x 6 root admin 204 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 379 3 Dec 12:07 TokenDefinitions.plist
drwxrwxr-x 3 root admin 102 23 Jan 08:10 en.lproj
-rw-rw-r--@ 1 root admin 17 3 Dec 12:07 package_version
/Library/Receipts/Vidalia.pkg//Contents/Resources/en.lproj:
total 8
drwxrwxr-x 3 root admin 102 23 Jan 08:10 .
drwxrwxr-x 5 root admin 170 23 Jan 08:10 ..
-rw-rw-r-- 1 root admin 368 3 Dec 12:07 Descrip
[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]
Andrew Lewman
Andrew Lewman
https://gitlab.torproject.org/legacy/trac/-/issues/974
TBB 1.1.13-dev contains invalid preferences
2020-06-13T14:01:42Z
Andrew Lewman
TBB 1.1.13-dev contains invalid preferences
it appears that invalidprefs.js file is being generated, which is overriding some of
the prefs we set
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
it appears that invalidprefs.js file is being generated, which is overriding some of
the prefs we set
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
Andrew Lewman
Andrew Lewman
https://gitlab.torproject.org/legacy/trac/-/issues/975
Torbutton prevents PKCS#12 import/export
2020-06-16T01:27:28Z
Trac
Torbutton prevents PKCS#12 import/export
If I activate torbutton, I cannot import or export personal PKCS#12 certificates. Firefox tells me I that an unknown error happened. If I deactivate torbutton and restart firefox, everything works fine. Firefox is 3.0.8 on Ubuntu 8.10 AM...
If I activate torbutton, I cannot import or export personal PKCS#12 certificates. Firefox tells me I that an unknown error happened. If I deactivate torbutton and restart firefox, everything works fine. Firefox is 3.0.8 on Ubuntu 8.10 AMD64.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: kurti
https://gitlab.torproject.org/legacy/trac/-/issues/976
complete nonfunction on fresh install
2010-06-22T23:28:33Z
Trac
complete nonfunction on fresh install
System:
MS XP home V 2002 SP2
Firefox/3.1b3 GTB5
XML Parsing Error: undefined entity
Location: jar:file:///C:/Program%20Files/Mozilla%20Firefox%203.1%20Beta%203/chrome/toolkit.jar!/content/global/netError.xhtml
Line Number 60, C...
System:
MS XP home V 2002 SP2
Firefox/3.1b3 GTB5
XML Parsing Error: undefined entity
Location: jar:file:///C:/Program%20Files/Mozilla%20Firefox%203.1%20Beta%203/chrome/toolkit.jar!/content/global/netError.xhtml
Line Number 60, Column 12: <title>&loadError.label;</title>
-----------!^
When I turn it on and try to go to Google homepage via any means I get the above error. All results for any website similar to above.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: Aerospaced
https://gitlab.torproject.org/legacy/trac/-/issues/977
buf_shrink_freelists: Assertion !n_to_free failed
2020-06-13T14:01:44Z
Roger Dingledine
buf_shrink_freelists: Assertion !n_to_free failed
dr|z3d> Nasty Tor crash: "May 05 21:08:52.448 [Error] Bug: buffers.c:281:
buf_shrink_freelists: Assertion !n_to_free failed; aborting."
It was 0.2.1.14-rc on Windows.
"DNSPort and 1 hidden service. Run from Vidalia, so ControlPort was ...
dr|z3d> Nasty Tor crash: "May 05 21:08:52.448 [Error] Bug: buffers.c:281:
buf_shrink_freelists: Assertion !n_to_free failed; aborting."
It was 0.2.1.14-rc on Windows.
"DNSPort and 1 hidden service. Run from Vidalia, so ControlPort was set too.
A few IRC connections, and probably idle other than that.
[Automatically added by flyspray2trac: Operating System: All]
https://gitlab.torproject.org/legacy/trac/-/issues/978
DirPortFrontPage gives 503 on loaded dirmirror
2020-06-13T14:01:44Z
Sebastian Hahn
DirPortFrontPage gives 503 on loaded dirmirror
When configuring DirPortFrontPage, a loaded mirror will return a 503
consistently when the DirPort is hit. A browser will simply display a
white page and not indicate the error condition at all, so the output
can be surprising to the ave...
When configuring DirPortFrontPage, a loaded mirror will return a 503
consistently when the DirPort is hit. A browser will simply display a
white page and not indicate the error condition at all, so the output
can be surprising to the average user. If we cannot "fix" this, at least
warning the user is probably a sane idea.
[Automatically added by flyspray2trac: Operating System: All]
https://gitlab.torproject.org/legacy/trac/-/issues/979
Torbutton not disabling javascript
2010-07-29T16:21:38Z
Trac
Torbutton not disabling javascript
Torbutton does not disable javascript when I turn it on
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Devolve
Torbutton does not disable javascript when I turn it on
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Devolve
https://gitlab.torproject.org/legacy/trac/-/issues/980
Request the addition of htaccess into the /dist directory
2020-06-13T17:18:18Z
Trac
Request the addition of htaccess into the /dist directory
Please add .htaccess
"Options +Indexes"
When rsync is run according to the instructions on the mirror instructions page, because .htaccess is not
present on the sync origin, it is deleted in the target.
Thanks, Jon
[Automatically ad...
Please add .htaccess
"Options +Indexes"
When rsync is run according to the instructions on the mirror instructions page, because .htaccess is not
present on the sync origin, it is deleted in the target.
Thanks, Jon
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: JonCharge
https://gitlab.torproject.org/legacy/trac/-/issues/981
Proxy Info does not get cleared
2020-06-13T14:01:44Z
Trac
Proxy Info does not get cleared
I entered a proxy setting for tor during a visit to an office. Once I left that office, I could no longer connect to tor.
The error message is that it's still trying to find the proxy for https settings, and the server doesn't exist
(n...
I entered a proxy setting for tor during a visit to an office. Once I left that office, I could no longer connect to tor.
The error message is that it's still trying to find the proxy for https settings, and the server doesn't exist
(nor does it resolve)
[Automatically added by flyspray2trac: Operating System: Windows Vista]
**Trac**:
**Username**: laxamar
https://gitlab.torproject.org/legacy/trac/-/issues/982
Crash in closing tls connection
2020-06-13T14:01:51Z
Trac
Crash in closing tls connection
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 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**: neoeinstein
Tor: 0.2.2.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/983
Abort crash in libcrypto malloc during onion handshake
2020-06-13T14:01:56Z
Trac
Abort crash in libcrypto malloc during onion handshake
Occurred after ~15 hours of uptime on an x86_64 box.
I keep all cores archived, so if you have requests for me
to run against the core, let me know.
"""
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv...
Occurred after ~15 hours of uptime on an x86_64 box.
I keep all cores archived, so if you have requests for me
to run against the core, let me know.
"""
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 6, Aborted.
[New process 3611]
[New process 19395]
[New process 3612]
[New process 3614]
[New process 3613]
#0 0x00007fd0ea7cbfb5 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00007fd0ea7cbfb5 in raise () from /lib/libc.so.6
#1 0x00007fd0ea7cdbc3 in abort () from /lib/libc.so.6
#2 0x00007fd0ea80b228 in ?? () from /lib/libc.so.6
#3 0x00007fd0ea811b2c in ?? () from /lib/libc.so.6
#4 0x00007fd0ea8138f1 in ?? () from /lib/libc.so.6
#5 0x00007fd0ea815828 in malloc () from /lib/libc.so.6
#6 0x00007fd0eaf91f33 in CRYPTO_malloc () from /lib/libcrypto.so.0.9.8
#7 0x00007fd0eafbc18f in BN_mod_exp_mont_consttime () from /lib/libcrypto.so.0.9.8
#8 0x00007fd0eafd8925 in ?? () from /lib/libcrypto.so.0.9.8
#9 0x00007fd0eafd92ab in ?? () from /lib/libcrypto.so.0.9.8
#10 0x00000000004b1786 in crypto_pk_private_decrypt (env=<value optimized out>, to=<value optimized out>, from=0x8 <Address 0x8 out of bounds>,
fromlen=518, padding=<value optimized out>, warnOnFailure=0) at crypto.c:762
#11 0x00000000004b2a7e in crypto_pk_private_hybrid_decrypt (env=0x16207c0, to=0x7fd0e9633c30 "",
from=0x7fd0e9633e70 "s\214\235½aNàÇå¯\030\adlf\233\021\206\\+\035\203{h ëÈâ\203AÉ®?\225Ï¢éôA\232ÙREC¨ÿÚÜí>¨\003\226ÚÔCd0¢1\211û~ÎMÖ\213W\t¿WB\223põ\024Ï3>è:rÆ\036\234.\233Á(2C3É,,\224ìÅ&.\\\237ÝÑ\017I\r/⸺\207\032\225\002\205á_}0\206o\005JÊÆ\216\234Ò]÷ÿ\231Ïß¡¾çWz\223\213\215j®\026ÐY<ç/µ<½\037âón¨\026ôÚfZBc4\031\b\221±ál\217Ùõ8Ç}\032ägæÂ{*", fromlen=186, padding=60002, warnOnFailure=0) at crypto.c:989
#12 0x0000000000466b85 in onion_skin_server_handshake (
onion_skin=0x7fd0e9633e70 "s\214\235½aNàÇå¯\030\adlf\233\021\206\\+\035\203{h ëÈâ\203AÉ®?\225Ï¢éôA\232ÙREC¨ÿÚÜí>¨\003\226ÚÔCd0¢1\211û~ÎMÖ\213W\t¿WB\223põ\024Ï3>è:rÆ\036\234.\233Á(2C3É,,\224ìÅ&.\\\237ÝÑ\017I\r/⸺\207\032\225\002\205á_}0\206o\005JÊÆ\216\234Ò]÷ÿ\231Ïß¡¾çWz\223\213\215j®\026ÐY<ç/µ<½\037âón¨\026ôÚfZBc4\031\b\221±ál\217Ùõ8Ç}\032ägæÂ{*", private_key=0x16207c0, prev_private_key=0x0,
handshake_reply_out=0x7fd0e9633f30 "å\002õ\006(Gf.%1|cÛL? IÜ\204g\031\036Å\016½\217\234µå9\215uEàCʨ¾Íá©xð\201)\f\233Ó\020ÃÎ\037¶\0041Z",
key_out=0x7fd0e9633fd0 "ãJ(v|ÈßBdð-3v\005QÛ\202±\211\022\205J&\0247öI\233\027G¥\034ƶÇ\022,#ÆïDJ*þ®,\vRú\217ûU\005$s>=MtßWßõò²ú\022\217:ÍHú",
key_out_len=72) at onion.c:232
#13 0x000000000044062a in cpuworker_main (data=<value optimized out>) at cpuworker.c:273
#14 0x00000000004a6ab5 in tor_pthread_helper_fn (_data=0x1620220) at compat.c:1694
#15 0x00007fd0ead163ba in start_thread () from /lib/libpthread.so.0
#16 0x00007fd0ea87efcd in clone () from /lib/libc.so.6
#17 0x0000000000000000 in ?? ()
"""
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: neoeinstein
https://gitlab.torproject.org/legacy/trac/-/issues/984
Tor using forbidden nodes
2020-06-13T14:01:56Z
Trac
Tor using forbidden nodes
Hello.
I have this in my torcc:
ExcludeNodes {us},{gb},{cn},{au}
but my log is showing this kind of lines:
[Warning] Requested exit node 'thegoddamnpenisblue' is in ExcludeNodes, or ExcludeExitNodes, using anyway.
[Warning] Requested exi...
Hello.
I have this in my torcc:
ExcludeNodes {us},{gb},{cn},{au}
but my log is showing this kind of lines:
[Warning] Requested exit node 'thegoddamnpenisblue' is in ExcludeNodes, or ExcludeExitNodes, using anyway.
[Warning] Requested exit node 'userbw20prfpis' is in ExcludeNodes, or ExcludeExitNodes, using anyway.
I'm also running as a relay, but this happened also when I was running Tor as client-only.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: G-Lo
0.2.1.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/985
libevent error - Tor not starting - 0.2.0.26-rc works!
2020-06-13T14:01:56Z
Trac
libevent error - Tor not starting - 0.2.0.26-rc works!
Temporarily, I have to use 0.2.0.26-rc (r14597) until the libevent error is fixed as in:
https://bugs.torproject.org/flyspray/index.php?do=details&id=792
I went back one revision at a time from this ftp server:
ftp://ftp.osmirror.nl/p...
Temporarily, I have to use 0.2.0.26-rc (r14597) until the libevent error is fixed as in:
https://bugs.torproject.org/flyspray/index.php?do=details&id=792
I went back one revision at a time from this ftp server:
ftp://ftp.osmirror.nl/pub/tor/win32/
[Automatically added by flyspray2trac: Operating System: Windows Vista]
**Trac**:
**Username**: 80063r
https://gitlab.torproject.org/legacy/trac/-/issues/986
Activating Torbutton in Select Tabs
2018-03-10T14:50:52Z
Trac
Activating Torbutton in Select Tabs
Whenever Torbutton is activated, the whole Firefox session is gripped under the tight reign of the Tor network. Some users may want use Tor on particular sites where their privacy is important, but continue browsing the other sites norma...
Whenever Torbutton is activated, the whole Firefox session is gripped under the tight reign of the Tor network. Some users may want use Tor on particular sites where their privacy is important, but continue browsing the other sites normally. Or simply because it is slower than normal connections, they might want to limit it to the particular sites or connections where anonymity is prioritized.
I propose an option which allows the user to activate Torbutton only in tabs or windows they want access using the Tor network. Simply by directing the connection of the Torbutton activated tabs to the Tor software, the user can enjoy normal connection beside it.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Oxwil
https://gitlab.torproject.org/legacy/trac/-/issues/987
eventdns can't strerror() on windows?
2020-06-13T14:01:57Z
Roger Dingledine
eventdns can't strerror() on windows?
Mai 24 12:59:01.875 [Warnung] eventdns: Error Unknown error (10054) while reading request.
the line in question seems to be:
log(EVDNS_LOG_WARN, "Error %s (%d) while reading request.",
strerror(err), err);
Do we want a Windows-sty...
Mai 24 12:59:01.875 [Warnung] eventdns: Error Unknown error (10054) while reading request.
the line in question seems to be:
log(EVDNS_LOG_WARN, "Error %s (%d) while reading request.",
strerror(err), err);
Do we want a Windows-style tor_socket_strerror() wrapper here?
(and probably a variety of other places in eventdns)
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
https://gitlab.torproject.org/legacy/trac/-/issues/988
Different TLS certs for incoming vs outgoing
2020-06-13T14:01:58Z
Roger Dingledine
Different TLS certs for incoming vs outgoing
We should learn to present different TLS certs for incoming connections
vs outgoing connections.
The motivating example is bridges. They want to show the same identity
to people who connect, yet behave like clients when they connect to ...
We should learn to present different TLS certs for incoming connections
vs outgoing connections.
The motivating example is bridges. They want to show the same identity
to people who connect, yet behave like clients when they connect to other
relays (e.g. change keys when they change IP addresses).
(Of course, this change would provide a new way to test for bridges: if a
Tor connects to you, connect back and see if the cert is different. But at
least that's an active test that requires the bridge to connect to you
first. But then, the attack I describe above only kicks in when the bridge
connects to you. Hm.)
[Automatically added by flyspray2trac: Operating System: All]
Tor: 0.2.2.x-final
https://gitlab.torproject.org/legacy/trac/-/issues/989
Proxy-excluded urls should be excluded from Torbutton's manipulations.
2018-03-11T07:23:53Z
Trac
Proxy-excluded urls should be excluded from Torbutton's manipulations.
When Torbutton's state is toggled in Firefox, it locks down page interaction and
forces the user to reload the page manually. This includes urls that have
been excluded from the proxy in Firefox's advanced network configuration
settings...
When Torbutton's state is toggled in Firefox, it locks down page interaction and
forces the user to reload the page manually. This includes urls that have
been excluded from the proxy in Firefox's advanced network configuration
settings.
It would be helpful if Torbutton respected proxy-excluded urls and left their
state alone.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: zed
https://gitlab.torproject.org/legacy/trac/-/issues/990
Option for Warning dialog(s) to "remember this and don't ask me again until t...
2018-03-11T07:24:33Z
Trac
Option for Warning dialog(s) to "remember this and don't ask me again until this preference changes"
If Torbutton's internal test fails, the user is alerted every time Torbutton is toggled that the test failed.
It might be useful to add a tickbox to the dialog (for advanced users) to dismiss the dialog completely
until those settings ...
If Torbutton's internal test fails, the user is alerted every time Torbutton is toggled that the test failed.
It might be useful to add a tickbox to the dialog (for advanced users) to dismiss the dialog completely
until those settings change.. "Remember my answer and don't ask me again unless these settings change".
A concomitant about:config tweak to set this state might also be handy.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: zed
https://gitlab.torproject.org/legacy/trac/-/issues/991
Unit tests broken in Tor master
2020-06-13T14:01:59Z
Sebastian Hahn
Unit tests broken in Tor master
<sebastian> unit tests in master are broken
<sebastian> 5f03d6c547629af73dea2cfdaf888bc3a7caab5d is first bad commit
<sebastian> commit 5f03d6c547629af73dea2cfdaf888bc3a7caab5d
<sebastian> Author: Karsten Loesing <karsten.loesing@gmx.net...
<sebastian> unit tests in master are broken
<sebastian> 5f03d6c547629af73dea2cfdaf888bc3a7caab5d is first bad commit
<sebastian> commit 5f03d6c547629af73dea2cfdaf888bc3a7caab5d
<sebastian> Author: Karsten Loesing <karsten.loesing@gmx.net>
<sebastian> Date: Tue May 26 21:41:42 2009 +0200
<sebastian> I'll look into fixing that tomorrow night if no-one else gets around to it
unit test output:
============================== geoip
..............
File test.c: line 4630 (test_geoip): Assertion failed: ("zz=24,ab=16,xy=8"==s)
("zz=24,ab=16,xy=8" != "ab=16")
make: *** [test] Error 1
[Automatically added by flyspray2trac: Operating System: All]
https://gitlab.torproject.org/legacy/trac/-/issues/992
Torbutton reset toolbar's settings
2020-06-12T23:42:18Z
Trac
Torbutton reset toolbar's settings
Toolbar settings and icons are always resets to defaults when Torbutton add-on is enabled.
When it's disabled everything goes fine.
I have already encoutered this problem with an other add-on. It's a conflict with TabMixPlus.
There is a...
Toolbar settings and icons are always resets to defaults when Torbutton add-on is enabled.
When it's disabled everything goes fine.
I have already encoutered this problem with an other add-on. It's a conflict with TabMixPlus.
There is a simple way to fix it by not running initialization and try to access gBrowser until the window is loaded.
Here's the fix for the other add-on (if it can help) : http://bazaar.launchpad.net/~asac/ubufox/main/revision/148/content/alternatePlugins.js
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: scaler
https://gitlab.torproject.org/legacy/trac/-/issues/993
Add ExitPolicy by country
2020-06-13T14:54:08Z
Trac
Add ExitPolicy by country
Reason: more and more country are voting laws to censor internet: browsing, P2P,...
As browsing would probably be banned at your country's DNS level, there's not big risk of being charge of abuse,
because if you serve as exit node to htt...
Reason: more and more country are voting laws to censor internet: browsing, P2P,...
As browsing would probably be banned at your country's DNS level, there's not big risk of being charge of abuse,
because if you serve as exit node to http://offending.site.com and this site is banned by your own country, your
local DNS would direct you to somewhere else or give an error. The TOR Client would then get this wrong answer but
the exit node would not be charged of anything.
However, you could appear to be involved in illegal P2P.
Even if TOR natively filters out well known P2P ports, anyone can set his P2P software to port 443, port 80,...
So being able to filter out by country (usually your own country) is important to prevent this kind of abuse.
That's because laws are applicable generally country by country. To check that you are actually doing P2P
(as an exit node) governments have to simulate a P2P client and connect to you.
This would most probably be done in your own country otherwise charges could easily be dismissed during a trial.
So banning your own country can be useful, and not too hard to implement, as it is already done with ExitNodes.
An alternative I tried: I blocked individual IP ranges. But unfortunately that doen't seem to work and has
quite nasty side effects.
I tried it out taking FR (France) IP addresses as example.
FR ranges of IP give around 19,7K ranges
Feeding 19,7K lines of
ExitPolicy reject so.me.fr.ip/mask
result is:
- TOR consuming 100% CPU (on 1 CPU of a Dual core 2,4GHZ) for around 1 min at startup
- Vidalia doing same thing
- /var/log/tor/log contains at lot of messages:
[warn] router_dump_router_to_string(): Bug: descriptor policy_write_item ran out of room!
[warn] router_rebuild_descriptor(): Bug: Couldn't generate router descriptor.
- ps -aux | grep tor
shows that the TOR process is at 98,8% memory (hence the previous "bug" messages I suppose)
- complained at startup about raising file handles (ulimit) to 32767 [this might be unrelated]
Quite clearly, feeding into TOR around 20K ranges of blocked IP wasn't a good idea, and wasn't in the architectural
design of TOR. I do also guess TOR my advertise to other nodes what it is blocking (is it... I admit I didn't read
all the protocol !) and blocking so many ranges could result in a lot of useless traffic.
So obviously, the tricky part would be to make an evolution to the protocol just to tell other nodes your
blocking (or allowing) on a specific country code.
Other altenative: TOR could also be blocking/allowing on a protocol (as Wireshark can do) and not on a ports,
which is not very reliable. This could be more difficult as this type of code is not already in TOR. Depending on the
level of the protocol you specify than could be quite tricky.
(Isn't WireShark Open Source, could be an inspiration for coding such a feature).
Severity: I put medium, as if every TOR exit node is charged by it's own country's authority, there will be less exit
nodes and this could lead to severe network congestion.
(I did personnaly revert to entry-middlenode, and removed my accept *:80, *:443)
Summary:
- Feature 1:
ExitPolicy reject {fr}, allow {ca}
- Feature 2:
ExitPolicy allow [HTTP], reject [FTP]
(In fact WireShark recognises HTTP traffic but it you cannot set a capture filter on this criteria, so such a
"high level" protocol could be difficult to track properly)
//
Configuration: Ubuntu 8.10 - 64bits - TOR 0.2.0.34-1~intrepid from ppa.launchpad.net/e-stealth/ubuntu
Vidalia 0.1.8 from same repository
//
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: Zakhar
Tor: unspecified
https://gitlab.torproject.org/legacy/trac/-/issues/994
Tor check gives false negatives for exits that disallow port 80
2020-06-13T17:18:19Z
Sebastian Hahn
Tor check gives false negatives for exits that disallow port 80
: karsten: that can't be the (only) bug. Remember that
email we got a while back? It claimed that tor.sebastianhahn.net wasn't an
exit, but it had been running (and been included in the consensus) for 40 days
: the reason for that was si...
: karsten: that can't be the (only) bug. Remember that
email we got a while back? It claimed that tor.sebastianhahn.net wasn't an
exit, but it had been running (and been included in the consensus) for 40 days
: the reason for that was simple
: # Exit check to check.torproject.org or your exit checking website
: my $dstip = "209.237.247.217";
: my $dstport = 80;
: (and I just realized now)
: I don't exit to 80
: but check.tp.o tests whether you can exit to it on port 80
: So my node will always be a false negative
: That's clearly a bug in check
[Automatically added by flyspray2trac: Operating System: All]
https://gitlab.torproject.org/legacy/trac/-/issues/995
check.tp.o reports false negatives
2020-06-13T17:18:19Z
Karsten Loesing
check.tp.o reports false negatives
12:35:01 < someuser> hello. is the tor check based on wether the IP is on
tor exit node list?
12:36:28 < someuser> I am getting "not using tor" but the indicated IP is
not of my ISP
12:37:37 < karsten> what IP does it tell you you're usi...
12:35:01 < someuser> hello. is the tor check based on wether the IP is on
tor exit node list?
12:36:28 < someuser> I am getting "not using tor" but the indicated IP is
not of my ISP
12:37:37 < karsten> what IP does it tell you you're using?
12:37:53 < someuser> 78.97.155.194
12:38:12 < karsten> that's listed as exit node.
12:38:31 < karsten> and check.torproject.org tells you you're not using
tor?
12:38:37 < someuser> yes
12:41:39 < someuser> it was about 20 minutes ago
12:41:58 < karsten> ok, that means around 10:21 UTC.
12:44:10 < karsten> around 10:20 should be fine. the question is only what
data basis (directory consensus) is used by check.tp.o.
12:44:39 < karsten> i think ioerror_ will have a look. ioerror_, i can help
with descriptors of that time.
12:53:02 < someuser> I am using Lenny with Tor version 0.2.0.34 (r18423)
12:53:39 < someuser> it works fine normally
12:55:49 < someuser> I tried out the Tor button before on Iceweasel 2 and
the tor state was inverted as it went trough tor when it said it was
disabled and vice-versa
12:56:03 < karsten> yeah, i don't think it's a problem on your side. i'm
not sure why check would think that node isn't an exit.
12:56:20 < someuser> so I use a normal install and proxy settings in
browser
12:58:15 < karsten> that node permits exiting to check.tp.o. the only thing
is that the first time it was included in a consensus was 09:00 UTC. maybe
check doesn't update its consensus every hour?
13:02:29 < karsten> (which would mean it might still work with the 08:00
UTC consensus where that node wasn't listed.)
13:22:30 < Sebastian> for someuser's problem, I wonder if it's a problem
with check, or one with the dnsel
13:23:35 < karsten> someuser's node permits both 80 and 443.
13:23:40 < Sebastian> I know, I checked
[Automatically added by flyspray2trac: Operating System: All]
Jacob Appelbaum
Jacob Appelbaum
https://gitlab.torproject.org/legacy/trac/-/issues/996
tor-0.2.1.14-rc dies on SIGILL shortly after receiving SIGHUP
2020-06-13T14:02:01Z
Trac
tor-0.2.1.14-rc dies on SIGILL shortly after receiving SIGHUP
This bug report submitted on behalf of Scott.
On two successive tor runs as a relay, tor terminated abnormally on
SIGILL after receiving a SIGHUP. The operating system is FreeBSD
7-STABLE, and tor is 0.2.1.14-rc. A SIGHUP was sent to...
This bug report submitted on behalf of Scott.
On two successive tor runs as a relay, tor terminated abnormally on
SIGILL after receiving a SIGHUP. The operating system is FreeBSD
7-STABLE, and tor is 0.2.1.14-rc. A SIGHUP was sent to tor, which
issued the following messages to /var/log/notices.log in the second
case.
Jun 04 10:36:10.957 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Jun 04 10:36:10.966 [notice] Tor 0.2.1.14-rc (r19307) opening log file.
Jun 04 10:36:10.966 [warn] Can't log to stdout with RunAsDaemon set; skipping stdout
Jun 04 10:36:10.966 [warn] Can't log to stdout with RunAsDaemon set; skipping stdout
It then terminated on a SIGILL, leaving a tor.core file in /var/db/tor,
and the FreeBSD kernel noted the following in /var/log/messages.
Jun 4 10:36:12 hellas kernel: pid 16788 (tor), uid 256: exited on signal 4 (core dumped)
The first case did exactly the same with, of course, different date and
timestamps and a different pid in the messages. In each case, I
appended the date to the name of the tor.core file to prevent it from
being overwritten/replaced by any later occurrence of this crash. The
two tor.core files do have different sizes:
-rw------- 1 _tor _tor 30973952 Jun 3 03:28 tor.core.03jun2009
-rw------- 1 _tor _tor 68128768 Jun 4 10:36 tor.core.04jun2009
gdb backtraces are shown for each tor.core file in the typescript file
below.
Script started on Fri Jun 5 00:40:45 2009
hellas# gdb /usr/local/bin/tor tor.core.03jun2009
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
Core was generated by `tor'.
Program terminated with signal 4, Illegal instruction.
Reading symbols from /lib/libz.so.4...done.
Loaded symbols for /lib/libz.so.4
Reading symbols from /usr/local/lib/libevent-1.4.so.3...done.
Loaded symbols for /usr/local/lib/libevent-1.4.so.3
Reading symbols from /usr/lib/libssl.so.5...done.
Loaded symbols for /usr/lib/libssl.so.5
Reading symbols from /lib/libcrypto.so.5...done.
Loaded symbols for /lib/libcrypto.so.5
Reading symbols from /lib/libthr.so.3...done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /usr/lib/librt.so.1...done.
Loaded symbols for /usr/lib/librt.so.1
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x080b0f1e in policies_parse_from_options (options=0x3499bc00)
at policies.c:431
431 if (load_policy_from_option(options->DirPolicy, &dir_policy, -1) < 0)
[New Thread 0x34102030 (LWP 100195)]
[New Thread 0x34101f20 (LWP 100194)]
[New Thread 0x34101040 (LWP 100193)]
(gdb) bt
#0 0x080b0f1e in policies_parse_from_options (options=0x3499bc00)
at policies.c:431
#1 0x08068824 in options_act (old_options=0x34123400) at config.c:1298
#2 0x080697b6 in set_options (new_val=0x3499bc00, msg=0xbfbfe4a8)
at config.c:807
#3 0x0806a262 in options_init_from_string (
cf=0x344f1000 "## Configuration file for a typical Tor user\n## Last updated 8 October 2006 for Tor 0.1.2.3-alpha.\n## (May or may not work for older or newer versions of Tor.)\n##\n## Lines that begin with \"## \" try to"...,
command=0, command_arg=0x0, msg=0xbfbfe4a8) at config.c:4087
#4 0x0806a909 in options_init_from_torrc (argc=11, argv=0xbfbfe694)
at config.c:3961
#5 0x080a715c in signal_callback (fd=1, events=8, arg=Variable "arg" is not available.
) at main.c:1306
#6 0x33d81565 in event_base_loop () from /usr/local/lib/libevent-1.4.so.3
#7 0x33d81899 in event_loop () from /usr/local/lib/libevent-1.4.so.3
#8 0x080a936a in do_main_loop () at main.c:1435
#9 0x080a951d in tor_main (argc=11, argv=0xbfbfe694) at main.c:2060
#10 0x080e5422 in main (argc=100193, argv=0x0) at tor_main.c:30
(gdb) quit
hellas# gdb /usr/local/bin/tor tor.core.04jun2009
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
Core was generated by `tor'.
Program terminated with signal 4, Illegal instruction.
Reading symbols from /lib/libz.so.4...done.
Loaded symbols for /lib/libz.so.4
Reading symbols from /usr/local/lib/libevent-1.4.so.3...done.
Loaded symbols for /usr/local/lib/libevent-1.4.so.3
Reading symbols from /usr/lib/libssl.so.5...done.
Loaded symbols for /usr/lib/libssl.so.5
Reading symbols from /lib/libcrypto.so.5...done.
Loaded symbols for /lib/libcrypto.so.5
Reading symbols from /lib/libthr.so.3...done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /usr/lib/librt.so.1...done.
Loaded symbols for /usr/lib/librt.so.1
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x080b0f1e in policies_parse_from_options (options=0x37df1c00)
at policies.c:431
431 if (load_policy_from_option(options->DirPolicy, &dir_policy, -1) < 0)
[New Thread 0x34102030 (LWP 100195)]
[New Thread 0x34101f20 (LWP 100194)]
[New Thread 0x34101040 (LWP 100240)]
(gdb) bt
#0 0x080b0f1e in policies_parse_from_options (options=0x37df1c00)
at policies.c:431
#1 0x08068824 in options_act (old_options=0x34123400) at config.c:1298
#2 0x080697b6 in set_options (new_val=0x37df1c00, msg=0xbfbfe4b8)
at config.c:807
#3 0x0806a262 in options_init_from_string (
cf=0x37ece000 "## Configuration file for a typical Tor user\n## Last updated 8 October 2006 for Tor 0.1.2.3-alpha.\n## (May or may not work for older or newer versions of Tor.)\n##\n## Lines that begin with \"## \" try to"...,
command=0, command_arg=0x0, msg=0xbfbfe4b8) at config.c:4087
#4 0x0806a909 in options_init_from_torrc (argc=11, argv=0xbfbfe6a0)
at config.c:3961
#5 0x080a715c in signal_callback (fd=1, events=8, arg=Variable "arg" is not available.
) at main.c:1306
#6 0x33d81565 in event_base_loop () from /usr/local/lib/libevent-1.4.so.3
#7 0x33d81899 in event_loop () from /usr/local/lib/libevent-1.4.so.3
#8 0x080a936a in do_main_loop () at main.c:1435
#9 0x080a951d in tor_main (argc=11, argv=0xbfbfe6a0) at main.c:2060
#10 0x080e5422 in main (argc=100240, argv=0x0) at tor_main.c:30
(gdb) quit
hellas# exit
exit
Script done on Fri Jun 5 00:42:13 2009
The torrc file can be made available upon request if needed.
Comments:
I have no recollection of any prior version of tor failing in this
manner in response to a SIGHUP. It is very restricting not to dare to
send SIGHUPs at all with this version in order to avoid causing yet
another crash. I am considering reviving 0.2.1.13-alpha to regain
this functionality. I have built 0.2.1.15-rc, but am reluctant to
install and use it, given that this bug most likely still exists in
0.2.1.15-rc, whereas it didn't seem to happen in the earlier version.
Submitted (via Jon <scream@nonvocalscream.com>) by:
Scott Bennett <bennett@cs.niu.edu>
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: JonCharge
https://gitlab.torproject.org/legacy/trac/-/issues/997
Hidden services fail to load if you have a stale descriptor
2020-06-13T14:02:02Z
Roger Dingledine
Hidden services fail to load if you have a stale descriptor
Using git head.
In connection_ap_handshake_rewrite_and_attach(), we check
rend_cache_lookup_entry(). If >0 (meaning we have a rend descriptor),
we then evaluate:
/** How long after we receive a hidden service descriptor do we consider
...
Using git head.
In connection_ap_handshake_rewrite_and_attach(), we check
rend_cache_lookup_entry(). If >0 (meaning we have a rend descriptor),
we then evaluate:
/** How long after we receive a hidden service descriptor do we consider
* it valid? */
#define NUM_SECONDS_BEFORE_HS_REFETCH (60*15)
if (now - entry->received < NUM_SECONDS_BEFORE_HS_REFETCH) {
and if it's stale (we got it more than 15 minutes ago), we call
log_info(LD_REND, "Stale descriptor %s. Re-fetching.",
safe_str(conn->rend_data->onion_address));
rend_client_refetch_v2_renddesc(conn->rend_data);
However, in rend_client_refetch_v2_renddesc() we don't care whether
it's stale. Towards the top of the function we call:
if (rend_cache_lookup_entry(rend_query->onion_address, -1, &e) > 0) {
log_info(LD_REND, "We would fetch a v2 rendezvous descriptor, but we "
"already have that descriptor here. Not fetching.");
return;
}
So now that we don't try to fetch v0 rend descriptors, that means that
Tor simply times out on all socks requests to hidden services for which
we have a stale descriptor.
Presumably this is a bug on 0.2.1.x and 0.2.0.x too.
My original rend desc design was "if you have a fresh one, use it. If
you have one but it's stale, fetch a new one; then whether you get a new
one or no, use the one you have." We seem to have clobbered that design
in 0.2.0.20-rc (r13540) when we added support for v0 and v2 rend descs.
In any case, refetching after 15 minutes was cheap back in the days of
Tor 0.0.9, but is expensive now.
So the two extremes we have are:
1) connection_ap_handshake_rewrite_and_attach() which says "it's stale
after 15 minutes; try to fetch a new one if it's stale" and
2) /** Time period for which a v2 descriptor will be valid. */
#define REND_TIME_PERIOD_V2_DESC_VALIDITY (24*60*60)
Do we want something in between?
(Thanks to neoeinstein for tracking down the bug.)
[Automatically added by flyspray2trac: Operating System: All]
Tor: 0.2.2.x-final
Karsten Loesing
Karsten Loesing
https://gitlab.torproject.org/legacy/trac/-/issues/998
Torbutton prevents from exporting certificates
2011-01-21T17:39:49Z
Trac
Torbutton prevents from exporting certificates
While Torbutton is activated in my Firefox browser, exporting personal certificates becomes impossible.
Instead of displaying the passphrase dialog before exporting the PKCS#12 exchange file, an alert box states that
the certificate exp...
While Torbutton is activated in my Firefox browser, exporting personal certificates becomes impossible.
Instead of displaying the passphrase dialog before exporting the PKCS#12 exchange file, an alert box states that
the certificate export fails for an "unknown reason".
This problem appears only when the torbutton is installed and enabled in the session. It disappear when the torbutton is
disabled (or uninstalled, of course). It impacts only the personal (with private key) certificate, not root certificates.
In order to reproduce the problem, you should import a personal email certificate from thawte.com (it's free)
or cacert.org (it's free too, but need to import a root certificate to recognize cacert).
At least, you should update the FAQ / troubleshooting topic advising to disable temporarily torbutton when user has to
export his certificates.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: mr_mzi
https://gitlab.torproject.org/legacy/trac/-/issues/999
automatically activate Tor for specific sites
2010-06-22T23:35:30Z
Trac
automatically activate Tor for specific sites
It would be convenient if there could be a list made of sites to automatically use Tor for, regardless of whether Torbutton is on for all sites.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: a_...
It would be convenient if there could be a list made of sites to automatically use Tor for, regardless of whether Torbutton is on for all sites.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: a_thing
https://gitlab.torproject.org/legacy/trac/-/issues/1000
Latest maint-0.2.1 git update fails compile
2020-06-13T14:02:03Z
Trac
Latest maint-0.2.1 git update fails compile
Here was the latest update message:
From git://git.torproject.org/git/tor
bd0eaa0..3a5259e maint-0.2.0 -> origin/maint-0.2.0
c50098f..8453263 maint-0.2.1 -> origin/maint-0.2.1
358efe1..74bf885 master -> origin/master
Upda...
Here was the latest update message:
From git://git.torproject.org/git/tor
bd0eaa0..3a5259e maint-0.2.0 -> origin/maint-0.2.0
c50098f..8453263 maint-0.2.1 -> origin/maint-0.2.1
358efe1..74bf885 master -> origin/master
Updating 358efe1..74bf885
make failed, make clean + make failed and make clean + ./autogen.sh + make failed with the following:
gcc -g -O2 -Wall -g -O2 -fno-strict-aliasing -L/usr/pkg/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -o tor buffers.o circuitbuild.o circuitlist.o circuituse.o command.o config.o connection.o connection_edge.o connection_or.o control.o cpuworker.o directory.o dirserv.o dirvote.o dns.o dnsserv.o geoip.o hibernate.o main.o networkstatus.o onion.o policies.o reasons.o relay.o rendcommon.o rendclient.o rendmid.o rendservice.o rephist.o router.o routerlist.o routerparse.o eventdns.o config_codedigest.o tor_main.o ../common/libor.a ../common/libor-crypto.a -lz -levent -lssl -lcrypto -lpthread
config.o: In function `init_libevent':
/usr/local/src/tor/src/or/config.c:4810: undefined reference to `configure_libevent_logging'
/usr/local/src/tor/src/or/config.c:4814: undefined reference to `suppress_libevent_log_msg'
/usr/local/src/tor/src/or/config.c:4816: undefined reference to `tor_check_libevent_header_compatibility'
/usr/local/src/tor/src/or/config.c:4818: undefined reference to `tor_libevent_initialize'
/usr/local/src/tor/src/or/config.c:4820: undefined reference to `suppress_libevent_log_msg'
/usr/local/src/tor/src/or/config.c:4822: undefined reference to `tor_libevent_get_method'
/usr/local/src/tor/src/or/config.c:4822: undefined reference to `tor_check_libevent_version'
/usr/local/src/tor/src/or/config.c:4826: undefined reference to `tor_libevent_get_version_str'
/usr/local/src/tor/src/or/config.c:4827: undefined reference to `tor_libevent_get_method'
dns.o: In function `dns_launch_correctness_checks':
/usr/local/src/tor/src/or/dns.c:1571: undefined reference to `tor_evtimer_new'
main.o: In function `handle_signals':
/usr/local/src/tor/src/or/main.c:1741: undefined reference to `tor_libevent_get_base'
/usr/local/src/tor/src/or/main.c:1741: undefined reference to `tor_evsignal_new'
main.o: In function `connection_start_reading_from_linked_conn':
/usr/local/src/tor/src/or/main.c:423: undefined reference to `tor_libevent_get_base'
main.o: In function `connection_add':
/usr/local/src/tor/src/or/main.c:136: undefined reference to `tor_libevent_get_base'
/usr/local/src/tor/src/or/main.c:136: undefined reference to `tor_event_new'
/usr/local/src/tor/src/or/main.c:138: undefined reference to `tor_libevent_get_base'
/usr/local/src/tor/src/or/main.c:138: undefined reference to `tor_event_new'
main.o: In function `second_elapsed_callback':
/usr/local/src/tor/src/or/main.c:1166: undefined reference to `tor_libevent_get_base'
/usr/local/src/tor/src/or/main.c:1166: undefined reference to `tor_evtimer_new'
main.o: In function `do_main_loop':
/usr/local/src/tor/src/or/main.c:1450: undefined reference to `tor_libevent_get_base'
/usr/local/src/tor/src/or/main.c:1458: undefined reference to `tor_libevent_get_method'
*** Error code 1
Stop.
make: stopped in /usr/local/src/tor/src/or
*** Error code 1
Stop.
make: stopped in /usr/local/src/tor/src
*** Error code 1
Stop.
make: stopped in /usr/local/src/tor
*** Error code 1
Stop.
make: stopped in /usr/local/src/tor
[Automatically added by flyspray2trac: Operating System: BSD]
**Trac**:
**Username**: yancm
https://gitlab.torproject.org/legacy/trac/-/issues/1001
tor git master from bdd5785f075d89123f6ac8110ea86f31981ae3b1
2020-06-13T14:02:03Z
Andrew Lewman
tor git master from bdd5785f075d89123f6ac8110ea86f31981ae3b1
Tor from git master ( bdd5785f075d89123f6ac8110ea86f31981ae3b1) crashes with:
Jun 15 23:17:31.845 [Debug] connection_handle_write(): After TLS write of 512: 0 read, 586 written
Jun 15 23:17:31.846 [Debug] connection_or_flush_from_firs...
Tor from git master ( bdd5785f075d89123f6ac8110ea86f31981ae3b1) crashes with:
Jun 15 23:17:31.845 [Debug] connection_handle_write(): After TLS write of 512: 0 read, 586 written
Jun 15 23:17:31.846 [Debug] connection_or_flush_from_first_active_circuit(): Made a circuit inactive.
Jun 15 23:17:31.847 [Debug] conn_write_callback(): socket 87 wants to write.
Jun 15 23:17:31.847 [Debug] flush_chunk_tls(): flushed 512 bytes, 0 ready to flush, 0 remain.
Jun 15 23:17:31.848 [Debug] connection_handle_write(): After TLS write of 512: 0 read, 586 written
Jun 15 23:17:31.849 [Debug] conn_read_callback(): socket 39 wants to read.
Jun 15 23:17:31.849 [Debug] connection_read_to_buf(): 39: starting, inbuf_datalen 0 (0 pending in tls object). at_most 0.
Jun 15 23:17:31.850 [Debug] connection_read_to_buf(): After TLS read of 0: 0 read, 0 written
Jun 15 23:17:31.850 [Debug] connection_consider_empty_read_buckets(): global relayed read bucket exhausted. Pausing.
Jun 15 23:17:31.851 [Debug] connection_or_process_cells_from_inbuf(): 39: starting, inbuf_datalen 0 (0 pending in tls object).
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000001c
Crashed Thread: 0
Thread 0 Crashed:
0 tor 0x000d36c4 event_base_set + 26
1 tor 0x000d2aae tor_event_new + 78 (compat_libevent.c:119)
2 tor 0x000d2aef tor_evtimer_new + 47 (compat_libevent.c:126)
3 tor 0x0005f312 dns_launch_correctness_checks + 354 (dns.c:1571)
4 tor 0x0006b3b5 second_elapsed_callback + 1093 (main.c:1122)
5 tor 0x000d47a2 event_base_loop + 1087
6 tor 0x0006c712 do_main_loop + 386 (main.c:1454)
7 tor 0x0006c9ab tor_main + 91 (main.c:2075)
8 tor 0x00001aa2 _start + 216
9 tor 0x000019c9 start + 41
Thread 1:
0 libSystem.B.dylib 0x92d2eb96 recvfrom$NOCANCEL$UNIX2003 + 10
1 tor 0x000439e2 cpuworker_main + 114 (cpuworker.c:244)
2 tor 0x000bde63 tor_pthread_helper_fn + 67 (compat.c:1728)
3 libSystem.B.dylib 0x92d17155 _pthread_start + 321
4 libSystem.B.dylib 0x92d17012 thread_start + 34
Libevent 1.4.11 compiled as a universal binary.
[Automatically added by flyspray2trac: Operating System: OSX 10.5 Leopard]
Nick Mathewson
Nick Mathewson