Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2014-06-06T15:57:34Zhttps://gitlab.torproject.org/legacy/trac/-/issues/11366Hidden service cannot be created2014-06-06T15:57:34ZTracHidden service cannot be createdHidden service creation and activation no longer works in the latest Orbot. Tested all the way up to 13.0.6 (nightly).
I've started a small HTTP server (KWS for Android) on port 8888 and set port 8888 in the "Hidden Services Ports" fie...Hidden service creation and activation no longer works in the latest Orbot. Tested all the way up to 13.0.6 (nightly).
I've started a small HTTP server (KWS for Android) on port 8888 and set port 8888 in the "Hidden Services Ports" field and checked "Hidden Service Hosting". The hostname and private_key files are created (checked from root shell) but the service is not accessible.
Manually adding the service to app_bin/torrc and re-running tor makes the hidden service appear. I added this:
HiddenServiceDir /data/data/org.torproject.android/app_data/
HiddenServicePort 8888 127.0.0.1:8888
If I understand the Orbot sources correctly, the line it tries to add when enabling a service is
HiddenServicePort 8888 **0.0.0.0**:8888 (not sure if that makes a difference)
The ".Onion Hostname" field is _never_ populated, once again if I understand the sources correctly the getHiddenServiceHostname() private method in TorService is never called (in the latest version from Git).
Finally, when using the REQUEST_HS_PORT intent to trigger this externally, I get the dialog asking me to confirm the activation of the hidden service, then Orbot hangs altogether and must be force-killed.
I suspect this is due to the fact that the enableHiddenServicePort method in the Orbot class (https://gitweb.torproject.org/orbot.git/blob/HEAD:/src/org/torproject/android/Orbot.java#l357) is called from https://gitweb.torproject.org/orbot.git/blob/HEAD:/src/org/torproject/android/Orbot.java#l444 upon pressing the Accept button, on the UI thread, so the UI hangs while waiting for the hidden service to be created (and due to the defect above, it never returns).
**Trac**:
**Username**: drazvanNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/11356tor binaries not installed properly2014-05-12T19:34:00ZTractor binaries not installed properlyI've just installed Orbot on my Samsung GT-S5830i device (not rooted) but when I tried to activate Tor, an error showed: "Unable to start Tor: Sorry Tor binaries not installed properly" I tried restarting app, and then turning my phone o...I've just installed Orbot on my Samsung GT-S5830i device (not rooted) but when I tried to activate Tor, an error showed: "Unable to start Tor: Sorry Tor binaries not installed properly" I tried restarting app, and then turning my phone off and on. None worked. When I take a look at the log:
Orbot is starting…
Orbot is starting…
Tor binary exists: /mnt/asec/org.torproject.android-1/lib/libtor.so
Privoxy binary exists: /mnt/asec/org.torproject.android-1/lib/libprivoxy.so
Obfsproxy binary exists: /mnt/asec/org.torproject.android-1/lib/libobfsproxy.so
Xtables binary exists: /mnt/asec/org.torproject.android-1/lib/libxtables.so
app installed on external storage - copying binaries to internal
link CP err=255 out:
rm failed for /data/data/org.torproject.android/app_bin/tor, No such file or directory
link CP err=127 out:
cp: permission denied
tor: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/tor
tor: POST: Is binary exec? false
link CP err=255 out:
rm failed for /data/data/org.torproject.android/app_bin/privoxy, No such file or directory
link CP err=127 out:
cp: permission denied
privoxy: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/privoxy
privoxy: POST: Is binary exec? false
link CP err=255 out:
rm failed for /data/data/org.torproject.android/app_bin/obfsproxy, No such file or directory
link CP err=127 out:
cp: permission denied
obfsproxy: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/obfsproxy
obfsproxy: POST: Is binary exec? false
link CP err=255 out:
rm failed for /data/data/org.torproject.android/app_bin/xtables, No such file or directory
link CP err=127 out:
cp: permission denied
xtables: PRE: Is binary exec? false
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/xtables
xtables: POST: Is binary exec? false
Orbot is starting…
Unable to start Tor: Sorry Tor binary not installed properly: /data/data/org.torproject.android/app_bin/tor
What do I do?
**Trac**:
**Username**: solakgitarNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/11292Orbot has trojan inside2016-04-07T10:55:38ZTracOrbot has trojan insideTOR Android is sceptible to man in the middle attacks (recompiled trojan in app / server list).
**Trac**:
**Username**: techTOR Android is sceptible to man in the middle attacks (recompiled trojan in app / server list).
**Trac**:
**Username**: techNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/11245Orbot bootstraped problem2020-06-13T03:00:57ZTracOrbot bootstraped problemOn my un rooted samsung galaxy note 10.1 Orbot only gets to bootstrapped 25%.
My system information:
Android version: 4.1.2
Model Number: GT - N8010
Log:
Orbot is starting…
Orbot is starting…
Tor binary exists: /data/data/org.torproje...On my un rooted samsung galaxy note 10.1 Orbot only gets to bootstrapped 25%.
My system information:
Android version: 4.1.2
Model Number: GT - N8010
Log:
Orbot is starting…
Orbot is starting…
Tor binary exists: /data/data/org.torproject.android/lib/libtor.so
Privoxy binary exists: /data/data/org.torproject.android/lib/libprivoxy.so
Obfsproxy binary exists: /data/data/org.torproject.android/lib/libobfsproxy.so
Xtables binary exists: /data/data/org.torproject.android/lib/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/data/org.torproject.android/lib/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/data/org.torproject.android/lib/libprivoxy.so
libprivoxy.so: POST: Is binary exec? true
libobfsproxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/lib/libobfsproxy.so
libobfsproxy.so: POST: Is binary exec? true
libxtables.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/lib/libxtables.so
libxtables.so: POST: Is binary exec? true
Orbot is starting…
got tor proc id: 21351
Tor process id=21351
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
updating settings in Tor service
Starting privoxy process
/data/data/org.torproject.android/lib/libprivoxy.so /data/data/org.torproject.android/app_bin/privoxy.config &
orConnStatus (madiba): LAUNCHED
NOTICE: Bootstrapped 10%: Finishing handshake with directory server.
Privoxy is running on port:8118
Privoxy process id=21371
NOTICE: Bootstrapped 15%: Establishing an encrypted directory connection.
orConnStatus (itpol2): CONNECTED
orConnStatus (madiba): CONNECTED
NOTICE: Bootstrapped 20%: Asking for networkstatus consensus.
Circuit (1) BUILT: itpol2
NOTICE: I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
Circuit (2) BUILT: madiba
NOTICE: Bootstrapped 25%: Loading networkstatus consensus.
Circuit (2) CLOSED: madiba
NOTICE: I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
**Trac**:
**Username**: isaac868Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/11099Orbot's changelog isn't updated since 1.0.112014-09-19T19:34:27ZRoger DingledineOrbot's changelog isn't updated since 1.0.11https://gitweb.torproject.org/orbot.git/blob/HEAD:/CHANGELOG
It appears to be up to 13.0.5.
What happened in between? :)
(I ask in this case because I wanted to quickly check whether 13.0.5 has obfsclient turned on, since it looked fr...https://gitweb.torproject.org/orbot.git/blob/HEAD:/CHANGELOG
It appears to be up to 13.0.5.
What happened in between? :)
(I ask in this case because I wanted to quickly check whether 13.0.5 has obfsclient turned on, since it looked from the recent commits like it doesn't, but I don't know.)
Thanks!Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/11022Orbot doesn't start on GT-N7100 (4.3)2016-04-07T11:49:02ZTracOrbot doesn't start on GT-N7100 (4.3)Orbot won't start on unrooted galaxy note 2 with 4.3
Log:
Orbot is starting…
Tor binary exists: /data/app-lib/org.torproject.android-1/libtor.so
Privoxy binary exists: /data/app-lib/org.torproject.android-1/libprivoxy.so
Obfsproxy bina...Orbot won't start on unrooted galaxy note 2 with 4.3
Log:
Orbot is starting…
Tor binary exists: /data/app-lib/org.torproject.android-1/libtor.so
Privoxy binary exists: /data/app-lib/org.torproject.android-1/libprivoxy.so
Obfsproxy binary exists: /data/app-lib/org.torproject.android-1/libobfsproxy.so
Xtables binary exists: /data/app-lib/org.torproject.android-1/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-1/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-1/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-1/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-1/libxtables.so
libxtables.so: POST: Is binary exec? true
Orbot is starting…
Couldn't start Tor process:
**Trac**:
**Username**: graber77Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10798Unable to start Tor if Orbot integrated as system apps2016-04-07T11:34:30ZTracUnable to start Tor if Orbot integrated as system appsI can`t integrate the Orbot as system apps (/system/app/Orbot.apk) becouse not recognize and install the Tor binary from /sysstem/lib/libtor.so
**Trac**:
**Username**: luckasfbI can`t integrate the Orbot as system apps (/system/app/Orbot.apk) becouse not recognize and install the Tor binary from /sysstem/lib/libtor.so
**Trac**:
**Username**: luckasfbNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10794Orbot on Fairphone2014-04-06T16:34:12ZTracOrbot on FairphoneHi,
Orbot on Fairphone behaves weird which blocks using it.
When installed (with root access) and started, the default screen just flashes all the time, not/barely interacting with user input. Anyway, one can not start the functionalit...Hi,
Orbot on Fairphone behaves weird which blocks using it.
When installed (with root access) and started, the default screen just flashes all the time, not/barely interacting with user input. Anyway, one can not start the functionality.
**Versions:**
**Orbot** ... 0.2.3.23-rc.1.0.11-RC5-test2 from F-Droid
**F-Droid** ... 0.58
**Fairphone** ... Front end 1.1 "Caju"
**Android** ... 4.2.2 based on kernel 3.4.5
**Trac**:
**Username**: ax3lNathan FreitasNathan Freitashttps://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/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/10643orweb on android 4.2.2 build 51.2c2016-04-07T11:31:52ZTracorweb on android 4.2.2 build 51.2casus memopad 10 me302c
android 4.2.2 build 51.2c
cannot use orbot orweb or tor. orbot and orweb fail to start tor with log as below. Has been going on for months now,although it used to work fine. Not aware of any updates to android. I b...asus memopad 10 me302c
android 4.2.2 build 51.2c
cannot use orbot orweb or tor. orbot and orweb fail to start tor with log as below. Has been going on for months now,although it used to work fine. Not aware of any updates to android. I blame Google for doing some auto update to some lib which broke it.
Orbot is starting...
Orbot is starting...
checking Tor binaries
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
checking Tor binaries
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting...
Couldn't start Tor process:
Unable to start Tor: Unable to start Tor
Network connectivity is good. Waking Tor up...
Orbot is starting...
Orbot is starting...
checking Tor binaries
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
checking Tor binaries
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting...
Couldn't start Tor process:
Unable to start Tor: Unable to start Tor
Network connectivity is good. Waking Tor up...
**Trac**:
**Username**: javadevNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10639Orbot stops when wifi is drops and reconnects (my ip was shown)2014-08-25T12:14:19ZTracOrbot stops when wifi is drops and reconnects (my ip was shown)Orbot is tor for phones, they only made one design issue...
When orbot is active then I am safe, but when wifi drops and reconnects my normal IP is visible. The worst is that orbot still shows the green "I am connected" light.
PS: pleas...Orbot is tor for phones, they only made one design issue...
When orbot is active then I am safe, but when wifi drops and reconnects my normal IP is visible. The worst is that orbot still shows the green "I am connected" light.
PS: please forward this to orbot devs, I was unable to find their project fast enough so I put the bug here.
**Trac**:
**Username**: tijs14tijsTor: unspecifiedNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10584Let advance user to edit Orbot's torrc file2016-04-07T11:48:03ZTracLet advance user to edit Orbot's torrc fileI want to make my Orbot to use "HidServAuth", because some hidden website
requires to add this. So, please let advanced user to add something like
"HidServAuth" into their config file(using GUI/CLI).
**Trac**:
**Username**: ikurua22I want to make my Orbot to use "HidServAuth", because some hidden website
requires to add this. So, please let advanced user to add something like
"HidServAuth" into their config file(using GUI/CLI).
**Trac**:
**Username**: ikurua22Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/10506Unable to start Tor: Unable to start Tor2018-08-16T00:28:59ZTracUnable to start Tor: Unable to start TorI used Orbot for a couple of weeks without any problems, now it has suddenly stopped to start without any apparent reason.
My phone is a Galaxy S4 i9505 with Android 4.3 with root rights.
Thank you for your help.
```
[ 12-28 16:10:34....I used Orbot for a couple of weeks without any problems, now it has suddenly stopped to start without any apparent reason.
My phone is a Galaxy S4 i9505 with Android 4.3 with root rights.
Thank you for your help.
```
[ 12-28 16:10:34.812 18135:20310 D/Orbot ]
Orbot è in esecuzione...
[ 12-28 16:10:35.052 18135:20310 D/Orbot ]
(re)Setting permission on Tor binary
[ 12-28 16:10:35.072 18135:20310 D/Orbot ]
executing shell cmd: chmod 700 /data/data/org.torproject.android/app_bin/tor; runAsRoot=false;waitFor=true
[ 12-28 16:10:35.082 18135:20310 D/Orbot ]
(re)Setting permission on Privoxy binary
[ 12-28 16:10:35.102 18135:20310 D/Orbot ]
executing shell cmd: chmod 700 /data/data/org.torproject.android/app_bin/privoxy; runAsRoot=false;waitFor=true
[ 12-28 16:10:35.122 18135:20310 D/Orbot ]
(re)Setting permission on Obfsproxy binary
[ 12-28 16:10:35.142 18135:20310 D/Orbot ]
executing shell cmd: chmod 700 /data/data/org.torproject.android/app_bin/obfsproxy; runAsRoot=false;waitFor=true
[ 12-28 16:10:35.192 18135:20310 D/Orbot ]
executing shell cmd: export HOME=/data/data/org.torproject.android/app_bin; runAsRoot=false;waitFor=false
[ 12-28 16:10:35.192 18135:20310 D/Orbot ]
executing shell cmd: /data/data/org.torproject.android/app_bin/tor DataDirectory /data/data/org.torproject.android/app_data -f /data/data/org.torproject.android/app_bin/torrc || exit
; runAsRoot=false;waitFor=false
[ 12-28 16:10:39.497 18135:20310 D/Orbot ]
executing shell cmd: export HOME=/data/data/org.torproject.android/app_bin; runAsRoot=false;waitFor=false
[ 12-28 16:10:39.497 18135:20310 D/Orbot ]
executing shell cmd: /data/data/org.torproject.android/app_bin/tor DataDirectory /data/data/org.torproject.android/app_data -f /data/data/org.torproject.android/app_bin/torrc || exit
; runAsRoot=false;waitFor=false
[ 12-28 16:10:44.051 18135:20310 D/Orbot ]
executing shell cmd: export HOME=/data/data/org.torproject.android/app_bin; runAsRoot=false;waitFor=false
[ 12-28 16:10:44.051 18135:20310 D/Orbot ]
executing shell cmd: /data/data/org.torproject.android/app_bin/tor DataDirectory /data/data/org.torproject.android/app_data -f /data/data/org.torproject.android/app_bin/torrc || exit
; runAsRoot=false;waitFor=false
[ 12-28 16:10:48.545 18135:20310 E/Orbot ]
Unable to start Tor: Unable to start Tor
java.lang.Exception: Unable to start Tor
at org.torproject.android.service.TorService.runTorShellCmd(TorService.java:828)
at org.torproject.android.service.TorService.initTor(TorService.java:676)
at org.torproject.android.service.TorService.run(TorService.java:312)
at java.lang.Thread.run(Thread.java:841)
```
**Trac**:
**Username**: jack80Nathan FreitasNathan Freitashttps://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/10303modernize native build system2018-12-12T05:29:14ZTracmodernize native build systemSince I was doing a bunch of work in this Makefile stuff for GPG-Android, I updated Orbot as well. Attached are the patches.
**Trac**:
**Username**: hansSince I was doing a bunch of work in this Makefile stuff for GPG-Android, I updated Orbot as well. Attached are the patches.
**Trac**:
**Username**: hanshttps://gitlab.torproject.org/legacy/trac/-/issues/9989Orbot stucks on 25%2016-04-07T10:57:53ZTracOrbot stucks on 25%Im trying to start orbot on my samsung galaxy note 2 but it stucks on 25%
im using android 4.1.1, here are logs
Orbot is starting…
Orbot is starting…
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Set...Im trying to start orbot on my samsung galaxy note 2 but it stucks on 25%
im using android 4.1.1, here are logs
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: 3317
Tor process id=3317
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
NOTICE: Bootstrapped 10%: Finishing handshake with directory server.
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.
Starting privoxy process
/data/data/org.torproject.android/app_bin/privoxy /data/data/org.torproject.android/app_bin/privoxy.config &
Privoxy is running on port:8118
Privoxy process id=3370
NOTICE: Bootstrapped 15%: Establishing an encrypted directory connection.
orConnStatus (wau): CONNECTED
NOTICE: Bootstrapped 20%: Asking for networkstatus consensus.
Circuit (1) BUILT: wau
NOTICE: Bootstrapped 25%: Loading networkstatus consensus.
**Trac**:
**Username**: BennyNathan FreitasNathan Freitashttps://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/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/9805Orbot needs updating on F-Droid/Guardian Project Repo2016-04-07T11:33:47ZcypherpunksOrbot needs updating on F-Droid/Guardian Project RepoThe lastest version shown at https://guardianproject.info/repo/ is 12.0.3, while the Play Store and https://guardianproject.info/releases/ have 12.0.5.
The default FDroid repo lists an even older version.
Please update... Thanks.The lastest version shown at https://guardianproject.info/repo/ is 12.0.3, while the Play Store and https://guardianproject.info/releases/ have 12.0.5.
The default FDroid repo lists an even older version.
Please update... Thanks.Nathan FreitasNathan Freitas