Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:12:54Zhttps://gitlab.torproject.org/legacy/trac/-/issues/3887Tor Private Network Refuses to make circuits2020-06-13T14:12:54ZTracTor Private Network Refuses to make circuitsBasically TOR in a private environment is refusing to make circuits, it 100% and bootstraps fine and says a circuit is made then repeatedly says: [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
and
[warn] No a...Basically TOR in a private environment is refusing to make circuits, it 100% and bootstraps fine and says a circuit is made then repeatedly says: [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
and
[warn] No available nodes when trying to choose node. Failing.
The environment is in VMWare using a virtual switch. The operating systems being used are Ubuntu Server 10.04 for the DirectoryAuthority and Ubuntu Desktop 10.04 for all the Relay and Clients. 4 Relays are in use and one Client.
Directory Authority Debug File is available if you need this? I just need to Find out a way to get it from the server.
Relay 1 Debug Log File **http://pastebin.com/wRUVCAvU**
**Trac**:
**Username**: raidenxlhttps://gitlab.torproject.org/legacy/trac/-/issues/3641TOR high CPU then crashes2020-06-13T14:12:08ZTracTOR high CPU then crashesI've been using the Vidalia bundle for a while, changing to Polipo about 18 months ago. I use TOR to anonymize the connection to torrent trackers - not for the peer-to-peer connections! I seldom use Torbutton on FF, and it's been turned ...I've been using the Vidalia bundle for a while, changing to Polipo about 18 months ago. I use TOR to anonymize the connection to torrent trackers - not for the peer-to-peer connections! I seldom use Torbutton on FF, and it's been turned of for several days in case that was the problem.
The bundle started misbehaving a couple of weeks ago. I started getting lots of warnings about DNS resolution using Socks5, so I upgraded to the latest Vidalia bundle.
Now Tor starts out normally, but after anything from a few minutes to several hours the process starts hogging a CPU (>90%) and crashes after a few hours. Restarting it repeats the behaviour. I am still getting the DNS resolutiuon errors. The only application routing via Tor is uTorrent - I have been using an old build (v1.6) of this for many months without problem, so I am unsure what may have triggered the change
**Trac**:
**Username**: YorkshireJumboTor: 0.2.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/3880Tor Browser Ports are blocked in Iran2011-09-01T14:01:24ZTracTor Browser Ports are blocked in IranHello
Have a Good Time
I tried Tor Browser ,This program is very similar to the toonel.net
But , After running the tor software
This problem occurs : "The connection has timed out"
Unfortunately, Most provider companies (ISP) have been b...Hello
Have a Good Time
I tried Tor Browser ,This program is very similar to the toonel.net
But , After running the tor software
This problem occurs : "The connection has timed out"
Unfortunately, Most provider companies (ISP) have been blocked These ports in Iran,
like : 8118 , 8081 ,8909 ,8181 ,808 , 8088 And often unconventional ports !!
When I changed the port to another port will be disabled program
( I changed the port in both programs , Tor & FireFox )
I'm using Windows XP SP2 32 bit
Is there any solution to this problem ?
Please advise me how I can use ?
Thanks
Kind Regard
**Trac**:
**Username**: MehrdadMike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/3909Tor 0.2.2.32 no longer cross compile (to iOS)2020-06-13T14:12:58ZTracTor 0.2.2.32 no longer cross compile (to iOS)Since version 0.2.2.32 I can no longer cross compile Tor to iOS.
Configure step is fine, build step runs smooth up until the linking phase, from the build log:
```
...
arm-apple-darwin9-gcc -DHAVE_CONFIG_H -I. -I../.. ...
mv -f .deps/...Since version 0.2.2.32 I can no longer cross compile Tor to iOS.
Configure step is fine, build step runs smooth up until the linking phase, from the build log:
```
...
arm-apple-darwin9-gcc -DHAVE_CONFIG_H -I. -I../.. ...
mv -f .deps/config_codedigest.Tpo ...
rm -f libtor.a
ar cru libtor.a buffers.o ...
arm-apple-darwin9-ranlib libtor.a
...
```
as you can see, the program "ar" is called instead of "arm-apple-darwin9-ar" causing quite some problems as architectures are being mixed and matched ;-)
If I prepend to my $PATH an "ar" which is a symlink to "arm-apple-darwin9-ar" everything builds fine.
I can reproduce the behavior while cross compiling to iOS but I suppose it could happen with other architectures as no patches are needed to build the program under such operating system.
**Trac**:
**Username**: sid77Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/3923tor 0.2.2.32 dies in assert on reloading config when TrackExitHosts was used2020-06-13T14:13:00ZTractor 0.2.2.32 dies in assert on reloading config when TrackExitHosts was usedTor 0.2.2.32 dies in assert on reloading config or control/SETCONF TrackExitHosts=... when some exit hosts was tracked before.
Log:
```
Sep 04 xx:xx:xx.xxx [err] _tor_strndup(): Bug: util.c:226: _tor_strndup: Assertion n < SIZE_T_CEILING...Tor 0.2.2.32 dies in assert on reloading config or control/SETCONF TrackExitHosts=... when some exit hosts was tracked before.
Log:
```
Sep 04 xx:xx:xx.xxx [err] _tor_strndup(): Bug: util.c:226: _tor_strndup: Assertion n < SIZE_T_CEILING failed; aborting.
```
Backtrace:
```
#1 0xb7cb8811 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7cb9fb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0x081071e1 in _tor_strndup (s=0x85a0481 "exit", n=4294967295) at util.c:226
#4 0x080c3d73 in addressmap_clear_excluded_trackexithosts (options=0x84a6898)
at connection_edge.c:849
#5 0x080b45d0 in options_act (old_options=0x816ccf0) at config.c:1328
#6 0x080b5753 in set_options (new_val=0x84a6898, msg=0xbffffaf8)
at config.c:674
#7 0x080b5e91 in options_init_from_string (
cf=0x89ef858 "## Configuration file "...,
command=0, command_arg=0x0, msg=0xbffffaf8) at config.c:4279
#8 0x080b6325 in options_init_from_torrc (argc=1, argv=0xbffffd64)
at config.c:4153
#9 0x080500e7 in process_signal (sig=1) at main.c:1428
#10 0xb7f5ec23 in event_base_loop () from /usr/lib/libevent-2.0.so.5
...
```
Function addressmap_clear_excluded_trackexithosts seems broken in lines 845-850, strrchr(3) does not work like this.
Patch attached.
**Trac**:
**Username**: laruldanTor: 0.2.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/3930tor 0.2.2.32 crashes with SIGSEGV on SSL_CIPHER_get_name2020-06-13T14:13:02ZTractor 0.2.2.32 crashes with SIGSEGV on SSL_CIPHER_get_nameWhen running in daemon mode as a relay, tor crashes with a SIGSEV in in libssl.
Here the stack trace:
```
#0 0x40168b00 in SSL_CIPHER_get_name () from /lib/libssl.so.1.0.0
#1 0x000bdbb4 in tor_tls_client_is_using_v2_ciphers (ssl=<val...When running in daemon mode as a relay, tor crashes with a SIGSEV in in libssl.
Here the stack trace:
```
#0 0x40168b00 in SSL_CIPHER_get_name () from /lib/libssl.so.1.0.0
#1 0x000bdbb4 in tor_tls_client_is_using_v2_ciphers (ssl=<value optimized out>, address=0x3a0ed8 "[scrubbed]") at tortls.c:866
#2 0x000bde9c in tor_tls_handshake (tls=0x39ea38) at tortls.c:1294
#3 0x00077d98 in connection_tls_continue_handshake (conn=0x39f608) at connection_or.c:920
#4 0x0006e72c in connection_handle_read (conn=0x39f608) at connection.c:2610
#5 0x0001136c in conn_read_callback (fd=<value optimized out>, event=0, _conn=0x401765bc) at main.c:514
#6 0x401018a4 in event_base_loop () from /opt/lib/libevent-2.0.so.5
#7 0x0000e7b8 in do_main_loop () at main.c:1564
#8 0x0000ea70 in tor_main (argc=1, argv=<value optimized out>) at main.c:2226
#9 0x403159a0 in __libc_start_main () from /lib/libc.so.6
#10 0x0000d388 in _start ()
```
Plattform is a Synology DS211j: Linux 2.6.32.12 #1748 Wed Jun 29 11:44:24 CST 2011 armv5tel GNU/Linux synology_88f6281_211j
Client-only operation works fine.
**Trac**:
**Username**: monochromecTor: 0.2.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/4089Listening to wrong IP according to log (due to nic alias?)2020-06-13T14:13:24ZTracListening to wrong IP according to log (due to nic alias?)The log reads:
"Now checking whether ORPort A.B.172.47:9001 and DirPort A.B.172.47:9030 are reachable..."
But the torrc has:
ORListenAddress A.B.172.50
DirListenAddress A.B.172.50
After tor start it really does listen to A.B.172.50 an...The log reads:
"Now checking whether ORPort A.B.172.47:9001 and DirPort A.B.172.47:9030 are reachable..."
But the torrc has:
ORListenAddress A.B.172.50
DirListenAddress A.B.172.50
After tor start it really does listen to A.B.172.50 and not to the ip from the log.
The probable cause for this is the use of a physical eth0 with ip A.B.172.47 and an alias eth0:1 with A.B.172.50.
Running on Gentoo.
**Trac**:
**Username**: 4ZMhttps://gitlab.torproject.org/legacy/trac/-/issues/4151error message2020-06-13T14:13:35ZTracerror messageSep 30 12:41:28.033 [Warning] Your server (66.209.38.105:443) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
I am trying to set up a relay and get this message...Sep 30 12:41:28.033 [Warning] Your server (66.209.38.105:443) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
I am trying to set up a relay and get this message, can you advise on what needs to be done. I looked at my router setup and Upnp seems to be allowed, it might help if I knew what ORPORT stands for when checking my firewall settings. I am using dsl/broadband/wireless to connect to ISP and don't know if this is allowed with tor.
any help would be appreciated. vadalia 0.2.14 tor 2.2.32 bundle
**Trac**:
**Username**: JourneyOneTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/3892Controlport behavior changed in 0.2.2.32 - CookieAuthentication now required ...2020-06-13T14:12:55ZcypherpunksControlport behavior changed in 0.2.2.32 - CookieAuthentication now required to access control portCurrent and previous versions of the torrc file states that either a HashedControlPassword OR CookieAuthentication may be used to access tor's controlport.
From torrc
## If you enable the controlport, be sure to enable one of these
## ...Current and previous versions of the torrc file states that either a HashedControlPassword OR CookieAuthentication may be used to access tor's controlport.
From torrc
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
#CookieAuthentication 1
After upgrading from 0.2.1.26 to 0.2.2.32, tor now requires that CookieAuthentication be enabled to access the ControlPort. Upon starting Vidalia after the tor upgrade, an error message was received asking for the location of the authentication cookie even when a HashControlPassword was specified in the torrc file.Tor: 0.2.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/3915Control listener on /var/run/tor/control2020-06-13T14:12:58ZTracControl listener on /var/run/tor/controlwhy does tor open a control listener on /var/run/tor/control? This looks like a bug to me.
log:
sudo /usr/sbin/tor -f /etc/tor/my-tor1rc
Sep 02 16:27:07.281 [notice] Tor v0.2.2.32 (git-84a279ff87e5bfea). This is experimental software. D...why does tor open a control listener on /var/run/tor/control? This looks like a bug to me.
log:
sudo /usr/sbin/tor -f /etc/tor/my-tor1rc
Sep 02 16:27:07.281 [notice] Tor v0.2.2.32 (git-84a279ff87e5bfea). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Sep 02 16:27:07.282 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good.
Sep 02 16:27:07.282 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9041
Sep 02 16:27:07.282 [notice] Opening DNS listener on 127.0.0.1:9031
Sep 02 16:27:07.282 [notice] Opening Control listener on 127.0.0.1:9051
Sep 02 16:27:07.282 [notice] Opening Control listener on /var/run/tor/control
Sep 02 16:27:07.283 [notice] Opening Control listener on /var/run/tor/my-tor1-control-socket
torrc:
ControlSocket /var/run/tor/my-tor1-control-socket
ControlPort 9051
CookieAuthentication 1
CookieAuthFile /tmp/my-tor1-control-auth-cookie
ClientOnly 1
TransPort 9041
DNSPort 9031
SocksPort 0
AutomapHostsOnResolve 1
VirtualAddrNetwork 10.0.0.0/8
Log notice file /var/log/tor/my-tor1-log
PidFile /var/run/tor/my-tor1.pid
DataDirectory /var/lib/tor/my-tor-1
**Trac**:
**Username**: toruser32Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/4038connection refused/vidalia2012-02-13T18:17:20Zcypherpunksconnection refused/vidaliaOn occasion vidalia says 'connection refused by peer', while having 'catching signal TERM, exiting cleanly' in its logs. Tor doesn't start then. Using Tor Browser Bundle 2.2.32-4 (Linux). Didn't happen with former versions of tbbOn occasion vidalia says 'connection refused by peer', while having 'catching signal TERM, exiting cleanly' in its logs. Tor doesn't start then. Using Tor Browser Bundle 2.2.32-4 (Linux). Didn't happen with former versions of tbbTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/3940Allow MapAddress .exit even if AllowDotExit is 02020-06-13T14:13:03ZSteven MurdochAllow MapAddress .exit even if AllowDotExit is 0If AllowDotExit is 0 (the default) MapAddress doesn't permit a .exit address to be set as the destination. It is desirable to keep AllowDotExit disabled for security reasons, but there shouldn't be any harm in always permitting MapAddres...If AllowDotExit is 0 (the default) MapAddress doesn't permit a .exit address to be set as the destination. It is desirable to keep AllowDotExit disabled for security reasons, but there shouldn't be any harm in always permitting MapAddress entries because the user must enter these manually. This feature is desirable because it allows the user to force exit enclaving.
Using Tor v0.2.2.32 (git-877e17749725ab88).Tor: 0.3.3.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/4260[PATCH] Update TOR build instructions for mingw2020-06-13T14:13:54ZTrac[PATCH] Update TOR build instructions for mingwHi,
I've updated the documentation for building TOR on MinGW, and attached the result (and the patch). Please, consider replacing the file <doc/tor-win32-mingw-creation.txt> with it.
Here are the main changes:
- the MinGW installer in...Hi,
I've updated the documentation for building TOR on MinGW, and attached the result (and the patch). Please, consider replacing the file <doc/tor-win32-mingw-creation.txt> with it.
Here are the main changes:
- the MinGW installer includes the MSYS and DTK packages, so there no need to download and install them separately.
- there's no more issue with symlinks for openssl.
- specifying "mingw" to the "Configure" command is enough to disable openssl ciphers/hashes that don't compile on MinGW.
- since v1.2.5, zlib needs some extra (?) environment variables for its installation.
- the libraries download links have been updated so that they point to the latest version to date.
- instructions for executing unit-tests have been added for the libraries and TOR.
Maybe zlib should be built before openssl since some optional features of openssl seems to depend on zlib. I followed these instructions in order to build TOR successfully on my WinXP computer.
**Trac**:
**Username**: Tey'Tor: unspecifiedErinn ClarkErinn Clarkhttps://gitlab.torproject.org/legacy/trac/-/issues/4259[PATCH] Tor crashes when nodes restrictions are changed at runtime2020-06-13T14:13:53ZTrac[PATCH] Tor crashes when nodes restrictions are changed at runtimeHi,
Changing nodes restrictions using a controller while Tor is doing DNS resolution could makes Tor crashes (on WinXP at least). The problem can be repeated by trying to reach a non-existent domain using Tor:
curl --socks4a 127.0.0.1...Hi,
Changing nodes restrictions using a controller while Tor is doing DNS resolution could makes Tor crashes (on WinXP at least). The problem can be repeated by trying to reach a non-existent domain using Tor:
curl --socks4a 127.0.0.1:9050 inexistantdomain.ext
.. and changing the ExitNodes parameter through the control port before Tor returns a DNS resolution error (of course, the following command won't work directly if the control port is password protected):
echo SETCONF ExitNodes=TinyTurtle | nc -v 127.0.0.1 9051
Using a non-existent domain is needed to repeat the issue so that Tor takes a few seconds for resolving the domain (which allows us to change the configuration). Tor will crash while processing the configuration change.
The bug is located in the addressmap_clear_excluded_trackexithosts method which iterates over the entries of the addresses map in order to check whether the changes made to the configuration will impact those entries. When a DNS resolving is in progress, the new_adress field of the associated entry will be set to NULL. The method doesn't expect this field to be NULL, hence the crash.
I attached a patch that fixes the problem.
**Trac**:
**Username**: Tey'