Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:04:48Zhttps://gitlab.torproject.org/legacy/trac/-/issues/19919If ORPort address is publicly routable, use it to guess Address2020-06-13T15:04:48ZteorIf ORPort address is publicly routable, use it to guess AddressSplitting this off from #13953: we'll warn in that ticket, and make the change to the address resolution order in this one.Splitting this off from #13953: we'll warn in that ticket, and make the change to the address resolution order in this one.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/15240Tor starts PTs before creating the extended_orport_auth_cookie file they need2020-06-13T14:44:14ZJens KubiezielTor starts PTs before creating the extended_orport_auth_cookie file they needI'm using 0.2.5.10-1~d70.wheezy+1 from Debian and obfs4proxy 0.0.4-1 to set up a some bridges. My torrc looks like:
```
Address 192.0.2.23
OutboundBindAddress 192.0.2.23
OutboundBindAddress 2001:db8::94de
ORPort 56527
ExtORPort 55009
ORL...I'm using 0.2.5.10-1~d70.wheezy+1 from Debian and obfs4proxy 0.0.4-1 to set up a some bridges. My torrc looks like:
```
Address 192.0.2.23
OutboundBindAddress 192.0.2.23
OutboundBindAddress 2001:db8::94de
ORPort 56527
ExtORPort 55009
ORListenAddress 192.0.2.23:56527
ORListenAddress [2001:db8::94de]:56527
DataDirectory /var/lib/tor
PidFile /var/run/tor/tor.pid
Log notice file /var/log/tor/notices.log
ServerTransportPlugin scramblesuit exec /usr/bin/obfsproxy managed
ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxy -enableLogging -logLevel=INFO
ServerTransportListenAddr obfs3 192.0.2.23:33027
ServerTransportListenAddr obfs3 [2001:db8::94de]:33027
ServerTransportListenAddr obfs4 192.0.2.23:47131
ServerTransportListenAddr obfs4 [2001:db8::94de]:47131
ServerTransportListenAddr scramblesuit 192.0.2.23:16428
ServerTransportListenAddr scramblesuit [2001:db8::94de]:16428
ContactInfo me@example.org
User debian-tor
RunAsDaemon 1
NumCPUs 1
PublishServerDescriptor 1
SocksPort 0
BridgeRelay 1
Exitpolicy reject *:*
Exitpolicy reject6 *:*
BridgeRecordUsageByCountry 1
ConnDirectionStatistics 1
EntryStatistics 1
ExtraInfoStatistics 1
DynamicDHGroups 1
HardwareAccel 1
```
When I enter the bridge line in TBB 4.5a4, I can't get a connection. Looking at the obfs4proxy.log, I see the message:
> 2015/03/11 22:19:25 [ERROR]: obfs4([scrubbed]:58915) - failed to connect to ORPort: mismatch in server hash
When I comment out the `ExtORPort` line and restart Tor, I can connect to the bridge. If I set `ExtORPort auto` I can't get a connection. Later I'll provide a more detailed log.Tor: 0.2.6.x-finalGeorge KadianakisGeorge Kadianakishttps://gitlab.torproject.org/legacy/trac/-/issues/15219Visiting site triggers warning2020-06-15T23:24:37ZcypherpunksVisiting site triggers warningIf to try visit 5yo.panty.shot.valdikss.org.ru using tor (TorBrowser) then it triggers warnings for me
```
[warn] I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's not going to wor...If to try visit 5yo.panty.shot.valdikss.org.ru using tor (TorBrowser) then it triggers warnings for me
```
[warn] I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's not going to work. Did you perhaps ask for an IPv6 address on an IPv4Only port, or vice versa?
```https://gitlab.torproject.org/legacy/trac/-/issues/15102Tor crashed with tor_assertion_failed_() in ../src/or/buffers.c:26272020-06-13T14:43:56ZTracTor crashed with tor_assertion_failed_() in ../src/or/buffers.c:2627Hi,
unfortunately our tor relay just crashed today while relaying aroung 20MB/s data.
This is all I could find in the /var/log/tor/log:
Mar 02 11:02:23.000 [notice] Heartbeat: Tor's uptime is 30 days 6:00 hours, with 27608 circuits op...Hi,
unfortunately our tor relay just crashed today while relaying aroung 20MB/s data.
This is all I could find in the /var/log/tor/log:
Mar 02 11:02:23.000 [notice] Heartbeat: Tor's uptime is 30 days 6:00 hours, with 27608 circuits open. I've sent 63378.02 GB and received 61162.07 GB.
Mar 02 11:02:23.000 [notice] Average packaged cell fullness: 99.115%
Mar 02 11:02:23.000 [notice] TLS write overhead: 3%
Mar 02 11:02:23.000 [notice] Circuit handshake stats since last time: 216438/216438 TAP, 170322/170322 NTor.
Mar 02 11:18:54.000 [err] tor_assertion_failed_(): Bug: ../src/or/buffers.c:2627: assert_buf_ok: Assertion ch->data < &ch->mem[0]+ch->memlen failed; aborting.
Mar 02 11:18:54.000 [err] Bug: Assertion ch->data < &ch->mem[0]+ch->memlen failed in assert_buf_ok at ../src/or/buffers.c:2627. Stack trace:
Mar 02 11:18:54.000 [err] Bug: /usr/bin/tor(log_backtrace+0x41) [0x7fc22b3d6191]
Mar 02 11:18:54.000 [err] Bug: /usr/bin/tor(tor_assertion_failed_+0x94) [0x7fc22b3e1d94]
Mar 02 11:18:54.000 [err] Bug: /usr/bin/tor(assert_buf_ok+0x167) [0x7fc22b3528a7]
Mar 02 11:18:54.000 [err] Bug: /usr/bin/tor(assert_connection_ok+0xce) [0x7fc22b38bbae]
Mar 02 11:18:54.000 [err] Bug: /usr/bin/tor(+0x35017) [0x7fc22b2fa017]
Mar 02 11:18:54.000 [err] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x754) [0x7fc22a94af24]
Mar 02 11:18:54.000 [err] Bug: /usr/bin/tor(do_main_loop+0x195) [0x7fc22b2fb7b5]
Mar 02 11:18:54.000 [err] Bug: /usr/bin/tor(tor_main+0x18f5) [0x7fc22b2fe7a5]
Mar 02 11:18:54.000 [err] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fc229b2bec5]
Mar 02 11:18:54.000 [err] Bug: /usr/bin/tor(+0x32f5b) [0x7fc22b2f7f5b]
**Trac**:
**Username**: amkihttps://gitlab.torproject.org/legacy/trac/-/issues/15088Add the wait4() syscall to the seccomp sandbox2020-06-13T14:43:55ZTracAdd the wait4() syscall to the seccomp sandboxTor version 0.2.5.10 seems to call wait4() upon receiving SIGHUP, and this violates the seccomp sandbox rules in sandbox.c, crashing the tor process.
Trace from tor's log on debug loglevel, right after `/etc/init.d/tor reload`:
```
====...Tor version 0.2.5.10 seems to call wait4() upon receiving SIGHUP, and this violates the seccomp sandbox rules in sandbox.c, crashing the tor process.
Trace from tor's log on debug loglevel, right after `/etc/init.d/tor reload`:
```
============================================================ T= 1425215692
(Sandbox) Caught a bad syscall attempt (syscall wait4)
/usr/bin/tor(+0x12f4f1)[0x4273cf44f1]
/lib64/libc.so.6(waitpid+0x1a)[0x3423957b1da]
/lib64/libc.so.6(waitpid+0x1a)[0x3423957b1da]
/usr/bin/tor(notify_pending_waitpid_callbacks+0x4a)[0x4273cf42da]
/usr/bin/tor(process_signal+0x4ad)[0x4273bfb96d]
/usr/lib64/libevent-2.0.so.5(event_base_loop+0x99e)[0x3423a111a6e]
/usr/bin/tor(do_main_loop+0x1ad)[0x4273bfa77d]
/usr/bin/tor(tor_main+0x1875)[0x4273bfd755]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x342394e2d55]
/usr/bin/tor(+0x31c49)[0x4273bf6c49]
Mar 01 16:14:52.000 [info] cpuworker_main(): read request failed. Exiting.
```
The patch is as simple as adding wait4() to the whitelist:
```
diff -Naur tor-0.2.5.10/src/common/sandbox.c tor-0.2.5.10.new/src/common/sandbox.c
--- tor-0.2.5.10/src/common/sandbox.c
+++ tor-0.2.5.10.new/src/common/sandbox.c
@@ -119,6 +119,7 @@
SCMP_SYS(epoll_wait),
SCMP_SYS(fcntl),
SCMP_SYS(fstat),
+ SCMP_SYS(wait4),
#ifdef __NR_fstat64
SCMP_SYS(fstat64),
#endif
```
**Trac**:
**Username**: sanicTor: 0.2.5.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/15083Assertion ch->data < &ch->mem[0]+ch->memlen failed2020-06-13T14:43:54ZTracAssertion ch->data < &ch->mem[0]+ch->memlen failedFeb 28 06:25:04.000 [notice] Tor 0.2.5.10 (git-43a5f3d91e726291) opening new log file.
Feb 28 09:12:42.000 [notice] Caching new entry debian-tor for debian-tor
Feb 28 09:12:55.000 [notice] Heartbeat: Tor's uptime is 9 days 23:57 hours, w...Feb 28 06:25:04.000 [notice] Tor 0.2.5.10 (git-43a5f3d91e726291) opening new log file.
Feb 28 09:12:42.000 [notice] Caching new entry debian-tor for debian-tor
Feb 28 09:12:55.000 [notice] Heartbeat: Tor's uptime is 9 days 23:57 hours, with 3628 circuits open. I've sent 2019.68 GB and received 1952.11 GB.
Feb 28 09:12:55.000 [notice] Average packaged cell fullness: 97.211%
Feb 28 09:12:55.000 [notice] TLS write overhead: 3%
Feb 28 09:12:55.000 [notice] Circuit handshake stats since last time: 24992/25002 TAP, 25312/25314 NTor.
Feb 28 15:12:55.000 [notice] Heartbeat: Tor's uptime is 10 days 5:57 hours, with 4022 circuits open. I've sent 2074.91 GB and received 2005.67 GB.
Feb 28 15:12:55.000 [notice] Average packaged cell fullness: 97.253%
Feb 28 15:12:55.000 [notice] TLS write overhead: 3%
Feb 28 15:12:55.000 [notice] Circuit handshake stats since last time: 37526/37526 TAP, 31539/31539 NTor.
Feb 28 15:29:59.000 [err] tor_assertion_failed_(): Bug: ../src/or/buffers.c:2627: assert_buf_ok: Assertion ch->data < &ch->mem[0]+ch->memlen failed; aborting.
Feb 28 15:29:59.000 [err] Bug: Assertion ch->data < &ch->mem[0]+ch->memlen failed in assert_buf_ok at ../src/or/buffers.c:2627. Stack trace:
Feb 28 15:29:59.000 [err] Bug: /usr/bin/tor(log_backtrace+0x41) [0x7fb3e3dd9d01]
Feb 28 15:29:59.000 [err] Bug: /usr/bin/tor(tor_assertion_failed_+0x9f) [0x7fb3e3de59bf]
Feb 28 15:29:59.000 [err] Bug: /usr/bin/tor(assert_buf_ok+0x167) [0x7fb3e3d547f7]
Feb 28 15:29:59.000 [err] Bug: /usr/bin/tor(assert_connection_ok+0xb8) [0x7fb3e3d8de28]
Feb 28 15:29:59.000 [err] Bug: /usr/bin/tor(+0x37617) [0x7fb3e3cfc617]
Feb 28 15:29:59.000 [err] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x414) [0x7fb3e33d3254]
Feb 28 15:29:59.000 [err] Bug: /usr/bin/tor(do_main_loop+0x19d) [0x7fb3e3cfcf4d]
Feb 28 15:29:59.000 [err] Bug: /usr/bin/tor(tor_main+0x1aa5) [0x7fb3e3d000b5]
Feb 28 15:29:59.000 [err] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fb3e25f0ead]
Feb 28 15:29:59.000 [err] Bug: /usr/bin/tor(+0x3465d) [0x7fb3e3cf965d]
**Trac**:
**Username**: poiutyTor: 0.2.6.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/15073issue with establishing tor connection in linux2020-06-13T14:43:53ZTracissue with establishing tor connection in linuxHello
I am a user in Iran, running tor on a linux. Recently- more than a week- tor failed to establish connection to the tor network, messages as such:
Feb 28 09:40:46.000 [notice] Bootstrapped 0%: Starting
Feb 28 09:40:47.000 [notice] B...Hello
I am a user in Iran, running tor on a linux. Recently- more than a week- tor failed to establish connection to the tor network, messages as such:
Feb 28 09:40:46.000 [notice] Bootstrapped 0%: Starting
Feb 28 09:40:47.000 [notice] Bootstrapped 5%: Connecting to directory server
Feb 28 09:41:50.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Feb 28 09:41:51.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection
Feb 28 09:41:51.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus
Feb 28 09:41:51.000 [notice] Bootstrapped 25%: Loading networkstatus consensus
Feb 28 09:47:20.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
I know that your first advise must be using the tor-browser but for the technical reason and ease of use and also torrifying everything outo f my linux I much prepfer to use tor as a daemon built in app in linux.
I tried to troubleshoot all the possible ways including a new kvm and setting tor in it to observe the connection establishment and if that is suppressed by the Iran regime. I should say that there I received pretty funny messages as:
Feb 28 09:57:48.000 [warn] 10 connections died in state connect()ing with SSL state (No SSL object)
Feb 28 09:59:05.000 [warn] Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (Connection timed out; TIMEOUT; count 12; recommendation warn)
Feb 28 09:59:05.000 [warn] 11 connections have failed:
Feb 28 09:59:05.000 [warn] 11 connections died in state connect()ing with SSL state (No SSL object)
or
Feb 28 10:06:14.000 [notice] Bootstrapped 100%: Done
Feb 28 10:06:32.000 [warn] Received http status code 404 ("Not found") from server '85.14.240.188:443' while fetching "/tor/keys/fp/27B6B5996C426270A5C95488AA5BCEB6BCC86956".
Feb 28 10:08:45.000 [warn] parse error: Malformed object: missing object end line
Feb 28 10:08:45.000 [warn] Unparseable microdescripto
or
Feb 25 11:51:53.000 [warn] I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's not going to work. Did you perhaps ask for an IPv6 address on an IPv4Only port, or vice versa?
Feb 25 11:51:53.000 [warn] I'm about to ask a node for a connection that I am telling it to fulfil with neither IPv4 nor IPv6. That's not going to work. Did you perhaps ask for an IPv6 address on an IPv4Only port, or vice versa?
Feb 25 11:52:05.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $F65E0196C94DFFF48AFBF2F5F9E3E19AAE583FD0~destiny at 94.242.246.23. Retrying on a new circuit.
Feb 25 11:52:05.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $F65E0196C94DFFF48AFBF2F5F9E3E19AAE583FD0~destiny at 94.242.246.23. Retrying on a new circuit.
pretty much seems to my eyes a tampered ssl. My tor config is straight forward and includes a default 9050 port socks 5 on the 127.0.0.1.
Here is the signature and version info:
-Linux localhost 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
-tor-0.2.5.10-1.el6.x86_64
-torsocks-2.0.0-2.el6.x86_64
**Trac**:
**Username**: hsafehttps://gitlab.torproject.org/legacy/trac/-/issues/15064Fix a bug using IPFW transparent proxy2020-06-13T14:43:52ZTracFix a bug using IPFW transparent proxyWe've been working on setting up IPFW transparent proxy on FreeBSD, and ran into a bug when using "TransProxyType ipfw". The attached patch fixes the issue.
**Trac**:
**Username**: kmoore134We've been working on setting up IPFW transparent proxy on FreeBSD, and ran into a bug when using "TransProxyType ipfw". The attached patch fixes the issue.
**Trac**:
**Username**: kmoore134Tor: 0.2.6.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/15014Socks5 and socks5t got changed and broke compatibility with privoxy2017-06-09T15:52:48ZTracSocks5 and socks5t got changed and broke compatibility with privoxyI updated tor on the 15 relays I run privately and the 5 my employers network hosts, for employees to use as clients; I started receiving an error in privoxy for unencrypted sites when I tried to browse:
* 2015-02-23 16:02:09.636 0000...I updated tor on the 15 relays I run privately and the 5 my employers network hosts, for employees to use as clients; I started receiving an error in privoxy for unencrypted sites when I tried to browse:
* 2015-02-23 16:02:09.636 0000260c Error: Invalid server headers. Applying the MS IIS5 hack didn't help.
and in torbrowser:
* "...does not look like http"
I was pulling my hair out restoring backup configs for privoxy, tor, and tor browser itself to find that something had been changed in tor 0.2.5.10 with the socks5 protocols that now breaks functionality for privoxy. I have used other programs on socks5 fine since the change, which is why I thought it was privoxy, which it "is".
However, when you decide to change something in tor where another service is developed and deployed in unison with tor, like privoxy, please put an option to specify in torrc to use the old protocol until privoxy, or whatever project, can get up to speed :) I Have always known privoxy and tor to be promoted together, people suggesting privoxy when they suggest tor. I mean, socks5t was developed specifically for privoxy, right?
Now, I'd say over HALF of the people using the tor network to browse (because of the popularity with privoxy) are having the same error, not realizing they need to change privoxy config to use socks4 or socks4a until privoxy updates or you add an option to revert compatibility.
I don't know if privoxy is in tor browser bundle or not but I assume not, since tor browser gets configured with the only proxy being socks, by default. I assume torbirdy? is responsible for this.
**Trac**:
**Username**: johnakabeanTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/14988tor 0.2.5 does not build on s390 with picky gcc2020-06-13T14:43:29Zweasel (Peter Palfrader)tor 0.2.5 does not build on s390 with picky gcc
https://jenkins.torproject.org/job/tor-ci-linux-0.2.5-extra-s390/ARCHITECTURE=s390x,SUITE=jessie/5/consoleFull
```
5:31:08 depbase=`echo src/common/backtrace.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
15:31:08 gcc -DHAVE_CONFIG_H -I. -I.....
https://jenkins.torproject.org/job/tor-ci-linux-0.2.5-extra-s390/ARCHITECTURE=s390x,SUITE=jessie/5/consoleFull
```
5:31:08 depbase=`echo src/common/backtrace.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
15:31:08 gcc -DHAVE_CONFIG_H -I. -I../tor -I../tor/src/ext -Isrc/ext -I../tor/src/common -Isrc/common -I../tor/src/or -Isrc/or -DSHARE_DATADIR="\"/usr/local/share\"" -DLOCALSTATEDIR="\"/usr/local/var\"" -DBINDIR="\"/usr/local/bin\"" -I../tor/src/common -g -O2 -D_FORTIFY_SOURCE=2 -fstack-protector-all -Wstack-protector -fwrapv --param ssp-buffer-size=1 -fPIE -fasynchronous-unwind-tables -Wall -fno-strict-aliasing -W -Wfloat-equal -Wundef -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -Wredundant-decls -Wchar-subscripts -Wcomment -Wformat=2 -Wwrite-strings -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wbad-function-cast -Wswitch-enum -Werror -Winit-self -Wmissing-field-initializers -Wdeclaration-after-statement -Wold-style-definition -Waddress -Wmissing-noreturn -Wstrict-overflow=1 -Wnormalized=id -Woverride-init -Wextra -Warray-bounds -Wlogical-op -MT src/common/backtrace.o -MD -MP -MF $depbase.Tpo -c -o src/common/backtrace.o ../tor/src/common/backtrace.c &&\
15:31:08 mv -f $depbase.Tpo $depbase.Po
15:31:11 ../tor/src/common/backtrace.c: In function 'clean_backtrace':
15:31:11 ../tor/src/common/backtrace.c:65:24: error: unused parameter 'stack' [-Werror=unused-parameter]
15:31:11 clean_backtrace(void **stack, int depth, const ucontext_t *ctx)
15:31:11 ^
15:31:14 cc1: all warnings being treated as errors
15:31:14 Makefile:2365: recipe for target 'src/common/backtrace.o' failed
15:31:14 make[1]: *** [src/common/backtrace.o] Error 1
```Tor: 0.2.6.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/14953AUTHDIR_NEWDESCS events control channel munges descriptors2020-06-13T14:43:24Zweasel (Peter Palfrader)AUTHDIR_NEWDESCS events control channel munges descriptorsSubscribing to uploaded descriptors on Tor's control port returns truncated descriptors:
```
% socat - UNIX-CONNECT:/var/run/tor/control
AUTHENTICATE xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
250 OK
SETEVENTS AUTHDIR_NEWDESCS
250 OK...Subscribing to uploaded descriptors on Tor's control port returns truncated descriptors:
```
% socat - UNIX-CONNECT:/var/run/tor/control
AUTHENTICATE xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
250 OK
SETEVENTS AUTHDIR_NEWDESCS
250 OK
650+AUTHDIR_NEWDESC=
DROPPED
Not replacing router descriptor; no information has changed since the last one with this identity.
@uploaded-at 2015-02-19 15:16:31
@source "195.154.166.113"
router relay1 195.154.166.113 9002 0 0
platform Tor 0.2.3.25 on Linux
opt protocols Link 1 2 Circuit 1
published 2015-02-19 15:16:31
opt fingerprint 8672 1EDE FAEC 4AE7 AC42 4A65 E111 565A CC8F 3ABE
uptime 15815372
bandwidth 5242880 10485760 521025
opt extra-info-digest E3C0A428989A6CC84606FB9E273CC1B6513AE6AF
onion-key
-----BEGIN RSA PUBLIC KEY-----
MIGJAoGBAMFn46oyQ2jkRPjx6D9IHDvfW2db53+IxXaeQwHdaayxls7r9HF81/UK
618hrOJMSGwe7RTBa16XIlqm8Dx/AILZtEx+vERYz1MIPWjXT6/WJEh+qXCuibcg
wDDvCBryoDMp23GwtYclFZdCvir3oNydZlWz1lwaraMEZMLDwZ+LAgMBAAE=
-----END RSA PUBLIC KEY-----
signing-key
-----BEGIN RSA PUBLIC KEY-----
MIGJAoGBAMJe0bpEEN5c5+5NnMPG4isD+N7d7djowOrKxDis+Bu0WfSPSCcDdb7p
yicwQW0Lpy21naWS1sQuDgHcuHt2dyZwqIVNXLww7NGdxuq0ejB83D3p04puyDvC
klYiM7X/mU+qWFpvlOvrh20utSou8AbQGEz9LSdo6rYxivTPmWRxAgMBAAE=
-----END RSA PUBLIC KEY-----
opt hidden-service-dir
contact anonymous1 anonymous@mail.com
reject *:*
router-signature
-----BEGIN SIGNATURE-----
Qc6FmoZqkllya4e1/fp4LoREphSwruLetHsLQUlO3kCccqusfbXkooXYiEbFC2zp
vSPNNx8vvjs1lqZdPZ5b3++Uar06FgPl2BM08PVXk0B7l7QHuXa3JBqfewR6hLVe
mU2vxVsw55
.
650 OK
650+AUTHDIR_NEWDESC=
DROPPED
Not replacing router descriptor; no information has changed since the last one with this identity.
@uploaded-at 2015-02-19 15:16:32
[...]
```
Note how the signature was truncated.Tor: 0.2.6.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/14895SENTCONNECT TCP RST/TIMEOUT print IP in FAILED/CLOSED2020-06-13T14:43:13ZgrarpampSENTCONNECT TCP RST/TIMEOUT print IP in FAILED/CLOSEDConnect requests resulting in TCP ACK properly print the IP resolved and connected to by the exit in SUCCEEDED and CLOSED...
NEW torproject.org:80 PURPOSE=USER
SENTCONNECT torproject.org:80
REMAP 154.35.132.70:80 SOURCE=EXIT
SUCCEEDED 1...Connect requests resulting in TCP ACK properly print the IP resolved and connected to by the exit in SUCCEEDED and CLOSED...
NEW torproject.org:80 PURPOSE=USER
SENTCONNECT torproject.org:80
REMAP 154.35.132.70:80 SOURCE=EXIT
SUCCEEDED 154.35.132.70:80
CLOSED 154.35.132.70:80 REASON=DONE
Yet those resulting in TCP RST or TIMEOUT fail to print the IP even though the IP is (if not it should be) returned and known to client in those cases as well...
NEW torproject.org:800 PURPOSE=USER
SENTCONNECT torproject.org:800
FAILED torproject.org:800 REASON=END REMOTE_REASON=CONNECTREFUSED
CLOSED torproject.org:800 REASON=END REMOTE_REASON=CONNECTREFUSED
NEW example.com:800 PURPOSE=USER
SENTCONNECT example.com:800
DETACHED example.com:800 REASON=TIMEOUT
...
FAILED example.com:800 REASON=CANT_ATTACH
CLOSED example.com:800 REASON=CANT_ATTACH
Fix:
- Instead of the printing the SENTCONNECT fwd name, print the IP in those FAILED and CLOSED lines.
- The IP should also be printed in DETACHED if we have it (which we should if the TIMEOUT is being returned to us in a cell from the exit, as opposed to the client timing it out).
Also, in the case of a RST, it seems something (like CONNECTING, REMAP, DETACHED or some relavent label and line) could/should be printed between SENTCONNECT and FAILED.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/14883Orbot handshake fails on networks with Blue Coat Systems' technology2020-06-13T03:58:08ZTracOrbot handshake fails on networks with Blue Coat Systems' technologyBootstrapping fails at 85%.
**Trac**:
**Username**: ProGamerGovBootstrapping fails at 85%.
**Trac**:
**Username**: ProGamerGovNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/14801"EXCLUDE Nodes" is not respected in Orbot2020-06-13T03:56:24ZTrac"EXCLUDE Nodes" is not respected in OrbotI've entered FiveEyes in Exlude Nodes and yet it still connects me to them. At first I thought it's just relay nodes. But just now, I was connected to a path with an Exit Node in one of them!
I input countries as:
US, UK, NZ, CA, AU,
A...I've entered FiveEyes in Exlude Nodes and yet it still connects me to them. At first I thought it's just relay nodes. But just now, I was connected to a path with an Exit Node in one of them!
I input countries as:
US, UK, NZ, CA, AU,
And I also tried with and without "Strict Nodes" option.
Orbot: 14.1.4-noPIE (Tor: 0.2.5.10)
Android: 4.4.4
Nexus 5, stock rooted
Downloaded Orbot from F-Droid
**Trac**:
**Username**: BugerNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/14782How to close Tor Expert Bundle2020-06-15T23:23:59ZTracHow to close Tor Expert BundleBefore with Tor Expert Bundle 0.2.4.23 (tor-0.2.4.23-win32.exe), when Tor started it opened a window and if i want to close Tor, i close the window.
In the window, i could see also tor status and if there are error messages.
Now with the...Before with Tor Expert Bundle 0.2.4.23 (tor-0.2.4.23-win32.exe), when Tor started it opened a window and if i want to close Tor, i close the window.
In the window, i could see also tor status and if there are error messages.
Now with the release of Tor Expert Bundle 0.2.5.10 (tor-win32-tor-0.2.5.10.zip), Tor run in background and if i want to close Tor i need to press Alt-Ctrl-Canc and kill tor.exe. Now is also impossible to view Tor status and error messages.
So i think is better to reintroduce in expert bundle the old window to close tor and when tor is minimize only an icon in the system tray (not a window in the taskbar, like tor 0.2.4.x)
**Trac**:
**Username**: qqqqwhttps://gitlab.torproject.org/legacy/trac/-/issues/14450tor-resolve should better handle .onion addresses2020-06-13T14:42:10Zweasel (Peter Palfrader)tor-resolve should better handle .onion addressesIn https://bugs.debian.org/776454, Russell Coker asks for a slight modification of tor-resolve's behavior wrt .onion addresses:
$ tor-resolve zp7zwyd5t3aju57m.onion
Jan 28 17:38:42.055 [warn] Got SOCKS5 status response '4': host is ...In https://bugs.debian.org/776454, Russell Coker asks for a slight modification of tor-resolve's behavior wrt .onion addresses:
$ tor-resolve zp7zwyd5t3aju57m.onion
Jan 28 17:38:42.055 [warn] Got SOCKS5 status response '4': host is unreachable
Jan 28 17:38:42.055 [warn] zp7zwyd5t3aju57m.onion is a hidden service; those don't have IP addresses. To connect to a hidden service, you need to send the hostname to Tor; we suggest an application that uses SOCKS 4a.
The above output is informative, but not particularly useful for the case of
scripts.
https://www.howtoforge.com/anonymous-ssh-sessions-with-tor
The above web site gives an example of how to use tor which btraks when used
with .onion addresses. One way to solve this would be for tor-resolve to
give "zp7zwyd5t3aju57m.onion" on stdout and the warning message on stderr,
that would inform users but work in the desired manner with scripts.
A small change to tor-resolve will make it work better with existing documented
practice and make it work with future use for .onion addresses in cases where
admins only care about non-onion addresses now.Tor: 0.2.6.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/14325tor-resolve errata2020-06-13T14:42:01Zgrarpamptor-resolve errataThe binary help string does not match the manpage option list, or the actual source code.
./tor-resolve
Syntax: tor-resolve [-4] [-v] [-x] [-F] [-p port] hostname [sockshost:socksport]
The note below should direct people to use SOCKSv...The binary help string does not match the manpage option list, or the actual source code.
./tor-resolve
Syntax: tor-resolve [-4] [-v] [-x] [-F] [-p port] hostname [sockshost:socksport]
The note below should direct people to use SOCKSv5, not legacy 4a stuff. This message occurs in two places in the source. The '-4' option should also be renamed to '-4a'.
./tor-resolve -v abcdefghijklmnop.onion 127.0.0.1:9051
[warn] ... To connect to a hidden service ... we suggest an application that uses SOCKS 4a.Tor: 0.2.6.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/14184Control port command "getinfo entry-guards" return all guards with the "up" s...2020-06-13T14:41:44ZDavid Gouletdgoulet@torproject.orgControl port command "getinfo entry-guards" return all guards with the "up" state`getinfo entry-guards` returns a list of guards that are all flagged as "up" even though the state file shows only one of them is actually up and all others are down.`getinfo entry-guards` returns a list of guards that are all flagged as "up" even though the state file shows only one of them is actually up and all others are down.Tor: 0.2.6.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/14157Tor Browser: Unsolved DNS of a website or HS result in 100% CPU usage2020-06-15T23:23:05ZTracTor Browser: Unsolved DNS of a website or HS result in 100% CPU usage
I've been observing this behavior for a while. Tor browser taking 100% CPU for few seconds if it DNS resolver fails for a website and HS is not reachable.
[Sasi@NoNameForHost ~]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b44...
I've been observing this behavior for a while. Tor browser taking 100% CPU for few seconds if it DNS resolver fails for a website and HS is not reachable.
[Sasi@NoNameForHost ~]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b44b071d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f05b56ace60 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#2 0x00007f05b0b16346 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#3 0x00007f05b0b167d4 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#4 0x00007f05b0b16bb8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#5 0x00007f05b0ae4e95 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#6 0x00007f05b0aa12f2 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#7 0x00007f05b0c5de74 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#8 0x00007f05b0c442eb in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#9 0x00007f05b0ae57e1 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#10 0x00007f05b56aeff8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#11 0x00007f05b53c6ee5 in start_thread (arg=0x7f05997ff700) at pthread_create.c:309
#12 0x00007f05b44bab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[Sasi@NoNameForHost ~]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b44b071d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f05b56ace60 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#2 0x00007f05b0b16346 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#3 0x00007f05b0b167d4 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#4 0x00007f05b0b16bb8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#5 0x00007f05b0ae4e95 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#6 0x00007f05b0aa12f2 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#7 0x00007f05b0c5de74 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#8 0x00007f05b0c442eb in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#9 0x00007f05b0ae57e1 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#10 0x00007f05b56aeff8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#11 0x00007f05b53c6ee5 in start_thread (arg=0x7f05997ff700) at pthread_create.c:309
#12 0x00007f05b44bab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[Sasi@NoNameForHost ~]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b53cdb8b in __libc_recv (fd=71, buf=0x7f057a040f20, n=5, flags=-1) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33
#1 0x00007f05b56abf36 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#2 0x00007f05b0b5cb61 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#3 0x00007f05b0b5ccec in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#4 0x00007f05b0b5cd47 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#5 0x00007f05b0b14426 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#6 0x00007f05b0b16899 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#7 0x00007f05b0b16bb8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#8 0x00007f05b0ae4e95 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#9 0x00007f05b0aa12f2 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#10 0x00007f05b0c5de74 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#11 0x00007f05b0c442eb in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#12 0x00007f05b0ae57e1 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#13 0x00007f05b56aeff8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#14 0x00007f05b53c6ee5 in start_thread (arg=0x7f05997ff700) at pthread_create.c:309
#15 0x00007f05b44bab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[root@NoNameForHost Downloads]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b44b071d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f05b56ace60 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#2 0x00007f05b0b16346 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#3 0x00007f05b0b167d4 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#4 0x00007f05b0b16bb8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#5 0x00007f05b0ae4e95 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#6 0x00007f05b0aa12f2 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#7 0x00007f05b0c5de74 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#8 0x00007f05b0c442eb in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#9 0x00007f05b0ae57e1 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#10 0x00007f05b56aeff8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#11 0x00007f05b53c6ee5 in start_thread (arg=0x7f05997ff700) at pthread_create.c:309
#12 0x00007f05b44bab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
**Trac**:
**Username**: Sasihttps://gitlab.torproject.org/legacy/trac/-/issues/14156Tor Browser: Unsolved DNS of a website or HS result in 100% CPU usage2020-06-15T23:23:02ZTracTor Browser: Unsolved DNS of a website or HS result in 100% CPU usage
I've been observing this behavior for a while. Tor browser taking 100% CPU for few seconds if it DNS resolver fails for a website and HS is not reachable.
[Sasi@NoNameForHost ~]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b44...
I've been observing this behavior for a while. Tor browser taking 100% CPU for few seconds if it DNS resolver fails for a website and HS is not reachable.
[Sasi@NoNameForHost ~]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b44b071d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f05b56ace60 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#2 0x00007f05b0b16346 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#3 0x00007f05b0b167d4 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#4 0x00007f05b0b16bb8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#5 0x00007f05b0ae4e95 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#6 0x00007f05b0aa12f2 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#7 0x00007f05b0c5de74 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#8 0x00007f05b0c442eb in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#9 0x00007f05b0ae57e1 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#10 0x00007f05b56aeff8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#11 0x00007f05b53c6ee5 in start_thread (arg=0x7f05997ff700) at pthread_create.c:309
#12 0x00007f05b44bab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[Sasi@NoNameForHost ~]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b44b071d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f05b56ace60 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#2 0x00007f05b0b16346 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#3 0x00007f05b0b167d4 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#4 0x00007f05b0b16bb8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#5 0x00007f05b0ae4e95 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#6 0x00007f05b0aa12f2 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#7 0x00007f05b0c5de74 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#8 0x00007f05b0c442eb in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#9 0x00007f05b0ae57e1 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#10 0x00007f05b56aeff8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#11 0x00007f05b53c6ee5 in start_thread (arg=0x7f05997ff700) at pthread_create.c:309
#12 0x00007f05b44bab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[Sasi@NoNameForHost ~]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b53cdb8b in __libc_recv (fd=71, buf=0x7f057a040f20, n=5, flags=-1) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33
#1 0x00007f05b56abf36 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#2 0x00007f05b0b5cb61 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#3 0x00007f05b0b5ccec in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#4 0x00007f05b0b5cd47 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#5 0x00007f05b0b14426 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#6 0x00007f05b0b16899 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#7 0x00007f05b0b16bb8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#8 0x00007f05b0ae4e95 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#9 0x00007f05b0aa12f2 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#10 0x00007f05b0c5de74 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#11 0x00007f05b0c442eb in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#12 0x00007f05b0ae57e1 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#13 0x00007f05b56aeff8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#14 0x00007f05b53c6ee5 in start_thread (arg=0x7f05997ff700) at pthread_create.c:309
#15 0x00007f05b44bab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[root@NoNameForHost Downloads]# pstack 19469
Thread 1 (process 19469):
#0 0x00007f05b44b071d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f05b56ace60 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#2 0x00007f05b0b16346 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#3 0x00007f05b0b167d4 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#4 0x00007f05b0b16bb8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#5 0x00007f05b0ae4e95 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#6 0x00007f05b0aa12f2 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#7 0x00007f05b0c5de74 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#8 0x00007f05b0c442eb in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#9 0x00007f05b0ae57e1 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libxul.so
#10 0x00007f05b56aeff8 in ?? () from /home/Sasi/tor-browser_en-US/Browser/libnspr4.so
#11 0x00007f05b53c6ee5 in start_thread (arg=0x7f05997ff700) at pthread_create.c:309
#12 0x00007f05b44bab8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
**Trac**:
**Username**: Sasi