Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2010-07-19T20:21:22Zhttps://gitlab.torproject.org/legacy/trac/-/issues/1272Orbot should store Tor files in the cache2010-07-19T20:21:22ZSebastian HahnOrbot should store Tor files in the cacheDunno if that is possible, but it would be neat to get rid of the
cached* files be clearing the cache from the applications menu
thing. i guess that would also allow Orbot to not require the
sd card writing permission?
[Automatically ad...Dunno if that is possible, but it would be neat to get rid of the
cached* files be clearing the cache from the applications menu
thing. i guess that would also allow Orbot to not require the
sd card writing permission?
[Automatically added by flyspray2trac: Operating System: All]Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1277Enabling bridges doesn't force you to enter any2010-03-05T23:00:21ZSebastian HahnEnabling bridges doesn't force you to enter anyThis can't work, if a user needs bridges, they have to enter them (especially if
they don't/can't contact the bridge authority)
[Automatically added by flyspray2trac: Operating System: All]This can't work, if a user needs bridges, they have to enter them (especially if
they don't/can't contact the bridge authority)
[Automatically added by flyspray2trac: Operating System: All]Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1278When enabling bridges, the log view goes entirely blank2010-03-05T23:07:22ZSebastian HahnWhen enabling bridges, the log view goes entirely blankI just enabled bridges (didn't enter any). Going to the log view now shows a black screen.
The symbol is still green, so Tor is probably still running. Disabling bridges again doesn't
make the log return. Shutting Tor down and then going...I just enabled bridges (didn't enter any). Going to the log view now shows a black screen.
The symbol is still green, so Tor is probably still running. Disabling bridges again doesn't
make the log return. Shutting Tor down and then going to the log gives me a log again,
starting with "Shutting down...". After starting Tor again, however (with bridges disabled),
the log is completely blank again.
[Automatically added by flyspray2trac: Operating System: All]Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1280Lack of a web browser with HTTPS proxy support may cause confusion2010-05-26T15:02:29ZPatrick McDonaldLack of a web browser with HTTPS proxy support may cause confusionIn the Tor on Android page, it recommends users of Android 1.6 systems use ProxySurf to use Tor. Since ProxySurf does not support proxy HTTPS and the "Are you using Tor" page only supports HTTPS. This may lead to confusion that Orbot i...In the Tor on Android page, it recommends users of Android 1.6 systems use ProxySurf to use Tor. Since ProxySurf does not support proxy HTTPS and the "Are you using Tor" page only supports HTTPS. This may lead to confusion that Orbot is not proxying correctly when it really is. Either an HTTP service for the "Are you using Tor" page or a note in the documentation would be most helpful.
[Automatically added by flyspray2trac: Operating System: All]Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1284Still problems with options in 0.0.4 release2010-05-26T15:03:59ZSebastian HahnStill problems with options in 0.0.4 releaseThis is going to be qute a few things ;)
I can check "Transparent Proxying" on a non-rooted device, without an
error message
Bridges and Update from Authority should be greyed out and inactive
while Use Bridges is off
Same for Relay P...This is going to be qute a few things ;)
I can check "Transparent Proxying" on a non-rooted device, without an
error message
Bridges and Update from Authority should be greyed out and inactive
while Use Bridges is off
Same for Relay Port and Nickname
Woah, I cannot define my exit policy? Bad idea.
The Reachable Addresses and Reachable Ports options are greyed out
and cannot be changed
I can check both Relaying and Use Bridges feature
I can enter any kind of garbage as the bridge address
I cannot enter the bridge fingerprint, so my bridge can be mitm'd
Generally, before allowing me to save a configuration, Orbot should
run tor with --verify-config to make sure the config is still accepted
and sane stuff has been entered.
Also, when I change config options, it seems they aren't immediately
effective, but rather require Tor to be restarted. The ui should tell the
user or offer a restart option or go ahead and restart.
[Automatically added by flyspray2trac: Operating System: All]Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1286Entering invalid config info makes Orbot go into infinite loop2010-09-09T20:29:04ZSebastian HahnEntering invalid config info makes Orbot go into infinite loopWhen Tor dies due to a config error, orbot tries to start it repeatedly. It doesn't
realize that Tor will never start, and it'll just spam the log with "starting Tor. waiting"
messages.
This loop is not interrupted by clicking the symbo...When Tor dies due to a config error, orbot tries to start it repeatedly. It doesn't
realize that Tor will never start, and it'll just spam the log with "starting Tor. waiting"
messages.
This loop is not interrupted by clicking the symbol again, even though the symbol
goes grey. Orbot keeps trying to start Tor and spamming the log.
The only way to get out of this mess seems to be force-stopping the orbot
application or killing the service.
[Automatically added by flyspray2trac: Operating System: All]Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1287QR download code links to http:// site2014-11-15T09:22:41ZSebastian HahnQR download code links to http:// siteSince we cannot really check signatures, https:// is kind of crucial here
[Automatically added by flyspray2trac: Operating System: All]Since we cannot really check signatures, https:// is kind of crucial here
[Automatically added by flyspray2trac: Operating System: All]Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1292Tor version in About screen is wrong2010-08-04T03:00:02ZSebastian HahnTor version in About screen is wrongUnder 3rd-Party-Software, it says:
Tor v2.0.x: https://www.torproject.org
It should say the exact version of Tor, and Tor version numbers start with 0.
[Automatically added by flyspray2trac: Operating System: All]Under 3rd-Party-Software, it says:
Tor v2.0.x: https://www.torproject.org
It should say the exact version of Tor, and Tor version numbers start with 0.
[Automatically added by flyspray2trac: Operating System: All]Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1308Orbot broken on rooted Droid when root is disallowed2010-08-04T02:39:34ZJacob AppelbaumOrbot broken on rooted Droid when root is disallowedI helped someone install Orbot on a rooted Droid tonight.
Launching Orbot properly prompted the user for root, the user doesn't trust us, and thus denied the request.
This caused Orbot to paint a black screen and hung Orbot. The user was...I helped someone install Orbot on a rooted Droid tonight.
Launching Orbot properly prompted the user for root, the user doesn't trust us, and thus denied the request.
This caused Orbot to paint a black screen and hung Orbot. The user was prompted to quit Orbot by the OS.
The user forced it closed and promptly laughed in my face.
Good times.
[Automatically added by flyspray2trac: Operating System: Other]Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1388Error parsing PID from output of "ps"2012-04-06T01:16:16ZTracError parsing PID from output of "ps"Orbot version: 0.2.2.10-alpha-orbot-0.0.5.apk
Android version: OpenEclair 1.3
Error log:
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): error: unable to parse 'app_92' as integer
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): java.lang.Nu...Orbot version: 0.2.2.10-alpha-orbot-0.0.5.apk
Android version: OpenEclair 1.3
Error log:
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): error: unable to parse 'app_92' as integer
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): java.lang.NumberFormatException: unable to parse 'app_92' as integer
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): at java.lang.Integer.parse(Integer.java:374)
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): at java.lang.Integer.parseInt(Integer.java:363)
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): at java.lang.Integer.parseInt(Integer.java:323)
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): at org.torproject.android.service.TorServiceUtils.findProcessId(TorServiceUtils.java:138)
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): at org.torproject.android.service.TorService.runPrivoxyShellCmd(TorService.java:452)
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): at org.torproject.android.service.TorService.access$000(TorService.java:32)
05-09 16:07:33.754: ERROR/TOR_SERVICE(26501): at org.torproject.android.service.TorService$1.run(TorService.java:384)
Description:
PID is at the first column of the output of "ps":
PID USER VSZ STAT COMMAND
22263 app_92 2736 S /data/data/org.torproject.android/tor -f /data/data/
OpenEclair uses BusyBox. Perhaps the output order is different.
**Trac**:
**Username**: anonymousNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1512Orbot doesn't work on non-rooted Android 2.0 devices2020-06-12T23:43:37ZSteven MurdochOrbot doesn't work on non-rooted Android 2.0 devicesOrbot can't do transparent proxying without root access, but there is no browser for Android 2.0 which supports proxy settings.Orbot can't do transparent proxying without root access, but there is no browser for Android 2.0 which supports proxy settings.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1530Capture sh cmd stdout for debugging errors2010-07-19T15:24:06ZNathan FreitasCapture sh cmd stdout for debugging errorsStdout/stderr from running Privoxy and Tor commands from sh should be captured and logged in OrbotStdout/stderr from running Privoxy and Tor commands from sh should be captured and logged in OrbotNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1531Don't loop ad infinitum in Orbot fails2010-07-19T15:37:32ZNathan FreitasDon't loop ad infinitum in Orbot failsDon't loop ad infinitum on binary exec fails in Orbot. Retrying a few times is okay, but not forever. The users needs to be able to easily check debug output and report problems.Don't loop ad infinitum on binary exec fails in Orbot. Retrying a few times is okay, but not forever. The users needs to be able to easily check debug output and report problems.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1570Orbot install wizard suggested to clarify root / non-root capabilities2010-08-04T03:00:39ZTracOrbot install wizard suggested to clarify root / non-root capabilitiesInstallation for non-root users does not adequately explain what is and is not possible. There is a good chance that inexperienced users may assume that their traffic is magically secure after application install.
Suggest to create a mu...Installation for non-root users does not adequately explain what is and is not possible. There is a good chance that inexperienced users may assume that their traffic is magically secure after application install.
Suggest to create a multi-step install 'wizard' process for a bit more hand-holding that differs for root vs. non-root 1.x (Orweb-capable) vs. non-root 2.x (few options available).
Enhancement closely related to defect #1512 - Orbot doesn't work on non-rooted Android 2.0 devices
**Trac**:
**Username**: djhallidayNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1716Per-app traffic routing prefs not persisted2010-07-23T01:55:17ZTracPer-app traffic routing prefs not persistedversion: Orbot-0.0.8-Beta-071910a.apk
the new per app torification preferences screen within Settings doesn't persist settings.
**Trac**:
**Username**: djhallidayversion: Orbot-0.0.8-Beta-071910a.apk
the new per app torification preferences screen within Settings doesn't persist settings.
**Trac**:
**Username**: djhallidayNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1814Need to setup an Android Market account2010-08-21T12:49:53ZNathan FreitasNeed to setup an Android Market accounthttp://market.android.com/publish
Requires a Google Account, and a $25 one-time payment.
This will be the official Tor Project account for releasing the Orbot application into the market.http://market.android.com/publish
Requires a Google Account, and a $25 one-time payment.
This will be the official Tor Project account for releasing the Orbot application into the market.Android (Orbot): 1.0Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1875Automate Orbot builds2013-10-16T18:54:20ZErinn ClarkAutomate Orbot buildsOrbot builds are currently done by hand. The process is pretty simple, so it ought to be easy to automate. Nathan might have some ideas of things he wants added to this, so I'm adding him to the cc.Orbot builds are currently done by hand. The process is pretty simple, so it ought to be easy to automate. Nathan might have some ideas of things he wants added to this, so I'm adding him to the cc.Deliverable-Mar2011Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1927orbot release 1.0.1 is missing changelog2011-02-17T17:33:30ZAndrew Lewmanorbot release 1.0.1 is missing changelogThe last changelog entry is for 1.0.The last changelog entry is for 1.0.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1934Updated Chinese Translation2011-11-04T17:21:56ZTracUpdated Chinese TranslationI've updated chinese translation for Orbot (svn trunk).
Patch will be attached.
**Trac**:
**Username**: pen9u1nI've updated chinese translation for Orbot (svn trunk).
Patch will be attached.
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1935Orbot UI hang in log view activity2011-05-03T07:11:12ZTracOrbot UI hang in log view activityDevice: Nexus one
Orbot: Orbot-1.0.3-Alpha-Experimental-100909c.apk
Steps to reproducer:
1. Start Orbot, and connect to Tor
2. After successfully connected to Tor, (May wait some time)
3. Press "Log" in the Menu
Expected: I can see th...Device: Nexus one
Orbot: Orbot-1.0.3-Alpha-Experimental-100909c.apk
Steps to reproducer:
1. Start Orbot, and connect to Tor
2. After successfully connected to Tor, (May wait some time)
3. Press "Log" in the Menu
Expected: I can see the log
Actually: I got a empty view
Then I press "return" button on my device, I got the main windows or Orbot.
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1957Do not start/stop tor when touch on log view2011-02-15T22:59:33ZTracDo not start/stop tor when touch on log viewDevice: Nexus one
Orbot 1.0.4-RC4-2010920
1. Switch to Log View
2. Touch on the screen
Unexpcepted: Tor stop/started after I touch screen.
I guess it's caused by the log view is not full fill the whole view, I can see it expanding whe...Device: Nexus one
Orbot 1.0.4-RC4-2010920
1. Switch to Log View
2. Touch on the screen
Unexpcepted: Tor stop/started after I touch screen.
I guess it's caused by the log view is not full fill the whole view, I can see it expanding when more log added into view.
BTW: the font size is too small in log view.
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1958Orbot stopped after I press Home/Back button2011-05-03T07:00:49ZTracOrbot stopped after I press Home/Back buttonDevice: Nexus one
Orbot 1.0.4-RC4-2010920
1. Start Orbot and connect to Tor successfully.
2. Press Home/Back button on device, return to home screen.
wait a moment, Orbot notfy that it has been stopped.
not always, but both in 1.0.3, ...Device: Nexus one
Orbot 1.0.4-RC4-2010920
1. Start Orbot and connect to Tor successfully.
2. Press Home/Back button on device, return to home screen.
wait a moment, Orbot notfy that it has been stopped.
not always, but both in 1.0.3, 1.0.4
**Trac**:
**Username**: pen9u1nNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/1960Orbot website points to wrong svn location2011-02-15T23:08:58ZRoger DingledineOrbot website points to wrong svn locationhttps://guardianproject.info/apps/orbot/
is sending people to
https://svn.torproject.org/cgi-bin/viewvc.cgi/projects/android/trunk/Orbot/
which isn't going to work. You can't svn co from a cgi script.
The correct url is
https://svn.torp...https://guardianproject.info/apps/orbot/
is sending people to
https://svn.torproject.org/cgi-bin/viewvc.cgi/projects/android/trunk/Orbot/
which isn't going to work. You can't svn co from a cgi script.
The correct url is
https://svn.torproject.org/svn/projects/android/trunk/Orbot/Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2069Orbot fails to start if configured as a relay2020-06-12T23:54:18ZTracOrbot fails to start if configured as a relayOrbot version: 1.0.4
Phone: Nexus One, 2.2.1 FRG83
Repo steps:
In Settings, select "Relaying", set "Relay Port" to 9001 set "Relay nickname". Press back. Press to start. Orbot turns yellow:
"set_options(): Bug: Acting on config option...Orbot version: 1.0.4
Phone: Nexus One, 2.2.1 FRG83
Repo steps:
In Settings, select "Relaying", set "Relay Port" to 9001 set "Relay nickname". Press back. Press to start. Orbot turns yellow:
"set_options(): Bug: Acting on config options left us in a broken state. Dying."
Selected lines from the log:
Orbit is starting....
got tor proc id: 18938
Tor process id=18938
Starting Tor...
Setting up control...
SUCCESS connected to control port
SUCCESS authenticated to control port
Setting up control...complete.
adding control port event handle
SUCCESS added control port event handle
You ContactInfo config option is not set .Please ...
Opening OR listener on 0.0.0.0:9001
You Tor server's identify key fingerprint is 'Skevek 73DD7A435...'
Unable to stat resolver configuration in '/etc/resolv.conf': No such file or directory
set_options(): Bug: Acting on config options left us in a broken state. Dying.
**Trac**:
**Username**: aglNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2168Privoxy file missing from Orbot2012-04-06T01:04:03ZTracPrivoxy file missing from OrbotOn Google Android Devphone 1 with firmware 1.6 and using Orweb version 1 with Orbot Version 11 (Which is the first release in the Android market): When Privoxy encounters Error 500 I get the message
500 Internal Privoxy Error
Privoxy ...On Google Android Devphone 1 with firmware 1.6 and using Orweb version 1 with Orbot Version 11 (Which is the first release in the Android market): When Privoxy encounters Error 500 I get the message
500 Internal Privoxy Error
Privoxy encountered an error while processing your request:
Could not load template file forwarding - failed or one of its included components.
Please contact your proxy administrator.
If you are the proxy administrator, please put the required file(s)in the (confdir)/templates directory. The location of the (confdir) directory is specified in the main Privoxy config file. (It's typically the Privoxy Install directory, or /etc/privoxy/).
As a user rather than a technogeek, I have no idea how to fix this, but I think it should be in the Orbot installation package.
**Trac**:
**Username**: 4u2guessNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2423OrBot transproxy silently fails open2011-05-10T01:57:25ZcypherpunksOrBot transproxy silently fails openOn rooted phones that lack proper modules or iptables commands, OrBot seems to fail silently without informing the user that their selected apps are not torified. Minimally, it should verify the iptables rules it attempts to create are s...On rooted phones that lack proper modules or iptables commands, OrBot seems to fail silently without informing the user that their selected apps are not torified. Minimally, it should verify the iptables rules it attempts to create are still present after it creates them.
Ideally, it should also ping check.torproject.org, which provides a minimal, easy to parse XHTML response at https://check.torproject.org/?TorButton=trueNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2424Android purges firewall rules after network disable/airplane mode.2020-06-13T00:01:39ZcypherpunksAndroid purges firewall rules after network disable/airplane mode.Setting my phone to disable data access and/or enable airplane mode seems to cause the transproxy iptables rules created by OrBot to get silently flushed. After re-enabling, all apps access everything without tor, until I go into the orb...Setting my phone to disable data access and/or enable airplane mode seems to cause the transproxy iptables rules created by OrBot to get silently flushed. After re-enabling, all apps access everything without tor, until I go into the orbot config screen to cause it to reapply them.
OrBot should listen for these network disable/loss/disconnect events if possible, and reinstate the iptables rules after this happens.
Someone should also test if switching from cell data to+from wifi also triggers this iptables reset. I have not tested that yet.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2493orbot is not working on Android (Froyo 2.2)2011-02-06T12:14:14ZTracorbot is not working on Android (Froyo 2.2)Hi,
I have a Samsung Galaxy S with Android Froyo 2.2 and installed the Orbot 1.04 .
I have followed your instructions from here http://www.torproject.org/docs/android.html.en
but after Orbot is activated (green window) and check if Tor...Hi,
I have a Samsung Galaxy S with Android Froyo 2.2 and installed the Orbot 1.04 .
I have followed your instructions from here http://www.torproject.org/docs/android.html.en
but after Orbot is activated (green window) and check if Tor is working with your web check page, it says " sorry but you are not using Tor"
It looks like I'm not the only one that I have this issue, others from xda-developers have the same issue.
Is it possible to fix this ?
Kind Regards,
Dinu
**Trac**:
**Username**: dinocNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2635Orbot continuously tries to kill Privoxy using the wrong PID2011-05-10T02:01:20ZNathan FreitasOrbot continuously tries to kill Privoxy using the wrong PIDorbot 1.0.4
kernel: 2.6.29
rooted: yes
On my Android BladeVillain ROM (based on Android 2.2) orbot logs hundreds of attempts to kill Privoxy, but using the User-ID of the privoxy process instead of the PID. This consumes almost all the C...orbot 1.0.4
kernel: 2.6.29
rooted: yes
On my Android BladeVillain ROM (based on Android 2.2) orbot logs hundreds of attempts to kill Privoxy, but using the User-ID of the privoxy process instead of the PID. This consumes almost all the CPU, making it look like the orbot app has crashed and preventing orbot from starting up correctly or shutting down correctly.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2636Orbot doesn't redirect connections to tor2011-05-10T02:04:20ZNathan FreitasOrbot doesn't redirect connections to tororbot 1.0.4
kernel: 2.6.29
ROM: BladeVillain1.1.0
rooted: yes
Orbot seems to start ok (according to the log) after requesting Superuser permission, but doesn't seem to generate any iptables entries.
("iptables -L" doesn't show any active...orbot 1.0.4
kernel: 2.6.29
ROM: BladeVillain1.1.0
rooted: yes
Orbot seems to start ok (according to the log) after requesting Superuser permission, but doesn't seem to generate any iptables entries.
("iptables -L" doesn't show any active chains). I can't see any mention of iptables in the log, but I don't know if there should be anything.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2662Gibberbot does not stay signed in2011-03-06T05:05:11ZcypherpunksGibberbot does not stay signed inGibberbot should have an option to stay signed in. I keep getting logged out after leaving the app in the background...Gibberbot should have an option to stay signed in. I keep getting logged out after leaving the app in the background...Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2761Orbot Service not shutting down2020-06-13T00:08:40ZTracOrbot Service not shutting downBehaviour:
When closing tor network with big Button and exiting Orbot after tor is "deactivated", privoxy is still running and the Orbot service is not stopped.
Actions:
- Killing Privoxy from shell stops the privoxy process (OK)
- Kill...Behaviour:
When closing tor network with big Button and exiting Orbot after tor is "deactivated", privoxy is still running and the Orbot service is not stopped.
Actions:
- Killing Privoxy from shell stops the privoxy process (OK)
- Killing Orbot process simply restarts the process (BAD)
Env:
- Running Orbot v1.0.4.1
- Android Froyo 2.2.1 speedmod kernel
- Samsung Galaxy
**Trac**:
**Username**: AlBotNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2775Orbot doesn't show iptables failure2011-05-10T02:03:47ZChristian FrommeOrbot doesn't show iptables failureOrbot iptables settings fail to apply for Orbot on Android 2.3.3, cm7 port. The problem seems to be related to bionic library, not Orbot itself. Still, maybe Orbot should not show a green onion in case the iptables command fails.
Here i...Orbot iptables settings fail to apply for Orbot on Android 2.3.3, cm7 port. The problem seems to be related to bionic library, not Orbot itself. Still, maybe Orbot should not show a green onion in case the iptables command fails.
Here is an example of how iptables fails on 2.3.3.
```
# whoami
root
# iptables -A INPUT -p icmp -j ACCEPT
getsockopt for multiport failed strangely: No such file or directory
getsockopt for multiport failed strangely: No such file or directory
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:378
```
A Google search for the error message shows that lots of other projects also encouter the same problem.
Thanks to cubi for testing & reporting this issue.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2935privoxy not the right http proxy2012-04-06T01:01:45ZRoger Dingledineprivoxy not the right http proxyprivoxy doesn't do http 1.1, so no pipelining for you. Also, it reads the whole page before it passes any of it on to Tor, introducing considerable latency from the user's perspective.
You might be happier moving to polipo, assuming it ...privoxy doesn't do http 1.1, so no pipelining for you. Also, it reads the whole page before it passes any of it on to Tor, introducing considerable latency from the user's perspective.
You might be happier moving to polipo, assuming it builds in android land. (Does it?)
You will likely be happier still moving to 'no http proxy', if you can manage it. (Can you?)Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2981Progress bar in an infinite loop while loading2020-06-13T00:12:50ZSathyanarayanan GunasekaranProgress bar in an infinite loop while loadingOrbot Version - 1.0.5
Device - HTC Legend
1. Start Orbot
2. While the progress bar loads, press Back/home
3. Return to Orbot
The progress bar is in an infinite loop, with no text.
The only way to exit, is to force quit or reboot.Orbot Version - 1.0.5
Device - HTC Legend
1. Start Orbot
2. While the progress bar loads, press Back/home
3. Return to Orbot
The progress bar is in an infinite loop, with no text.
The only way to exit, is to force quit or reboot.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2989ORBot install fails when installing/uncompressing tor binary2011-05-10T02:05:42ZTracORBot install fails when installing/uncompressing tor binaryThis is a bug report for 0.2.2.22-orbot-alpha-1.0.5.20110417a-dev, running on CM6.1.0-RC2 (Desire HD).
It seems like ORBot fails to unzip the tor binary to the data directory, as it is too large to fit in the dedicated memory for that o...This is a bug report for 0.2.2.22-orbot-alpha-1.0.5.20110417a-dev, running on CM6.1.0-RC2 (Desire HD).
It seems like ORBot fails to unzip the tor binary to the data directory, as it is too large to fit in the dedicated memory for that operation (...or so Google tells me).
Additionally (not sure if that should be a second bug), ORBot still declares the operation successful, even though it is caught by the exception handler. This, of course, leads to ORBot trying (and failing) to start afterwards, constantly receiving -1 as the pid (if you want to detect unrecoverable situations, that _might_ be one approach - keep in mind that I haven't read the corresponding code, maybe ORBot is already doing that).
Logcat (useless messages redacted):
---------------
I/ActivityManager( 1487): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.torproject.android/.Orbot }
I/ActivityManager( 1487): Start proc org.torproject.android for activity org.torproject.android/.Orbot: pid=23812 uid=10105 gids={3003}
I/ORBOT (23812): service started: org.torproject.android.service.TOR_SERVICE
D/ORBOT (23812): Tor binary exists=false
D/ORBOT (23812): Privoxy binary exists=false
D/asset (23812): Data exceeds UNCOMPRESS_DATA_MAX (3188430 vs 3145728)
D/ORBOT (23812): Error writing output file '/data/data/org.torproject.android/app_bin/tor': java.io.IOException
D/ORBOT (23812): SUCCESS: installed tor, privoxy binaries from raw
------------
Should I try running it on CM7 instead?
**Trac**:
**Username**: __sporkbombNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/2993ORBot Alpha [GUI]: Blank semi-permanent status box2011-05-10T02:06:06ZTracORBot Alpha [GUI]: Blank semi-permanent status boxVersion: 0.2.2.22-orbot-alpha-1.0.5.20110417a-dev
ROM: CM 7.0.2-DesireHD
Side note: Should bugs like this posted on guardian-dev instead?
The ORBot status box (in the center of the screen, should probably contain status messages regard...Version: 0.2.2.22-orbot-alpha-1.0.5.20110417a-dev
ROM: CM 7.0.2-DesireHD
Side note: Should bugs like this posted on guardian-dev instead?
The ORBot status box (in the center of the screen, should probably contain status messages regarding connection establishment) remains black, only containing the white "ring" animation. Meanwhile, the Android in the background remains yellow.
This remains constant - even if the connection is already established and transproxying enabled - until the screen is re-drawn (e.g. by unlocking the screen after the blanking timeout or by selecting any of the ORBot notificiations), at which point the expected UI state is established (green Android, no status box, "Connected to Tor").
Expected behaviour is of course that the "connected" UI state is displayed as soon as ORBot has finished connection setup.
**Trac**:
**Username**: __sporkbombNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3081Orbot start up problem/looping dialog2020-06-13T00:14:36ZNathan FreitasOrbot start up problem/looping dialog#1. Almost always it takes two (sometimes three) starts for Orbot to connect properly. One symptom is in #2 below. Another is that all looks good (connection sequence looks correct, drop down alert looks correct) but testing via check....#1. Almost always it takes two (sometimes three) starts for Orbot to connect properly. One symptom is in #2 below. Another is that all looks good (connection sequence looks correct, drop down alert looks correct) but testing via check.torproject.org shows no connection. Exiting and restarting usually yields a working connection.
#2. Frequently on the first try, the app shows the spinning white circular pattern in the black rectangle in front of the Orbot logo, "Orbot is starting" message under the logo, and then stays in that mode indefinitely.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3082Orbot problems on rooted x10 with jit installed.2020-06-13T00:14:36ZNathan FreitasOrbot problems on rooted x10 with jit installed.JIT is the just in time compiler developed by someone on XDA for the X10. Apparently SE pulled it from the 2.1 build due to a risk of processor overheating. When you put it back you get a performance increase of 50% based on benchmarks...JIT is the just in time compiler developed by someone on XDA for the X10. Apparently SE pulled it from the 2.1 build due to a risk of processor overheating. When you put it back you get a performance increase of 50% based on benchmarks, with the slight cost that when the processor is maxed out it sometimes casues a reboot, although i dont think that was the issue here. Not had a problem with overheating yet, but got safeguards in place.
Went into settings (note given previous problems I had disabled start on boot, might be worth making this default initially?) and enabled logs, attatched to this email.
Note display was helpful on one attempt but blank apart from waiting animation on 2 others. No easy way to stop process apart from task killer.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3226Screen orientation change ends configuration wizard2011-10-31T03:40:43ZTracScreen orientation change ends configuration wizard**moved from github issue #6 (https://github.com/guardianproject/Orbot/issues/6)**
Last reproduced on Orbot-1.0.5.2 on CM-7.05132011-NIGHTLY-N1
When the screen orientation changes while the configuration wizard is active, the user gets...**moved from github issue #6 (https://github.com/guardianproject/Orbot/issues/6)**
Last reproduced on Orbot-1.0.5.2 on CM-7.05132011-NIGHTLY-N1
When the screen orientation changes while the configuration wizard is active, the user gets dropped into the Orbot main activity screen. There seems to be no way to resume the wizard. This does not seem to impair any of Orbot's functions.
I observed the same issue with other pop-up activities like the first Tor connection confirmation.
**Trac**:
**Username**: djhallidayNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3227Orbot notification should be 'ongoing' not 'standard'2012-04-06T00:59:32ZTracOrbot notification should be 'ongoing' not 'standard'**migrated from github issue #5: https://github.com/guardianproject/Orbot/issues/5**
Orbot currently pushes a standard, dismissable notification to the Android system notifications bar when a circuit is established. It is more applicabl...**migrated from github issue #5: https://github.com/guardianproject/Orbot/issues/5**
Orbot currently pushes a standard, dismissable notification to the Android system notifications bar when a circuit is established. It is more applicable for remote services such as Orbot to display an ongoing notification instead.
**Trac**:
**Username**: djhallidayNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3253Orbot fails to work on Samsung 3.x Google IO device2011-11-03T18:40:56ZJacob AppelbaumOrbot fails to work on Samsung 3.x Google IO devicetor reports that it is loading the networkstatus consensus and sends an alert about "connected to the tor network" - however, it stays stuck at 25% with a yellow orbot icon.tor reports that it is loading the networkstatus consensus and sends an alert about "connected to the tor network" - however, it stays stuck at 25% with a yellow orbot icon.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3254Implement newnym2013-10-16T18:53:36ZJacob AppelbaumImplement newnymIt would be really useful to have newnym support in Orbot.It would be really useful to have newnym support in Orbot.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3572Disable Orbot transparent redirect for rfc1918 & localhost2020-06-13T00:23:02ZTracDisable Orbot transparent redirect for rfc1918 & localhostThe iptables rules setup on orbot to redirect all traffic through tor cause problems for when I'm on my wireless on my RFC1918 network or trying to access stuff bound onto localhost (vnc, ...).
Could the transparent redirect scripts be ...The iptables rules setup on orbot to redirect all traffic through tor cause problems for when I'm on my wireless on my RFC1918 network or trying to access stuff bound onto localhost (vnc, ...).
Could the transparent redirect scripts be updated to ignore RFC1918 & 127.0.0.X addresses?
**Trac**:
**Username**: dmz@zzservers.comNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3595Connections with IPv4-mapped IPv6 addresses bypass transproxy2020-06-13T02:06:22ZTracConnections with IPv4-mapped IPv6 addresses bypass transproxyA user (DEplan on #guardianproject) reported that Gibberbot was using his real IP despite Orbot's transproxy being turned on; further research led to the conclusion that recent releases of Android seem to use IPv4-mapped IPv6 adresses fo...A user (DEplan on #guardianproject) reported that Gibberbot was using his real IP despite Orbot's transproxy being turned on; further research led to the conclusion that recent releases of Android seem to use IPv4-mapped IPv6 adresses for a large portion of connections. For examples, please see http://pastebin.com/Z4KDDq40. These connections completely bypass transproxy.
I am not yet sure about the circumstances under which Android employs these addresses.
The problems in finding a solution are that Android usually does not include ip6tables (though Orbot could simply package that) and kernels do usually not include IPv6 netfilter modules. The latter is a major issue, since Orbot can't package modules for every single kernel a user might be running.
As a side note, IPv6 does not support NAT (which is what transproxying is based on).
I'll try to figure out what triggers this behaviour of Android and find possible solutions (using sysctl to disable IPv6 does not solve it).
**Trac**:
**Username**: __sporkbombNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3775Permission error on Orbot2020-06-13T00:27:16ZTracPermission error on OrbotThere's some kind of problem with permissions in Orbot. I'm not sure if this happens only to me, but when I try to start Tor, it cannot access cache/control_auth_cookie. I can chmod it every time, but it is a bit annoying.
**Trac**:
...There's some kind of problem with permissions in Orbot. I'm not sure if this happens only to me, but when I try to start Tor, it cannot access cache/control_auth_cookie. I can chmod it every time, but it is a bit annoying.
**Trac**:
**Username**: etnmichNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/3891Transparent proxy not woking2011-10-31T03:39:00ZcypherpunksTransparent proxy not wokingHi,
I have a Sony Ericsson X8,Android 2.1 – update 1.
I have installed Orbot from Android market.
Installation OK. Root allowed – “excellent”.
Starting Orbot I get:
- Setting up full transparent proxy
- Warning: error starting transpar...Hi,
I have a Sony Ericsson X8,Android 2.1 – update 1.
I have installed Orbot from Android market.
Installation OK. Root allowed – “excellent”.
Starting Orbot I get:
- Setting up full transparent proxy
- Warning: error starting transparent proxy
- Proxying!
- Bootstrapped 100% Done
Tor network is running
Check indicates: Sorry. You are not using Tor.
The transparent proxy do not work for me. (Always DISABLED)
What is wrong?
Regards STHnetNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4044Orbot release that includes 0.2.2.x stable?2011-10-31T03:37:29ZRoger DingledineOrbot release that includes 0.2.2.x stable?I notice that the last orbot release uses Tor 0.2.2.25-alpha.
Here are some major fixes since then that your users might like:
```
- Use the same circuit timeout for client-side introduction
circuits as for other four-hop circ...I notice that the last orbot release uses Tor 0.2.2.25-alpha.
Here are some major fixes since then that your users might like:
```
- Use the same circuit timeout for client-side introduction
circuits as for other four-hop circuits, rather than the timeout
for single-hop directory-fetch circuits; the shorter timeout may
have been appropriate with the static circuit build timeout in
0.2.1.x and earlier, but caused many hidden service access attempts
to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
on 0.2.2.2-alpha; fixes another part of bug 1297.
- In ticket 2511 we fixed a case where you could use an unconfigured
bridge if you had configured it as a bridge the last time you ran
Tor. Now fix another edge case: if you had configured it as a bridge
but then switched to a different bridge via the controller, you
would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
fixes bug 3321.
- When the controller configures a new bridge, don't wait 10 to 60
seconds before trying to fetch its descriptor. Bugfix on
0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
- Replace all potentially sensitive memory comparison operations
with versions whose runtime does not depend on the data being
compared. This will help resist a class of attacks where an
adversary can use variations in timing information to learn
sensitive data. Fix for one case of bug 3122. (Safe memcmp
implementation by Robert Ransom based partially on code by DJB.)
- When receiving a hidden service descriptor, check that it is for
the hidden service we wanted. Previously, Tor would store any
hidden service descriptors that a directory gave it, whether it
wanted them or not. This wouldn't have let an attacker impersonate
a hidden service, but it did let directories pre-seed a client
with descriptors that it didn't want. Bugfix on 0.0.6.
```Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4061Orbot on non-rooted Honeycomb 3.2 can use hidden built-in Proxy2016-04-07T11:21:35ZTracOrbot on non-rooted Honeycomb 3.2 can use hidden built-in ProxyThe help text in Orbot for non-rooted systems suggests using approved applications. One such app is Firefox + the Proxy plugin. I am running on an ASUS Transformer Honeycomb 3.2 and having used the PDA tablet app, knew there was a way ...The help text in Orbot for non-rooted systems suggests using approved applications. One such app is Firefox + the Proxy plugin. I am running on an ASUS Transformer Honeycomb 3.2 and having used the PDA tablet app, knew there was a way to set up a proxy port forward in the OS itself.
A Moto XOOM forum post pointed me to an app called "AnyCut" which lets you make a desktop widget for almost any system component or app. One of the components is "Proxy Settings". Thus:
1. Run Orbot
2. Run "Proxy Settings". Fill in the form to point to 127.0.0.1:8118
3. Stock web browser will automatically use this proxy.
Interested in helping with research on this.
**Trac**:
**Username**: scramblerNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4111orbot just keeps saying waiting and after a while becomes deactivated2011-10-31T03:36:18ZTracorbot just keeps saying waiting and after a while becomes deactivatedSo for the first time I installed orbot it worked fine and connected. But for some reason the next day it just kept showing waiting and flash some other line which I couldnt read cause it would go back to waiting very fast. I tried unins...So for the first time I installed orbot it worked fine and connected. But for some reason the next day it just kept showing waiting and flash some other line which I couldnt read cause it would go back to waiting very fast. I tried uninstalling and then restarting my htc sensation 4g and installed it again but no luck.
**Trac**:
**Username**: ramonNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4385Wizard comes up when you try to exit orbot2020-06-13T00:39:30ZSathyanarayanan GunasekaranWizard comes up when you try to exit orbotThe wizard doesn't kill itself due to android's weird handling of activities, so we manually have to kill it once the user clicks on "Options -> Exit".The wizard doesn't kill itself due to android's weird handling of activities, so we manually have to kill it once the user clicks on "Options -> Exit".Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4423Orbot flushes all foreign iptables rules2020-06-13T00:40:06ZTracOrbot flushes all foreign iptables rulesRegardless of whether transparency proxy is enabled or not, all foreign iptables rules get flushed when connecting or disconnecting to/from Tor.
Iptables chains stay untouched.
This is a big problem when using iptables based firewalls ...Regardless of whether transparency proxy is enabled or not, all foreign iptables rules get flushed when connecting or disconnecting to/from Tor.
Iptables chains stay untouched.
This is a big problem when using iptables based firewalls like "DroidWall" or "LBE Privacy Guard".
Example 1:
A internet access blocked application (a game, google location service, etc.) gets unblocked as soon as Orbot connects/disconnects to Tor.
Example 2:
A application should just be able to communicate through Tor. iptables related firewall blocks it. But Orbot's transparency proxy should allow it.
This still occures on the latest RC build:
"Orbot-1.0.6-Tor-0.2.3.7-alpha-RC3"
**Trac**:
**Username**: aribnsNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4444Iptables-binary bundled with Orbot segfaults on Android 2.3.52014-05-12T19:20:23ZTracIptables-binary bundled with Orbot segfaults on Android 2.3.5The iptables-binary that comes with the current release of Orbot (0.2.2.25-alpha-orbot-1.0.5.1, missing in the version-combobox of this bugtracker?) segfaults immediately in my environment:
- Galaxy S2
- XXKI4-based ROM (CheckRom RevoHD...The iptables-binary that comes with the current release of Orbot (0.2.2.25-alpha-orbot-1.0.5.1, missing in the version-combobox of this bugtracker?) segfaults immediately in my environment:
- Galaxy S2
- XXKI4-based ROM (CheckRom RevoHD 2.0)
=> Android 2.3.5
- Siyah-Kernel 2.2b4
As the iptables-binary of e.g. Droidwall works perfectly well, it might be a linking problem.
Replacing Orbots iptables-binary with the one from Droidwall enables all expected functions (transparent proxying etc.).
Stacktrace is attached. I called "iptablesorig --list" (renamed the binary) manually from a terminal to provide this information.
**Trac**:
**Username**: olifeeNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4541Orbot should play nice w/ WhisperCore netfilter API2012-04-06T00:57:20ZTracOrbot should play nice w/ WhisperCore netfilter APINote, we've begun development on this feature in the past, just creating a ticket now so it's trackable.
It would be super to have Orbot's transparent proxying capabilities on non-rooted devices. WhisperSystems has provided an API to do...Note, we've begun development on this feature in the past, just creating a ticket now so it's trackable.
It would be super to have Orbot's transparent proxying capabilities on non-rooted devices. WhisperSystems has provided an API to do just this within their WhisperCore ROM.
SDK available here: http://www.whispersys.com/sdk-docs/reference/packages.html
**Trac**:
**Username**: djhallidayNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4678Orbot fails to start on Asus Transformer with Prime 2.1.1 FW2020-06-13T00:45:41ZTracOrbot fails to start on Asus Transformer with Prime 2.1.1 FWFor some reason Orbot fails to start on Asus Transformer with Prime v2.1.1 firmware.
----
**Trac**:
**Username**: alllexxFor some reason Orbot fails to start on Asus Transformer with Prime v2.1.1 firmware.
----
**Trac**:
**Username**: alllexxNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4874orbot webpage lists wrong git url and says to look in svn2012-01-08T20:48:23ZRoger Dingledineorbot webpage lists wrong git url and says to look in svnThe bottom of https://guardianproject.info/apps/orbot/ tells users to git clone from gitweb. It should say git -- you can't clone from gitweb.
It also tells users to fetch stuff from svn. Is that obsolete yet? If it is, you should repla...The bottom of https://guardianproject.info/apps/orbot/ tells users to git clone from gitweb. It should say git -- you can't clone from gitweb.
It also tells users to fetch stuff from svn. Is that obsolete yet? If it is, you should replace the stuff in svn with a note saying to go look in git, so users don't think orbot is abandoned. If it isn't, you should fix that too. :)Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/4997Orbot doesnt works on 2.3.4 (Galaxy SII)2013-01-11T12:03:05ZTracOrbot doesnt works on 2.3.4 (Galaxy SII)Hello,
Orbot cant access to the Tor network with 2.3.4,but with my other SII with 2.3.3 it works fine?
Can you help me?
Here is the bug/logfile: http://pastebin.com/L3biPZQP
Thanks!
**Trac**:
**Username**: DoesntworkHello,
Orbot cant access to the Tor network with 2.3.4,but with my other SII with 2.3.3 it works fine?
Can you help me?
Here is the bug/logfile: http://pastebin.com/L3biPZQP
Thanks!
**Trac**:
**Username**: DoesntworkNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5096Support transferring bridge addresses in QR codes2020-06-13T03:02:59ZRobert RansomSupport transferring bridge addresses in QR codesAt some point (maybe in days, maybe in weeks), we will start distributing bridge addresses which contain multiple 80-bit-or-longer base32-encoded ‘cryptovariables’ (I don't know any other appropriate general term for them). Orbot users ...At some point (maybe in days, maybe in weeks), we will start distributing bridge addresses which contain multiple 80-bit-or-longer base32-encoded ‘cryptovariables’ (I don't know any other appropriate general term for them). Orbot users will want to not retype them into their puny phone keyboards.
See the ‘`libzbar`’ package for a QR-code decoder under the LGPL. See ‘`libqrencode`’ for a QR-code encoder under the LGPL. Neither of these can currently handle binary strings containing NULs (you don't want to be parsing/repacking bridge lines anyway, but you need to know about that bug before you use the QR-code hammer to pound e.g. OTR/GPG fingerprints, BitTorrent info hashes, or Curve25519/Ed25519 public keys).
Also, if you interact with a QR-code decoder through e.g. XML, don't get [bobbytabled](https://xkcd.com/327/). (P.S. ‘`zbarimg --xml`’ sucks.)Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5132Transifex exports empty android strings2020-06-13T17:32:53ZNathan FreitasTransifex exports empty android stringsWhen you export a the localized strings.xml files from Transifex, untranslated strings are included as empty string resources.
As an example, in the default english strings you might have:
<string name="menu_start">Start Tor</string>
...When you export a the localized strings.xml files from Transifex, untranslated strings are included as empty string resources.
As an example, in the default english strings you might have:
<string name="menu_start">Start Tor</string>
and then in another language, say Spanish, if that string is not translated in the transifex UI, you would have:
<string name="menu_start"></string>
By exporting an empty string resource, Android will use that empty string in the user interface, instead of gracefully degrading to the default english value.
This currently means we can only include translations from Transifex that are 100% complete, which is not what we have done in the past via pootle.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5244Infinite Flickering after Orientation Change in Orbot2020-06-13T02:08:13ZTracInfinite Flickering after Orientation Change in OrbotWhen using Orbot in normal mode and vertical orientation, then changing it to horizontal, Orbot UI starts to flicker indefinitely and is completely unusable.
If you change the orientation back to vertical, it might go back to normal or ...When using Orbot in normal mode and vertical orientation, then changing it to horizontal, Orbot UI starts to flicker indefinitely and is completely unusable.
If you change the orientation back to vertical, it might go back to normal or might still be flickering (though vertically this time)
I am using a test build of Orbot (0.2.3.11-alpha-1.0.7.3-ALPHA-2) which n8fr8 provided for me (it has the Arabic strings I translated added to it). Running on Galaxy Nexus ICS.
**Trac**:
**Username**: VoulnetNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5305Orbot ( 0.2.3.10-alpha-1.0.7-FINAL) connection error2020-06-13T00:59:12ZTracOrbot ( 0.2.3.10-alpha-1.0.7-FINAL) connection errorOrbot was working fine . now it refuses to connect and displays a working status and the following errors .
D/Orbot ( 3435): Attempt: Error connecting to control port: /data/data/org.torproject.android/cache/control_auth_cookie (Per...Orbot was working fine . now it refuses to connect and displays a working status and the following errors .
D/Orbot ( 3435): Attempt: Error connecting to control port: /data/data/org.torproject.android/cache/control_auth_cookie (Permission denied)
D/Orbot ( 3435): java.io.FileNotFoundException: /data/data/org.torproject.android/cache/control_auth_cookie (Permission denied)
I am using a samsung i9100 on a stock rom and Orbot version 0.2.3.10-alpha-1.0.7-FINAL
**Trac**:
**Username**: TBA001Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5385tor doesn't work on rooted android device2013-01-11T12:02:06ZTractor doesn't work on rooted android devicemy android device is htc desire HD ,I rooted it and installed tor orbot
its not working and can not connecting and show the error :
'/data/data/org.torproject.android/privoxy: not found'
all versions show the same error !!
please help :(...my android device is htc desire HD ,I rooted it and installed tor orbot
its not working and can not connecting and show the error :
'/data/data/org.torproject.android/privoxy: not found'
all versions show the same error !!
please help :( !
**Trac**:
**Username**: syriano.cobraNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5393orbot relay bug - orbot is not setting the relay values into torrc properly c...2020-06-13T01:00:46ZTracorbot relay bug - orbot is not setting the relay values into torrc properly causing orbot to not work when set as relayThis is about the bug discussed with 'n8fr8' on #guardianproject at freenode.
So, the relay functionality you said was broken and needs to be fixed for 'orbot' on smartphones.
I checked with the orbot version '0.2.3.10-alpha-orbot-1.0.7-...This is about the bug discussed with 'n8fr8' on #guardianproject at freenode.
So, the relay functionality you said was broken and needs to be fixed for 'orbot' on smartphones.
I checked with the orbot version '0.2.3.10-alpha-orbot-1.0.7-FINAL' and you have checked with the 'dev branch of the code' as you said (i suppose that means you have checked with latest version of code by compiling and running the latest updated version from git; i will do it too and let you know again). But none seemed to work. In fact, you said you were getting a more significant crash, when you enabled relaying on smartphone for dev branch of code.
You also thought if the problem is: whether the Relay conflict is with transproxying/root or with Tor client connection in general. But, i'm not sure if it later seemed not to be the problem.
Then, you told me to change the torrc file on my android phone, as you said that orbot is not setting the relay values properly which might be the reason for orbot not working as a relay on smartphone.
So, I will do that and let you know about it. I will also keep checking 'https://guardianproject.info/builds/Orbot/' to see if any new dev/debug release is posted.
Thankyou so very much for all your help, Mr.Nathan.
**Trac**:
**Username**: ruki_Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5469Orbot: can't specify node restrictions2020-06-13T01:02:26ZTracOrbot: can't specify node restrictionsI'm using Orbot (v0.2.3.10-alpha-1.0.7-FINAL, on Android ICS v4.0.1) and I can't seem to get the exit node I request.
In the Exit and Entrance Node fields I have "{us}" entered, yet sometimes I get IP's outside the US. Yesterday I got a ...I'm using Orbot (v0.2.3.10-alpha-1.0.7-FINAL, on Android ICS v4.0.1) and I can't seem to get the exit node I request.
In the Exit and Entrance Node fields I have "{us}" entered, yet sometimes I get IP's outside the US. Yesterday I got a UK ip.
Also, at random (usually after 30 minutes or so) I seem to lose connection to the Tor network without Orbot notifying me. I'm using Pandora from Canada.
**Trac**:
**Username**: dvdwsnNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5700Make/modify VoIP applications to work better on Tor2020-06-15T23:14:41ZKarsten LoesingMake/modify VoIP applications to work better on TorDepending on how hard it will be to make Tor handle VoIP applications people already want to use (#5699), we should explore how much mileage we can get out of making our own or modifying existing VoIP applications to work better on Tor. ...Depending on how hard it will be to make Tor handle VoIP applications people already want to use (#5699), we should explore how much mileage we can get out of making our own or modifying existing VoIP applications to work better on Tor. One example here is Roger's "push to talk" not-actually-realtime-but-close VoIP wishlist item that Nathan is working on.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5886Orbot needs wifi only option for Relay.2020-06-13T01:11:13ZNathan FreitasOrbot needs wifi only option for Relay.Orbot for Android has a Relay setting. And I would love to use it to help. However, you might want to enable as a default ACTIVE if on WiFi. That way everybody who downloads it can help when on WiFi and not while on a limited mobile p...Orbot for Android has a Relay setting. And I would love to use it to help. However, you might want to enable as a default ACTIVE if on WiFi. That way everybody who downloads it can help when on WiFi and not while on a limited mobile phone plan.
Or for those who have limited data plans, they can set the Relay to be on when WiFi is detected.
And if On when WiFi is detected, the phones can also serve as your Exit points. Furthering the cause.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5887Orbot needs wifi only option for Relay.2012-05-15T06:05:39ZNathan FreitasOrbot needs wifi only option for Relay.Orbot for Android has a Relay setting. And I would love to use it to help. However, you might want to enable as a default ACTIVE if on WiFi. That way everybody who downloads it can help when on WiFi and not while on a limited mobile p...Orbot for Android has a Relay setting. And I would love to use it to help. However, you might want to enable as a default ACTIVE if on WiFi. That way everybody who downloads it can help when on WiFi and not while on a limited mobile phone plan.
Or for those who have limited data plans, they can set the Relay to be on when WiFi is detected.
And if On when WiFi is detected, the phones can also serve as your Exit points. Furthering the cause.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5888Orbot does not start at boot in Android 2.3.42013-10-16T18:58:40ZTracOrbot does not start at boot in Android 2.3.4Orbot does start at boot in Android 2.3.4 Samsung Galaxy Mini even though I selected such an option. The phone is not rooted.
**Trac**:
**Username**: mattiOrbot does start at boot in Android 2.3.4 Samsung Galaxy Mini even though I selected such an option. The phone is not rooted.
**Trac**:
**Username**: mattiNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5890500 Internal Privoxy Error2016-04-07T11:24:20ZTrac500 Internal Privoxy ErrorI sonetimes get 500 Internal Privoxy Error with Could not load file forwarding-failed or something like that.
**Trac**:
**Username**: mattiI sonetimes get 500 Internal Privoxy Error with Could not load file forwarding-failed or something like that.
**Trac**:
**Username**: mattiNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/5955orbot getting stuck till the yellow bar and showing "waiting"2016-04-08T08:17:30ZTracorbot getting stuck till the yellow bar and showing "waiting"I'm really tired of searching forums to get to work orbot but with no success
Plz help
Model number HTC desire hd
Rom : android revolution hd 6.3.2
Android version :2.3.5
Sence version : 3.0
Kernel : 2..6.35.14_rcmixed3d_acs_ace_ncr_v11...I'm really tired of searching forums to get to work orbot but with no success
Plz help
Model number HTC desire hd
Rom : android revolution hd 6.3.2
Android version :2.3.5
Sence version : 3.0
Kernel : 2..6.35.14_rcmixed3d_acs_ace_ncr_v11.1-ge213fe7-dirtyken@klquicksall #12
Baseband : 12.56.69.25u_26.10.04.03_m
Thanks in advAnce
**Trac**:
**Username**: nazzzzzNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/6123Unable to start Tor2016-04-07T11:35:40ZTracUnable to start TorTor is unable to start when I press the start button. The command is not run successfully according to a log.
**Trac**:
**Username**: mattiTor is unable to start when I press the start button. The command is not run successfully according to a log.
**Trac**:
**Username**: mattiNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/6137Icon not in toolbar after killing2020-06-13T01:16:35ZTracIcon not in toolbar after killingOrbot icon is not in toolbar even though connected to the Tor network and Always-On Notifications is selected in the settings. I killed the Orbot application in the Android GUI and started it again by clicking on its icon but did not cli...Orbot icon is not in toolbar even though connected to the Tor network and Always-On Notifications is selected in the settings. I killed the Orbot application in the Android GUI and started it again by clicking on its icon but did not click the start button. The version is 0.2.3.15-ALPHA-1.0.8-RC3.
**Trac**:
**Username**: mattiNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/6300Orbot's wizard does not detects root2016-04-07T11:16:48ZTracOrbot's wizard does not detects rootOrbot's wizard say the device is not rooted, even if it is. It doesn't requests root access.
After enabling it in settings, the app requests root permissions and, if allowed, the transparent proxying works well.
**Trac**:
**Username*...Orbot's wizard say the device is not rooted, even if it is. It doesn't requests root access.
After enabling it in settings, the app requests root permissions and, if allowed, the transparent proxying works well.
**Trac**:
**Username**: Ays388Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/6459error starting transparent proxy2020-06-13T01:23:34ZTracerror starting transparent proxyHi,
I have a Google Nexus S, Android 2.3.7, with Cyanogenmod-7.2.0-crespo
I have installed Orbot 0.2.3.10 from www.torproject.org.
Superuser access is granted to Orbot.
Starting Orbot I get:
- Setting up full transparent proxy
- Warning:...Hi,
I have a Google Nexus S, Android 2.3.7, with Cyanogenmod-7.2.0-crespo
I have installed Orbot 0.2.3.10 from www.torproject.org.
Superuser access is granted to Orbot.
Starting Orbot I get:
- Setting up full transparent proxy
- Warning: error starting transparent proxy
- Proxying!
- Bootstrapped 100% Done
Tor network is running
Check indicates: Sorry. You are not using Tor.
The transparent proxy do not work for me. (Always DISABLED)
What is wrong?
P.S. I was using Orbot on the same device with Cyanogenmod-7.1, and it was working properly with transparent proxying. After installing the Cyanogenmod-7.2.0-crespo rom the problem appeared.
Thanks a lot.
**Trac**:
**Username**: odadgariNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/6988[orbot] Orbot relies on "which" to find the "su" binary.2020-06-13T01:35:15ZTrac[orbot] Orbot relies on "which" to find the "su" binary.On a stock system without busybox, requesting root access fails because "which"(a part of busybox) is not available.
D/Orbot (12049): executing shell cmds: which su; runAsRoot=false;waitFor=true
D/Orbot (12049): Could not acquire ro...On a stock system without busybox, requesting root access fails because "which"(a part of busybox) is not available.
D/Orbot (12049): executing shell cmds: which su; runAsRoot=false;waitFor=true
D/Orbot (12049): Could not acquire root permissions
############
% adb shell
shell@android:/ $ which which
/system/bin/sh: which: not found
127|shell@android:/ $su
shell@android:/ # echo -e '#!/system/bin/sh\necho /system/xbin/su' > /system/xbin/which
shell@android:/ # chmod 755 /system/xbin/which
shell@android:/ # which
/system/xbin/su
############
After that. It works.
**Trac**:
**Username**: MSalNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/7171Improve Orbot's user experience for handling blocked access to the Tor network2016-04-07T11:36:58ZKarsten LoesingImprove Orbot's user experience for handling blocked access to the Tor network(Re-using text from Nathan here.)
Improve user experience for handling blocked access to Tor network or bridges, and prompt to user to try obfsproxy. The interesting thing that you can do on Android is tell whether the user generally h...(Re-using text from Nathan here.)
Improve user experience for handling blocked access to Tor network or bridges, and prompt to user to try obfsproxy. The interesting thing that you can do on Android is tell whether the user generally has an "Internet" connection or not, meaning they have good connectivity, an IP address, etc. The state we're looking for is when the Internet is good, but Tor is stuck at 10% bootstrapping, or some other typical fingerprint of Tor network blockage. Orbot has solid bridge/obfsproxy support, but right now it is not exposed to users who don't know about it.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 Freitashttps://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/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/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/8600Orbot crashes when the app is reopened2013-12-09T22:17:11ZTracOrbot crashes when the app is reopenedI cannot test this myself because I do not have Android, but here is a quote from the help desk, ticket #8615:
> I installed Orbot in my Nexus 7, and while it works, whenever I go back to
> it (that is, I use another application, and th...I cannot test this myself because I do not have Android, but here is a quote from the help desk, ticket #8615:
> I installed Orbot in my Nexus 7, and while it works, whenever I go back to
> it (that is, I use another application, and then return to Orbot) the
> application starts flickering, and I cannot stop or reconfigure it. It
> won't answer to any clicks (touchs?) and the only way out is killing it
> through another app. What's the problem?
Help desk ticket #8617 describes comments on Google Market from users experiencing similar issues.
> > *Ivan Thomson* <!https://plus.google.com/103553384422095535404> - February
> > 3, 2013 - Samsung Galaxy Nexus with version 0.2.3.23-rc-1.0.11-RC6
> > Kind of works, but crashes.
> > Works, but freaks out if I reopen the app. At that point it crashes and Jay
> > flashes between the main screen and a black/blank screen non stop. I'm
> > forced to open apps from settings and force quit the app once it goes
> > spastic. Running 4.2.1 Jb on galaxy nexus.
> and also
> > *anthony carb* <!https://plus.google.com/115129417378559346384> - December
> > 9, 2012 - Version 0.2.3.23-rc-1.0.11-RC6
> > Poor for the HTC droid DNA
> > Looks to be a display problem screen flickers from start of setup so can't
> > configure
> and
> > *A Google User* - October 24, 2012 - Version 0.2.4.4-alpha-1.0.11-RC4
> > Broken since last update
> > UI flashing and flickering all over the place. No longer connecting. Gone
> > from perfectly fine to unusable
**Trac**:
**Username**: mattNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/8796500 Internal Privoxity error2014-09-01T20:07:06ZTrac500 Internal Privoxity errori've recently installed Orbot on my android galaxy S4, and it works on some websites but randomly when i try to access another page or website it comes up with
500 Internal Privoxy Error
privoxy encountered an error while processing you...i've recently installed Orbot on my android galaxy S4, and it works on some websites but randomly when i try to access another page or website it comes up with
500 Internal Privoxy Error
privoxy encountered an error while processing your request:
could not load template file forwarding - failed or one of its included components
**Trac**:
**Username**: ae86Tor: unspecifiedNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/8852Orbot + Firefox 10.0.4 + Proxymob 0.0.82016-07-08T12:52:14ZTracOrbot + Firefox 10.0.4 + Proxymob 0.0.8I installed Orbot and firefox 10.0.4 + proxymob 0.0.8 and I’ve been able to browse the deepweb for a few hours without any pb.
But maybe 2 days ago I suddenly couldn’t access tor anymore. I didn’t make any changes in between.
Orbot start...I installed Orbot and firefox 10.0.4 + proxymob 0.0.8 and I’ve been able to browse the deepweb for a few hours without any pb.
But maybe 2 days ago I suddenly couldn’t access tor anymore. I didn’t make any changes in between.
Orbot starts normally and is connected. If I go to
https://check.torproject.org
with firefox+proxymob I’ve got a nice
“Congratulations. Your browser is configured to use tor”.
But I can’t load any .onion page anymore.
I tried to reinstall everything, I restored the factory settings of my phone, I tried to define proxies manually, I tried under Wifi and 3G, I tried older versions of firefox and even proxymob, etc, etc. But it just don’t work anymore even if I see “congratulations, your Browser is configured to use Tor”
Any idea would be welcome !!
Samsung S GT-i9000
(I don’t want to root my device as I saw firefox running deepweb perfectly)
Android GingerBread 2.3.6 unrooted
firefox 10.0.4
proxymob 0.0.8
SOCKS Proxy Host 127.0.0.1
SOCKS Proxy Port 9050
SOCKS Remote DNS True
**Trac**:
**Username**: hokanekoNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/8882Include Arabic translation for Orbot strings.xml2014-04-16T06:06:25ZSheriefInclude Arabic translation for Orbot strings.xmlArabic Translation for Orbot strings.xml was revised (twice) and completed, Please include it.Arabic Translation for Orbot strings.xml was revised (twice) and completed, Please include it.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9720Orbot Android Force Close loop on weird bridge lines2016-04-07T11:38:41ZTracOrbot Android Force Close loop on weird bridge linesBasically it seems that one or both of the following are true:
Orbot Force Closes every time you try to interact with the Orbot app if:
1. You have something weird in your bridge line like a missing comma, or commas, or a FQDN instead...Basically it seems that one or both of the following are true:
Orbot Force Closes every time you try to interact with the Orbot app if:
1. You have something weird in your bridge line like a missing comma, or commas, or a FQDN instead of an IP, or or or or or or or. Please robustify.
2. You have a bridge string that is too long for Orbot's tastes, I think it may also set off a similar Force Close loop, but I haven't rigorously tested this.
**Trac**:
**Username**: gmorehouseNathan FreitasNathan Freitashttps://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/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 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/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/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/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/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/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/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/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/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/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/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/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/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 Freitas