Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T02:52:25Zhttps://gitlab.torproject.org/legacy/trac/-/issues/10786orbot (13.0.4a) on android 4.3 didn't start - asus me302c tablet2020-06-13T02:52:25ZTracorbot (13.0.4a) on android 4.3 didn't start - asus me302c tabletIn the orbot start window I get the following information:
Orbot is starting…
Tor binary exists: /data/app-lib/org.torproject.android-2/libtor.so
Privoxy binary exists: /data/app-lib/org.torproject.android-2/libprivoxy.so
Obfsproxy bina...In the orbot start window I get the following information:
Orbot is starting…
Tor binary exists: /data/app-lib/org.torproject.android-2/libtor.so
Privoxy binary exists: /data/app-lib/org.torproject.android-2/libprivoxy.so
Obfsproxy binary exists: /data/app-lib/org.torproject.android-2/libobfsproxy.so
Xtables binary exists: /data/app-lib/org.torproject.android-2/libxtables.so
link RM err=0 out:
link LN err=0 out:
libtor.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-2/libtor.so
libtor.so: POST: Is binary exec? true
tor: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/tor
tor: POST: Is binary exec? true
libprivoxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-2/libprivoxy.so
Orbot is starting…
libprivoxy.so: POST: Is binary exec? true
libobfsproxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-2/libobfsproxy.so
libobfsproxy.so: POST: Is binary exec? true
libxtables.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-2/libxtables.so
libxtables.so: POST: Is binary exec? true
Orbot is starting…
Couldn't start Tor process:
The tablet is unrooted. Tor version v0.2.4.20
**Trac**:
**Username**: wuzi8642Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10782Improve the spec of UniformDH2020-06-13T02:52:23ZGeorge KadianakisImprove the spec of UniformDHUniformDH is used by obfs3 and scramblesuit currently, and it might get used by more projects in the future. Yawning suggested to improve its spec to make its adoption easier.
Yawning suggested adding test vectors. We can look at test v...UniformDH is used by obfs3 and scramblesuit currently, and it might get used by more projects in the future. Yawning suggested to improve its spec to make its adoption easier.
Yawning suggested adding test vectors. We can look at test vectors of other key exchange protocols to see how they should look like. Example:
https://tools.ietf.org/html/rfc6932#appendix-A.1
Some more suggestions:
```
14:54 < Yawning> *looks at the list of gotchas*
14:54 < Yawning> spec should clarify that 0s are inserted if the public key is shorter than 1536 bits (probably obvious)
14:55 < Yawning> Should clarify that abs(p - X) is sent (99% sure that's what happens)
14:55 < Yawning> spec says to simply raise the public key, when it's another mod exp operation
14:56 < Yawning> apart from "wtb test vectors" those where the things i found
15:00 < Yawning> I also was sort of sad that MAX_PADDING isn't a power of 2, but probably too late to change that and that might have been deliberate
```https://gitlab.torproject.org/legacy/trac/-/issues/10762TorBridy should try both SOCKS port 9050 and 91502020-06-13T05:14:03ZMike PerryTorBridy should try both SOCKS port 9050 and 9150TorBridy's SOCKS configuration should try both 9050 and 9150 and use the one that works.
You can crib Torbutton's local tor check here (which requires access to the control port):
https://gitweb.torproject.org/torbutton.git/blob/master:...TorBridy's SOCKS configuration should try both 9050 and 9150 and use the one that works.
You can crib Torbutton's local tor check here (which requires access to the control port):
https://gitweb.torproject.org/torbutton.git/blob/master:/src/chrome/content/torbutton.js#l1701
We wrap that with the option to fall back to the remote check if transproxy is set here:
https://gitweb.torproject.org/torbutton.git/blob/master:/src/chrome/content/torbutton.js#l1675
The remote check is here:
https://gitweb.torproject.org/torbutton.git/blob/master:/src/chrome/content/torbutton.js#l1770
Unfortunately if you perform any network activity (including a remote tor check) with a socks port set, you may run into #8511, causing any hosts you contact to become unreachable after you change SOCKS settings. I am not sure if that caching behavior is present in Thunderbird too. The local tor check won't be affected by this bug, though.Jacob AppelbaumJacob Appelbaumhttps://gitlab.torproject.org/legacy/trac/-/issues/10684Torbirdy does not remember customized settings after enabling it again2020-06-13T06:03:14ZGeorg KoppenTorbirdy does not remember customized settings after enabling it againI usually have my Torbirdy pointed to the ports used by my TBB and it is a bit annoying that I always need to adapt its settings manually after enabling the extension again.I usually have my Torbirdy pointed to the ports used by my TBB and it is a bit annoying that I always need to adapt its settings manually after enabling the extension again.Sukhbir SinghSukhbir Singhhttps://gitlab.torproject.org/legacy/trac/-/issues/10647Orbot completely broken Android 4.1.22020-06-13T02:50:06ZTracOrbot completely broken Android 4.1.2I’ve used Orbot in the past on Android with success with different browsers, but the latest version seems to be completely broken as far as I could tell.
1. No matter what you do no application can see Tor running, so checking the Tor s...I’ve used Orbot in the past on Android with success with different browsers, but the latest version seems to be completely broken as far as I could tell.
1. No matter what you do no application can see Tor running, so checking the Tor status page shows that Tor is inactive even when it’s running.
The phone is rooted and I set “Transparent proxying to ON”
But not “Tor everything”
I then manually added different browsers in the add app section.
I tried in several different browsers including Orweb (marked as ‘latest’).
One browser seemed to realize it was connected to something but returned the message “There is a problem with the proxy server” and could not connect to anything.
All other browsers I tried simply ignore that Tor is running and connect directly (as seen on inspection of an IP checking site (or in Orweb that Check Tor page))
Currently this implementation of Tor on Android is completely unusable, which is a shame as it used to work great.
**Trac**:
**Username**: margoliaNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10371Obfsproxy memory leak2020-06-13T02:44:12ZTracObfsproxy memory leakHi everyone,
I have installed Obfsproxy from Tor project Debian and Python repositories (one v0.2.3 and the other v0.2.4) on my Ubuntu 12.04 LTS. Unfortunately both of them has memory leak problem and if too many users start using the s...Hi everyone,
I have installed Obfsproxy from Tor project Debian and Python repositories (one v0.2.3 and the other v0.2.4) on my Ubuntu 12.04 LTS. Unfortunately both of them has memory leak problem and if too many users start using the server, it makes the RAM full and crashes by itself. How can I generate a full report from this memory leak and place it here to help developers fix the issue?
Thanks.
**Trac**:
**Username**: taher12112https://gitlab.torproject.org/legacy/trac/-/issues/10337I'm not sure what the error is here2020-06-13T02:43:32ZTracI'm not sure what the error is here```
Orbot is starting?
Orbot is starting?
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting?
got tor proc id: 18511
Tor process id=18511
Con...```
Orbot is starting?
Orbot is starting?
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting?
got tor proc id: 18511
Tor process id=18511
Connecting to control port: 9051
SUCCESS connected to control port
SUCCESS authenticated to control port
Starting Tor client? complete.
adding control port event handler
SUCCESS added control port event handler
Starting privoxy process
/data/data/org.torproject.android/app_bin/privoxy /data/data/org.torproject.android/app_bin/privoxy.config &
orConnStatus (CaptainPicard2): LAUNCHED
NOTICE: Bootstrapped 85%: Finishing handshake with first hop.
NOTICE: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
NOTICE: To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features.
Privoxy is running on port:8118
Privoxy process id=18521
Transparent Proxying: enabling...
enabling transproxy for app: com.forshared(10142)
enabling transproxy for app: mgeek.dolphin.[10114(10114)](10114(10114))
enabling transproxy for app: com.humblebundle.library(10107)
enabling transproxy for app: com.opera.browser(10138)
enabling transproxy for app: com.silvermoon.client(10099)
enabling transproxy for app: com.cloudmosa.puffin(10116)
enabling transproxy for app: com.valvesoftware.android.steam.community(10102)
enabling transproxy for app: com.google.android.youtube(10091)
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10142 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10142 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10142 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10067 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10067 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10067 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10114 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10114 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10114 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10107 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10107 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10107 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10138 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10138 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10138 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10099 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10099 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10099 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10116 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10116 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10116 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10102 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10102 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10102 -p udp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p tcp ! -d 127.0.0.1 -m owner --uid-owner 10091 -m tcp --syn -j REDIRECT --to-ports 9040 || exit
/data/data/org.torproject.android/app_bin/iptables -t nat -A OUTPUT -p udp -m owner --uid-owner 10091 -m udp --dport 53 -j REDIRECT --to-ports 5400 || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -d 127.0.0.1 --dport 5400 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -d 127.0.0.1 --dport 9040 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -d 127.0.0.1 --dport 9050 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -d 127.0.0.1 --dport 8118 -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp -o lo -j ACCEPT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p tcp ! -d 127.0.0.1 -j REJECT || exit
/data/data/org.torproject.android/app_bin/iptables -t filter -A OUTPUT -m owner --uid-owner 10091 -p udp ! -d 127.0.0.1 -j REJECT || exit
;errCode=0;resp=FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:478
TorTransProxy resp code: 0
```
It stops at 85% and it doesnt go on to a green onion.
**Trac**:
**Username**: BubblesNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10134Create bananaphone transport for obfsproxy2020-06-13T02:39:45ZGeorge KadianakisCreate bananaphone transport for obfsproxydavid415 has started writing an obfsproxy module for bananaphone.
Code can be found here:
https://github.com/david415/obfsproxy
Discussion thread:
https://lists.torproject.org/pipermail/tor-dev/2013-November/005737.htmldavid415 has started writing an obfsproxy module for bananaphone.
Code can be found here:
https://github.com/david415/obfsproxy
Discussion thread:
https://lists.torproject.org/pipermail/tor-dev/2013-November/005737.htmlhttps://gitlab.torproject.org/legacy/trac/-/issues/9961Orbot contact information cannot be configured2020-06-13T02:36:07ZTracOrbot contact information cannot be configuredOrbot contact information cannot be configured in the settings menu and that leads to an INFO complaint about not set contact information in the log if Orbot is set up as a relay.
**Trac**:
**Username**: mattiOrbot contact information cannot be configured in the settings menu and that leads to an INFO complaint about not set contact information in the log if Orbot is set up as a relay.
**Trac**:
**Username**: mattiNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9902need separate Obfsproxy Windows binary2020-06-13T02:34:55ZTracneed separate Obfsproxy Windows binaryI am using Tor Expert Bundle in Windows. Adding obfs2/obfs3 bridges to torrc always get warnings like this:
```
[warn] We were supposed to connect to bridge 'xxx.xxx.xxx.xxx:xxxxx' using pluggable transport 'obfs2', but we can't find a ...I am using Tor Expert Bundle in Windows. Adding obfs2/obfs3 bridges to torrc always get warnings like this:
```
[warn] We were supposed to connect to bridge 'xxx.xxx.xxx.xxx:xxxxx' using pluggable transport 'obfs2', but we can't find a pluggable transport proxy supporting 'obfs2'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
```
Tor Expert Bundle does not include any pluggable, and as far as I know, obfsproxy does not provide separate binary neither, except the the whole big Tor Browser bundle. I would like keeping use "lightweight" Tor Expert Bundle with obfs support. Could you please provide separate Obfsproxy for Windows?
Thanks.
**Trac**:
**Username**: mosesofmasonhttps://gitlab.torproject.org/legacy/trac/-/issues/9861Orbot: enter multiple bridges, but it only uses one2020-06-13T02:34:00ZTracOrbot: enter multiple bridges, but it only uses oneThis is Orbot 12.0.5 on Android 2.3.x.
* use bridges is checked
* obfuscated bridges is checked
* bridge addresses are 1 per line, IP:port
* I know >1 of these work as I operate some of them for testing
I see a LAUNCHED for every bridg...This is Orbot 12.0.5 on Android 2.3.x.
* use bridges is checked
* obfuscated bridges is checked
* bridge addresses are 1 per line, IP:port
* I know >1 of these work as I operate some of them for testing
I see a LAUNCHED for every bridge when I start up Orbot connecting, but, circuits are only ever built through the second bridge on the list, for whatever reason. I never see log messages about the others other than LAUNCHED at startup.
Please let me know if there is a better place to submit this bug - I can't find it with The Guardian Project.
**Trac**:
**Username**: gmorehouseNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9825-v returns 'unknown' for Obfsproxy.exe from '2.4.17-beta-2-pt3'2020-06-13T02:33:00Zbastik-v returns 'unknown' for Obfsproxy.exe from '2.4.17-beta-2-pt3'> obfsproxy.exe -v
prints out
> unknown
It was included in 'tor-pluggable-transports-browser-2.4.17-beta-2-pt3_en-US.exe' and its (obfsproxy.exe) checksums are:
```
SHA-1: 8690778C86542ABC3596C65EF42903E943C843A9
SHA-256: F75A997308B6...> obfsproxy.exe -v
prints out
> unknown
It was included in 'tor-pluggable-transports-browser-2.4.17-beta-2-pt3_en-US.exe' and its (obfsproxy.exe) checksums are:
```
SHA-1: 8690778C86542ABC3596C65EF42903E943C843A9
SHA-256: F75A997308B689335AEA9705BF7DF57EEA0636CB7C2EB7D75BCAC41389F0F84F
SHA-512: 89459D5189C2490C22FA63AC8509AEF8B7902B38174C73BB2902C57F73DFAFC4EC42B1C361ADDBEB019D7709882589594D94FD264FD20A2712592326596B1107
```https://gitlab.torproject.org/legacy/trac/-/issues/9725'About' section has outdated information2020-06-13T02:30:59ZMatt Pagan'About' section has outdated informationAccording to a user, the 'About' section in Orbot still says it uses Tor 0.2.3.According to a user, the 'About' section in Orbot still says it uses Tor 0.2.3.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/8500Warn the user about possible transparent proxying failure2020-06-13T02:06:22ZTracWarn the user about possible transparent proxying failureThe transparent proxying feature is very likely to fail for a number of reasons, the most common is lack of a firmware supporting the needed iptables magic, or bugs like #3595.
Currently orbot doesn't warn the user when this occurs, lea...The transparent proxying feature is very likely to fail for a number of reasons, the most common is lack of a firmware supporting the needed iptables magic, or bugs like #3595.
Currently orbot doesn't warn the user when this occurs, leading to a false sense of security.
* It only mentions "(Requires root)" in the settings menu: true, but not enough: a special firmware is required too. It should be mentioned (possibly with a link to https://www.torproject.org/docs/android.html.en )
* At orbot startup, a system notification message is issued, saying that transparent proxying has been correctly enabled, even when this is not the case!
Orbot should check more toroughly if transparent proxying is really working, and issue a BIG WARNING in the user interface if this is not the case (or if this can not be detected).
Also the web page at https://www.torproject.org/docs/android.html.en could be improved, though it mentions the requirement for a suitable firmware, the warning could be made more evident (now you have to read the fine print to find out about this limitation).
We could also suggest the user to always check if a particular app is behaving as expected, for example checking the current network connections using a netstat-like tool like Os monitor
(see: http://f-droid.org/repository/browse/?fdfilter=os%20monitor&fdid=com.eolwral.osmonitor )
**Trac**:
**Username**: criNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/8344Orbot BUILD instructions incomplete2020-06-13T02:02:08ZTracOrbot BUILD instructions incompleteThe instructions for building Orbot are incomplete
https://gitweb.torproject.org/orbot.git/blob/9daaec2f84e59ad49cbff29c11eadbe52cc8f4d4:/BUILD
my NDK_BASE
`$NDK_BASEbash: /home/malaparte/src/android/android-ndk-r8c: Is a directory`
...The instructions for building Orbot are incomplete
https://gitweb.torproject.org/orbot.git/blob/9daaec2f84e59ad49cbff29c11eadbe52cc8f4d4:/BUILD
my NDK_BASE
`$NDK_BASEbash: /home/malaparte/src/android/android-ndk-r8c: Is a directory`
and
`make -C ./externalmake: Entering directory `/home/malaparte/src/tor/orbot/external'cd openssl-static && \ ndk-build/bin/sh: 2: ndk-build: not foundmake: *** [openssl-static/obj/local/armeabi/libcrypto.a] Error 127make: Leaving directory `/home/malaparte/src/tor/orbot/externa`
**Trac**:
**Username**: malaparte_https://gitlab.torproject.org/legacy/trac/-/issues/8079WARNING: error starting transparent proxying!2020-06-13T01:55:43ZTracWARNING: error starting transparent proxying!Hi,
I'm getting "WARNING: error starting transparent proxying!". Looks similar to https://trac.torproject.org/projects/tor/ticket/3891 but thing is:
- it was working just after Orbot installation (no warn message + I verified this for ...Hi,
I'm getting "WARNING: error starting transparent proxying!". Looks similar to https://trac.torproject.org/projects/tor/ticket/3891 but thing is:
- it was working just after Orbot installation (no warn message + I verified this for some apps and tethering on https://check.torproject.org/).
- I have CyanogenMod-7.2.0-vision installed (root access is granted for Orbot).
I was trying to use Orbot-bundled iptables but with no change.
I'll try to attach debug log ASAP. If you'll need additional information please let me know.
regards
milo
**Trac**:
**Username**: miloNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/7918HTML5 videos on Dailymotion are not working with TBB2020-06-13T01:52:44ZcypherpunksHTML5 videos on Dailymotion are not working with TBBHTML5 videos on Dailymotion are generating the following error with TBB:
"Media Not Supported
This video could not be loaded, either because the server or network failed or because the format is not supported."HTML5 videos on Dailymotion are generating the following error with TBB:
"Media Not Supported
This video could not be loaded, either because the server or network failed or because the format is not supported."https://gitlab.torproject.org/legacy/trac/-/issues/7532Count unique IPs in an anonymous way2020-06-13T04:05:38ZGeorge KadianakisCount unique IPs in an anonymous wayCurrently, pyobfsproxy (and obfsproxy) keep a list of IPs (or IP hashes) in memory to count connected unique IPs.
Velope suggested that we should find a more privacy-preserving way of counting unique IPs, and he is right.
Aaron suggest...Currently, pyobfsproxy (and obfsproxy) keep a list of IPs (or IP hashes) in memory to count connected unique IPs.
Velope suggested that we should find a more privacy-preserving way of counting unique IPs, and he is right.
Aaron suggested to look into https://git.eff.org/?p=cryptolog.git
and nick suggested to "use a bloom filter; count bits; get a probabilistic answer".Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/7254Orbot WARNs DNSPort and TransPort public address specified2020-06-13T01:40:54ZcypherpunksOrbot WARNs DNSPort and TransPort public address specified"WARN You specified and public address for DNSPort (and TransPort). Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason."
I don't have a good reason an..."WARN You specified and public address for DNSPort (and TransPort). Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason."
I don't have a good reason and want to fix this. There are 4 WARN messages, 1 DNSPort, another TransPort, another DNSPort and another Transport. They repeat as the Orbot log updates itself.
Orbot version 0.2.3.23-rc-1.0.11-RC6 on Samsung EXhibit II running CyanogenMod version 9-20120826_UNOFFICIAL-aancora-tmo
Hopefully I'm posting correctly in the correct place.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/7210Orbot hides the errors of the iptables rules2020-06-13T01:40:12ZTracOrbot hides the errors of the iptables rulesThe transparent proxy of orbot doesn't run in my phone. It shows a error in the notification area.
Yesterday, I decided review the debug log with adb and I found a (in my opinion) important problem in orbot.
You're running the rules of...The transparent proxy of orbot doesn't run in my phone. It shows a error in the notification area.
Yesterday, I decided review the debug log with adb and I found a (in my opinion) important problem in orbot.
You're running the rules of iptables with "/whatever/iptables rules | | exit". I know that my problem is due to some iptables rules but I can't see the error because you hide the error using "| | exit".
You can run each rule individually and check the exit code each time. I think my suggestion is better than the use of "| | exit" because with this orbot doesn't hide the errors.
Sorry if I don't send a patch but my know about java code is near to 0 :)
**Trac**:
**Username**: juanfra684Nathan FreitasNathan Freitas