Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2010-08-04T03:00:39Zhttps://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/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/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/1513Orbot can't be told to exit2010-07-19T15:37:05ZSteven MurdochOrbot can't be told to exitOrbot can be told to stop Tor, but it still sits in the notification area. It would be polite to offer users a button to quit Orbot, and stop it being visible (other similar applications like ConsoleBot and AndChat do this).
Force quit ...Orbot can be told to stop Tor, but it still sits in the notification area. It would be polite to offer users a button to quit Orbot, and stop it being visible (other similar applications like ConsoleBot and AndChat do this).
Force quit works, but it is a pain to find without having to install an additional application like MemoryCleaner.https://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/1509help window is too big for the screen on android 1.62010-07-19T15:39:12ZAndrew Lewmanhelp window is too big for the screen on android 1.6In orbot 0.0.6 with tor 0.2.2.13-alpha, when hitting menu, then help, the bottom two buttons are off the screen on android 1.6.In orbot 0.0.6 with tor 0.2.2.13-alpha, when hitting menu, then help, the bottom two buttons are off the screen on android 1.6.https://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/1350Enomther`s [ROM] TheOfficial Nexus1 doesn't work2011-05-10T02:07:12ZTracEnomther`s [ROM] TheOfficial Nexus1 doesn't workThe android based install doesn't work with Enomther`s [ROM] TheOfficial Nexus1, it just keeps failing over and over again, I let it go for hours thinking it was just slow. It works fine with cyanogenmod..
I can provide whatever additio...The android based install doesn't work with Enomther`s [ROM] TheOfficial Nexus1, it just keeps failing over and over again, I let it go for hours thinking it was just slow. It works fine with cyanogenmod..
I can provide whatever additional information you require.
[Automatically added by flyspray2trac: Operating System: Other]
**Trac**:
**Username**: oneadventhttps://gitlab.torproject.org/legacy/trac/-/issues/1336url in About is wrong2010-05-26T15:32:49ZAndrew Lewmanurl in About is wrongThe url in the about orbot points to https://torproject.org/android, which is a 404.
You probably want https://www.torproject.org/docs/android
[Automatically added by flyspray2trac: Operating System: All]The url in the about orbot points to https://torproject.org/android, which is a 404.
You probably want https://www.torproject.org/docs/android
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/legacy/trac/-/issues/1333"Apps" menu should hide for non-root users2010-07-19T20:23:22ZNathan Freitas"Apps" menu should hide for non-root usersMany users are are confused by the "Apps" menu option. This should be either be more clearly documented or it
should be hidden for non-root users.
[Automatically added by flyspray2trac: Operating System: All]Many users are are confused by the "Apps" menu option. This should be either be more clearly documented or it
should be hidden for non-root users.
[Automatically added by flyspray2trac: Operating System: All]https://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/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/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/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/1285Special Characters on Relay nickname2010-03-07T03:46:34ZTracSpecial Characters on Relay nicknameOrbot currently allows any type of characters on the relay nickname. This should not be allowed.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: goukiOrbot currently allows any type of characters on the relay nickname. This should not be allowed.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: goukihttps://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/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/1279Misleading message when initialization is finished2010-03-05T23:28:58ZChristian FrommeMisleading message when initialization is finishedAfter the initialization phase in Orbot is finished, it says something along the lines of "You're now browsing anonymously". Which isn't true as long as you haven't configured proxysurf along with Orbot. Maybe this should be changed so t...After the initialization phase in Orbot is finished, it says something along the lines of "You're now browsing anonymously". Which isn't true as long as you haven't configured proxysurf along with Orbot. Maybe this should be changed so that new users aren't confused whether or not they're surfing anonymously.
[Automatically added by flyspray2trac: Operating System: All]Jacob AppelbaumJacob Appelbaumhttps://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/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 Freitas