Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-16T01:10:55Zhttps://gitlab.torproject.org/legacy/trac/-/issues/33063Circuit keeps changing for about 4 times after manually requesting a circuit ...2020-06-16T01:10:55ZTracCircuit keeps changing for about 4 times after manually requesting a circuit change. Result: Can't view videos from sites that are censored in many countriesTitle.
When I try to watch a video on a site that's blocked in many countries, I manually change the circuit until it the video loads. But the circuits keep changing so the video can't be played unless you're very lucky.
How to reproduc...Title.
When I try to watch a video on a site that's blocked in many countries, I manually change the circuit until it the video loads. But the circuits keep changing so the video can't be played unless you're very lucky.
How to reproduce: Establish a new circuit when viewing a website (to see that it keeps changing by itself for about 4 times).
If you need it, I can tell you the website which is most affevted by it from my user experience. But I'm quite sure it's caused by the unwanted auto-changing.
**Trac**:
**Username**: oo7https://gitlab.torproject.org/legacy/trac/-/issues/32923Detached Tor Browser Firedox APK - Option to Customize Configuration - VPN Fu...2020-06-16T01:10:37ZTracDetached Tor Browser Firedox APK - Option to Customize Configuration - VPN Function - AndroidI can't say better than what is said here:
https://www.reddit.com/r/TOR/comments/af9brd/separate_apk_for_torbrowser_alpha_detached_from/
https://blog.torproject.org/comment/282067#comment-282067
https://trac.torproject.org/projects/tor/...I can't say better than what is said here:
https://www.reddit.com/r/TOR/comments/af9brd/separate_apk_for_torbrowser_alpha_detached_from/
https://blog.torproject.org/comment/282067#comment-282067
https://trac.torproject.org/projects/tor/ticket/28786
How are you guys paying zero attention to this critical function?
Taking away user customization cripples the fundamental principles of freedom to choose and speak freely.
Also, as Android' built in Always-on VPN can take advantage of outdated Orbot's VPN feature to tunnel everything over Tor with zero leak when user chooses Block internet without VPN option in Android network settings.
Just need a separate Tor Browser APK that can be used with good old Orbot. Or a new form of something similar that can allow users to choose.
I recently faced a major headache with Facebook's onion address. Whereby it won't allow users to upload anything. Only solution was to choose a customized IP/Node a user had used to access Facebook before. And above feature can help evade such lock downs.
I sincerely hope someone takes this seriously and does something.
Very similar report was filed 13 months before!!!
**Trac**:
**Username**: onestephttps://gitlab.torproject.org/legacy/trac/-/issues/32904Tor build fails with -enable-seccomp on mips2020-06-13T15:53:45ZTracTor build fails with -enable-seccomp on mips
Hi,
I'm trying to make tor seccomp variant for OpenWrt (https://github.com/openwrt/packages/pull/10779)
For MIPS build fails on error:
'mcontext_t' {aka 'struct <anonymous>'} has no member named 'M_SYSCALL'
for arm build is fine.
This...
Hi,
I'm trying to make tor seccomp variant for OpenWrt (https://github.com/openwrt/packages/pull/10779)
For MIPS build fails on error:
'mcontext_t' {aka 'struct <anonymous>'} has no member named 'M_SYSCALL'
for arm build is fine.
This issue is probably related to https://trac.torproject.org/projects/tor/ticket/24424
Log from failed build:
```
src/lib/sandbox/sandbox.c: In function 'sigsys_debugging':
src/lib/sandbox/sandbox.c:1617:35: error: 'mcontext_t' {aka 'struct <anonymous>'} has no member named 'M_SYSCALL'
syscall = (int) ctx->uc_mcontext.M_SYSCALL;
^
Makefile:10599: recipe for target 'src/lib/sandbox/sandbox.o' failed
make[4]: *** [src/lib/sandbox/sandbox.o] Error 1
make[4]: Leaving directory '/home/build/build_dir/build_dir/target-mips_24kc_musl/tor-seccomp/tor-0.4.2.5'
Makefile:5828: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/home/build/build_dir/build_dir/target-mips_24kc_musl/tor-seccomp/tor-0.4.2.5'
Makefile:170: recipe for target '/home/build/build_dir/build_dir/target-mips_24kc_musl/tor-seccomp/tor-0.4.2.5/.built' failed
make[2]: *** [/home/build/build_dir/build_dir/target-mips_24kc_musl/tor-seccomp/tor-0.4.2.5/.built] Error 2
make[2]: Leaving directory '/home/build/openwrt_packages/net/tor'
time: package/feeds/packages/tor/seccomp/compile#2.85#1.40#5.06
package/Makefile:111: recipe for target 'package/feeds/packages/tor/compile' failed
make[1]: *** [package/feeds/packages/tor/compile] Error 2
make[1]: Leaving directory '/home/build/build_dir'
/home/build/build_dir/include/toplevel.mk:218: recipe for target 'package/tor/compile' failed
make: *** [package/tor/compile] Error 2
```
**Trac**:
**Username**: pa-jaTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/33542Orbot not working after the update.2020-06-13T15:52:00ZTracOrbot not working after the update.Hello,
I have an Android 7.1.1 and after updated the Orbot then it can't work. It just show me "Orbot is starting..." . I removed and installed it again, but problem not solved.
How can I fix it?
Thank you.
**Trac**:
**Username**: Ha...Hello,
I have an Android 7.1.1 and after updated the Orbot then it can't work. It just show me "Orbot is starting..." . I removed and installed it again, but problem not solved.
How can I fix it?
Thank you.
**Trac**:
**Username**: Hack3rconhttps://gitlab.torproject.org/legacy/trac/-/issues/33131Bug: buf->datalen >= 0x7fffffff2020-06-13T15:50:38ZcypherpunksBug: buf->datalen >= 0x7fffffffWith
```
BandwidthRate
```
set greater than 2147483646 bytes, for example Config line:
```
BandwidthRate 2147483647
#same as
BandwidthRate 2 GBytes
```
no streams complete in my relay and this Bug message appears:
```
Feb 02 06:...With
```
BandwidthRate
```
set greater than 2147483646 bytes, for example Config line:
```
BandwidthRate 2147483647
#same as
BandwidthRate 2 GBytes
```
no streams complete in my relay and this Bug message appears:
```
Feb 02 06:32:37.000 [warn] {BUG} tor_bug_occurred_(): Bug: buffers_tls.c:73: buf_read_from_tls: Non-fatal assertion !(ASSERT_PREDICT
_UNLIKELY_(buf->datalen >= 0x7fffffff - at_most)) failed. (Future instances of this warning will be silenced.) (on Tor 0.4.2.5 )
Feb 02 06:32:37.000 [warn] {BUG} Bug: Tor 0.4.2.5: Non-fatal assertion !(ASSERT_PREDICT_UNLIKELY_(buf->datalen >= 0x7fffffff - at_mo
st)) failed in buf_read_from_tls at buffers_tls.c:73. (Stack trace not available) (on Tor 0.4.2.5 )
```
Looks like some INT_MAX buffer count trouble to me at least.
```
# BandwidthRate BandwidthRate __N__ bytes|KBytes|MBytes|GBytes|TBytes|KBits|MBits|GBits|TBits
# A token bucket limits the average incoming bandwidth usage on this node
# to the specified number of bytes per second, and the average outgoing
# bandwidth usage to that same value. If you want to run a relay in the
# public network, this needs to be _at the very least_ 75 KBytes for a
# relay (that is, 600 kbits) or 50 KBytes for a bridge (400 kbits) -- but of
# course, more is better; we recommend at least 250 KBytes (2 mbits) if
# possible. (Default: 1 GByte) +
# +
# Note that this option, and other bandwidth-limiting options, apply to TCP
# data only: They do not count TCP headers or DNS traffic. +
# +
# With this option, and in other options that take arguments in bytes,
# KBytes, and so on, other formats are also supported. Notably, "KBytes" can
# also be written as "kilobytes" or "kb"; "MBytes" can be written as
# "megabytes" or "MB"; "kbits" can be written as "kilobits"; and so forth.
# Tor also accepts "byte" and "bit" in the singular.
# The prefixes "tera" and "T" are also recognized.
# If no units are given, we default to bytes.
# To avoid confusion, we recommend writing "bytes" or "bits" explicitly,
# since it's easy to forget that "B" means bytes, not bits.
```Tor: 0.4.3.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/32975Tor Socks unresponsive behaviour after 24-36 hours of runtime2020-06-13T15:50:00ZTracTor Socks unresponsive behaviour after 24-36 hours of runtime__**Error description:**__
After around 1 or 1.5 days the tor socks proxy is getting unresponsive. There is actually no error message from tor itself. Only nyx is claiming to not have available buffer (error 105) and does not start any ...__**Error description:**__
After around 1 or 1.5 days the tor socks proxy is getting unresponsive. There is actually no error message from tor itself. Only nyx is claiming to not have available buffer (error 105) and does not start any more.
__**Error message: **__
`nyx -c .nyx/config -i 9951`
`Unable to connect to 127.0.0.1:9951: [Errno 105] No buffer space available`
__**Workaround:**__
I could solve the problem by deleting the ~/.tor folder and restarting tor.
__**Environment:**__
* 2 CPU VPS with 4GB RAM
* Tor version 0.4.2.5 build and installed from source
(also seen this behaviour on CentOS 7 repo package of tor v0.3.5.8)
* CentOS 7
(Linux version 3.10.0-042stab139.1 (root@kbuild-rh6-x64.eng.sw.ru) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) !#1 SMP Tue Jun 18 12:51:14 MSK 2019)
* non-exit relay
* controle port blocked by iptables for outside connection
* ssh port blocked by iptables for outside connection
**Trac**:
**Username**: ntrnhttps://gitlab.torproject.org/legacy/trac/-/issues/32877Sandbox crash when reloading log configuration2020-06-13T15:49:43ZTracSandbox crash when reloading log configurationA sandbox related crash was reported on the tor-relay mailing list. I'm currently looking into the issue and I expect to have a fix ready soon.
Original report:
-----
Subject: [tor-relays] tor crash on HUP only when SANDBOX is 1
Date:...A sandbox related crash was reported on the tor-relay mailing list. I'm currently looking into the issue and I expect to have a fix ready soon.
Original report:
-----
Subject: [tor-relays] tor crash on HUP only when SANDBOX is 1
Date: Sun, 5 Jan 2020 07:43:45 +0100
From: tor-relay@...
Reply-To: tor-relays@lists.torproject.org
To: tor-relays@lists.torproject.org
Hi,
I'm running an exit relay on a Debian Buster. I installed libseccomp and I've built tor 0.4.2.5 using debuild, like the wiki says.
Today I noticed that tor crashes on HUP signal, only when the Sandbox option is on. I never had this problem.
This is what my log says:
an 05 08:23:10.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Jan 05 08:23:10.000 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jan 05 08:23:10.000 [notice] Read configuration file "/etc/tor/torrc".
Jan 05 08:23:10.000 [notice] Tor 0.4.2.5 opening log file.
============================================================ T= 1578205390
(Sandbox) Caught a bad syscall attempt (syscall dup)
/usr/bin/tor(+0x1fc9fa)[0x561d896b29fa]
/lib/x86_64-linux-gnu/libc.so.6(dup+0x7)[0x7f0bebf4bbc7]
/lib/x86_64-linux-gnu/libc.so.6(dup+0x7)[0x7f0bebf4bbc7]
/usr/bin/tor(tor_log_update_sigsafe_err_fds+0x18b)[0x561d896c699b]
/usr/bin/tor(set_options+0x3c0)[0x561d89642f80]
/usr/bin/tor(options_init_from_string+0x17d)[0x561d896453dd]
/usr/bin/tor(options_init_from_torrc+0x404)[0x561d89645a74]
/usr/bin/tor(+0x5f961)[0x561d89515961]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x22a6c)[0x7f0bec5a3a6c]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7)[0x7f0bec5a4537]
/usr/bin/tor(do_main_loop+0xff)[0x561d8952a3af]
/usr/bin/tor(tor_run_main+0x1105)[0x561d89517d55]
/usr/bin/tor(tor_main+0x3a)[0x561d8951523a]
/usr/bin/tor(main+0x19)[0x561d89514df9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f0bebe8509b]
/usr/bin/tor(_start+0x2a)[0x561d89514e4a]
I'm telling you because i think it could be a bug, but I'm not sure that It's not caused by something else.
At the moment I've disabled Sandbox. Please, let me know if I can fix this in some way, thanks.
**Trac**:
**Username**: pegehttps://gitlab.torproject.org/legacy/trac/-/issues/32868crash: Assertion node->rs->is_possible_guard failed in compute_weighted_band...2020-06-13T15:49:41Ztoralfcrash: Assertion node->rs->is_possible_guard failed in compute_weighted_bandwidths atWith https://github.com/toralf/torutils/blob/f307866d2149bcd3c95df5269b3b48d051f871e9/info.py I monitor the status of my 2 Tor relays. A day before I commented out this section in torrc:
```
#FetchDirInfoEarly 1
#FetchDirInfoExtraEarly 1...With https://github.com/toralf/torutils/blob/f307866d2149bcd3c95df5269b3b48d051f871e9/info.py I monitor the status of my 2 Tor relays. A day before I commented out this section in torrc:
```
#FetchDirInfoEarly 1
#FetchDirInfoExtraEarly 1
#FetchUselessDescriptors 1
#UseMicrodescriptors 0
#DownloadExtraInfo 1
```
Now it took 7 minutes to finish (when those config values were set it was much faster).
But more interesting I realized today I crash of one of both Tor relays:
```
Jan 01 11:12:38.000 [warn] compute_weighted_bandwidths(): Bug: Consensus is missing some bandwidths. Using a naive router selection algorithm (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] tor_assertion_failed_(): Bug: src/feature/nodelist/node_select.c:723: compute_weighted_bandwidths: Assertion node->rs->is_possible_guard failed; aborting. (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: Tor 0.4.2.5: Assertion node->rs->is_possible_guard failed in compute_weighted_bandwidths at src/feature/nodelist/node_select.c:723: . Stack trace: (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(log_backtrace_impl+0x59) [0x55850995e1a9] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(tor_assertion_failed_+0x150) [0x5585099593e0] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(+0x12c474) [0x558509896474] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(frac_nodes_with_descriptors+0x73) [0x558509897373] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(+0x12afb2) [0x558509894fb2] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(count_loading_descriptors_progress+0x6c) [0x558509895b2c] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(connection_dir_reached_eof+0x20e0) [0x558509856f30] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(connection_handle_read+0x980) [0x5585097d2760] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(+0x6d97c) [0x5585097d797c] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/lib64/libevent-2.1.so.6(+0x219ca) [0x7ffbba3cb9ca] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/lib64/libevent-2.1.so.6(event_base_loop+0x4ef) [0x7ffbba3cc54f] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(do_main_loop+0xdd) [0x5585097d8b2d] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(tor_run_main+0x10c5) [0x5585097c6855] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(tor_main+0x46) [0x5585097c4076] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(main+0x19) [0x5585097c3c49] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /lib64/libc.so.6(__libc_start_main+0xeb) [0x7ffbb9d19eab] (on Tor 0.4.2.5 )
Jan 01 11:12:38.000 [err] Bug: /usr/bin/tor(_start+0x2a) [0x5585097c3c9a] (on Tor 0.4.2.5 )
```
System is a hardened Gentoo Linux running 2 relays. The second is not affected.Tor: 0.4.4.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/32859Tor man docs missing DoS log example2020-06-13T15:49:39ZTracTor man docs missing DoS log exampleIn "DENIAL OF SERVICE MITIGATION OPTIONS" man section, there is:
"If any of the DoS mitigations are enabled, a heartbeat message will appear in your log at NOTICE level which looks like:
DoS mitigation since startup: 429042 circuits re...In "DENIAL OF SERVICE MITIGATION OPTIONS" man section, there is:
"If any of the DoS mitigations are enabled, a heartbeat message will appear in your log at NOTICE level which looks like:
DoS mitigation since startup: 429042 circuits rejected, 17 marked addresses.
2238 connections closed. 8052 single hop clients refused.
The following options are useful only for a public relay. They control the Denial of Service mitigation subsystem described above."
However, Tor daemon actually logs:
"DoS mitigation since startup: **__x circuits killed with too many cells__**. y circuits rejected, z marked addresses. m connections closed. n single hop clients refused."
I propose:
1. adding log examples for each of the 3 log mitigation options, in their sections.
This perhaps will make more clear what "too many cells" means, as there seem to be no other documentation sources regarding this.
2. adding the **"x circuits killed with too many cells" **in the final log example.
**Trac**:
**Username**: JoeBeeezTor: unspecifiedDamian JohnsonDamian Johnsonhttps://gitlab.torproject.org/legacy/trac/-/issues/32841sandbox error on 0.4.2.x2020-06-13T15:49:34Zweasel (Peter Palfrader)sandbox error on 0.4.2.x0.4.2.x has (apparently introduced) a sandbox issue. This did not happen on 0.4.1.6 before.
Currently it seems to happen every time at midnight (the hup might come from logrotate)
```
Dec 17 23:55:04.000 [notice] Uploaded signature(s)...0.4.2.x has (apparently introduced) a sandbox issue. This did not happen on 0.4.1.6 before.
Currently it seems to happen every time at midnight (the hup might come from logrotate)
```
Dec 17 23:55:04.000 [notice] Uploaded signature(s) to dirserver 171.25.193.9:443
Dec 17 23:57:30.000 [notice] Time to fetch any signatures that we're missing.
Dec 18 00:00:00.000 [notice] Time to publish the consensus and discard old votes
Dec 18 00:00:00.000 [notice] Published ns consensus
Dec 18 00:00:01.000 [notice] Published microdesc consensus
Dec 18 00:00:04.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Dec 18 00:00:04.000 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Dec 18 00:00:04.000 [notice] Read configuration file "/etc/tor/torrc".
============================================================ T= 1576627205
(Sandbox) Caught a bad syscall attempt (syscall dup)
/usr/bin/tor(+0x1fc9fa)[0x565130b7a9fa]
/lib/x86_64-linux-gnu/libc.so.6(dup+0x7)[0x7f46a89a0bc7]
/lib/x86_64-linux-gnu/libc.so.6(dup+0x7)[0x7f46a89a0bc7]
/usr/bin/tor(tor_log_update_sigsafe_err_fds+0x18b)[0x565130b8e99b]
/usr/bin/tor(set_options+0x3c0)[0x565130b0af80]
/usr/bin/tor(options_init_from_string+0x17d)[0x565130b0d3dd]
/usr/bin/tor(options_init_from_torrc+0x404)[0x565130b0da74]
/usr/bin/tor(+0x5f961)[0x5651309dd961]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x22a6c)[0x7f46a8ff8a6c]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7)[0x7f46a8ff9537]
/usr/bin/tor(do_main_loop+0xff)[0x5651309f23af]
/usr/bin/tor(tor_run_main+0x1105)[0x5651309dfd55]
/usr/bin/tor(tor_main+0x3a)[0x5651309dd23a]
/usr/bin/tor(main+0x19)[0x5651309dcdf9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f46a88da09b]
/usr/bin/tor(_start+0x2a)[0x5651309dce4a]
```
and
```
Dec 20 00:00:00.000 [notice] Published microdesc consensus
Dec 20 00:00:05.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Dec 20 00:00:05.000 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Dec 20 00:00:05.000 [notice] Read configuration file "/etc/tor/torrc".
============================================================ T= 1576800005
(Sandbox) Caught a bad syscall attempt (syscall dup)
/usr/bin/tor(+0x1fc9fa)[0x55ffd52439fa]
/lib/x86_64-linux-gnu/libc.so.6(dup+0x7)[0x7fcb63423bc7]
/lib/x86_64-linux-gnu/libc.so.6(dup+0x7)[0x7fcb63423bc7]
/usr/bin/tor(tor_log_update_sigsafe_err_fds+0x18b)[0x55ffd525799b]
/usr/bin/tor(set_options+0x3c0)[0x55ffd51d3f80]
/usr/bin/tor(options_init_from_string+0x17d)[0x55ffd51d63dd]
/usr/bin/tor(options_init_from_torrc+0x404)[0x55ffd51d6a74]
/usr/bin/tor(+0x5f961)[0x55ffd50a6961]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x22a6c)[0x7fcb63a7ba6c]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x5a7)[0x7fcb63a7c537]
/usr/bin/tor(do_main_loop+0xff)[0x55ffd50bb3af]
/usr/bin/tor(tor_run_main+0x1105)[0x55ffd50a8d55]
/usr/bin/tor(tor_main+0x3a)[0x55ffd50a623a]
/usr/bin/tor(main+0x19)[0x55ffd50a5df9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7fcb6335d09b]
/usr/bin/tor(_start+0x2a)[0x55ffd50a5e4a]
```Tor: 0.4.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/32835regression: log subsystem not closing files on switch back to syslog2020-06-13T15:49:33Zstarlightregression: log subsystem not closing files on switch back to syslog```
SETCONF Log="debug file logfile001"
SETCONF Log="notice syslog"
$ fuser logfile001
logfile001: 31388
```
Did behave correctly in earlier versions.```
SETCONF Log="debug file logfile001"
SETCONF Log="notice syslog"
$ fuser logfile001
logfile001: 31388
```
Did behave correctly in earlier versions.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/32794improve OOS (out-of-sockets) handler victim selection and more2020-06-13T15:49:20Zstarlightimprove OOS (out-of-sockets) handler victim selection and moreI find these revisions a benefit. Will create a branch on GitLab desired.I find these revisions a benefit. Will create a branch on GitLab desired.Tor: 0.4.4.x-finalstarlightstarlighthttps://gitlab.torproject.org/legacy/trac/-/issues/32754X-Ufhash NNTP header when using win-tor2020-06-13T15:49:08ZTracX-Ufhash NNTP header when using win-tor
Hi, all
I'v been using win-tor as a proxy to Thunderbird for posting on newsgroups/usenet and trying to figure out how to query the X-Ufhash NNTP header that returns a long encrypted string to get meaningfull info
X-Ufhash : ZaQJEMf5Jd...
Hi, all
I'v been using win-tor as a proxy to Thunderbird for posting on newsgroups/usenet and trying to figure out how to query the X-Ufhash NNTP header that returns a long encrypted string to get meaningfull info
X-Ufhash : ZaQJEMf5JdvcWEOleKoXo4ljK0hv5rauvinj9qfPFH9gkEPA9vOw7Jqtkzj1SWuX6Q8ZeGvPfoGqFZipnXALeUtU8QLJQ513NMFAEVrNG2z3xZ48ksSy%2BKsEFCn6UJps8tZrNOrMiMKF%2FNofAzkyepiHCjV5CTN9PZ%2BV54b86ugEh9hPoGwPMgxFJJ8naz5uHr%2BHog6zUm4qfvxfrhgiuz17g%2BMO07eqsGuJ
is there some kind of way to decode ?
any ideas ?
thank's in advance
**Trac**:
**Username**: hack-4-freedomhttps://gitlab.torproject.org/legacy/trac/-/issues/33128Orbot is stuck on "starting"2020-02-10T20:20:50ZTracOrbot is stuck on "starting"Good day,
I recently downloaded Orbot on my Android phone and it worked only the first day. Now it is always stuck on "starting" whatever i do. Also the vpn is not working.
Thank you for your support
**Trac**:
**Username**: RonthehunGood day,
I recently downloaded Orbot on my Android phone and it worked only the first day. Now it is always stuck on "starting" whatever i do. Also the vpn is not working.
Thank you for your support
**Trac**:
**Username**: RonthehunNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/33114Crash after update to 16.1.4-BETA-1-tor-0.4.2.5-rc (from f-droid)2020-02-04T20:51:56ZTracCrash after update to 16.1.4-BETA-1-tor-0.4.2.5-rc (from f-droid)Updated my orbot this morning, because I saw an update in the F-Droid store, to 16.1.4-BETA-1-tor-0.4.2.5-rc.
1) I open orbot, the "start screen" loads fine. It shows the unconnected start-state. The background makes this nice pulsing ...Updated my orbot this morning, because I saw an update in the F-Droid store, to 16.1.4-BETA-1-tor-0.4.2.5-rc.
1) I open orbot, the "start screen" loads fine. It shows the unconnected start-state. The background makes this nice pulsing animation
2) I want to start the service, tap "start"/logo.
3) App crashes. It just disappears the second I click start.
4) I then reopen the app, still it is unconnected of course. I enable the VPN slider. The app instantly crashes (again). Even worse, when I now start it again, it crashes (does not show the start screen anymore, either).
I am on android 9. Lineageos 16.0-20191229-NIGHTLY-beryllium. Kernel 4.9.200-perf-g44bd5bc. I use a pocophone f1.
Cannot use the app now.
**Trac**:
**Username**: user45738Nathan FreitasNathan Freitas