Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2016-04-07T10:57:53Zhttps://gitlab.torproject.org/legacy/trac/-/issues/9989Orbot stucks on 25%2016-04-07T10:57:53ZTracOrbot stucks on 25%Im trying to start orbot on my samsung galaxy note 2 but it stucks on 25%
im using android 4.1.1, here are logs
Orbot is starting…
Orbot is starting…
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Set...Im trying to start orbot on my samsung galaxy note 2 but it stucks on 25%
im using android 4.1.1, here are logs
Orbot is starting…
Orbot is starting…
(re)Setting permission on Tor binary
(re)Setting permission on Privoxy binary
(re)Setting permission on Obfsproxy binary
Orbot is starting…
got tor proc id: 3317
Tor process id=3317
Connecting to control port: 9051
SUCCESS connected to control port
SUCCESS authenticated to control port
Starting Tor client… complete.
adding control port event handler
SUCCESS added control port event handler
NOTICE: Bootstrapped 10%: Finishing handshake with directory server.
NOTICE: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
NOTICE: To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features.
Starting privoxy process
/data/data/org.torproject.android/app_bin/privoxy /data/data/org.torproject.android/app_bin/privoxy.config &
Privoxy is running on port:8118
Privoxy process id=3370
NOTICE: Bootstrapped 15%: Establishing an encrypted directory connection.
orConnStatus (wau): CONNECTED
NOTICE: Bootstrapped 20%: Asking for networkstatus consensus.
Circuit (1) BUILT: wau
NOTICE: Bootstrapped 25%: Loading networkstatus consensus.
**Trac**:
**Username**: BennyNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9961Orbot contact information cannot be configured2020-06-13T02:36:07ZTracOrbot contact information cannot be configuredOrbot contact information cannot be configured in the settings menu and that leads to an INFO complaint about not set contact information in the log if Orbot is set up as a relay.
**Trac**:
**Username**: mattiOrbot contact information cannot be configured in the settings menu and that leads to an INFO complaint about not set contact information in the log if Orbot is set up as a relay.
**Trac**:
**Username**: mattiNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9861Orbot: enter multiple bridges, but it only uses one2020-06-13T02:34:00ZTracOrbot: enter multiple bridges, but it only uses oneThis is Orbot 12.0.5 on Android 2.3.x.
* use bridges is checked
* obfuscated bridges is checked
* bridge addresses are 1 per line, IP:port
* I know >1 of these work as I operate some of them for testing
I see a LAUNCHED for every bridg...This is Orbot 12.0.5 on Android 2.3.x.
* use bridges is checked
* obfuscated bridges is checked
* bridge addresses are 1 per line, IP:port
* I know >1 of these work as I operate some of them for testing
I see a LAUNCHED for every bridge when I start up Orbot connecting, but, circuits are only ever built through the second bridge on the list, for whatever reason. I never see log messages about the others other than LAUNCHED at startup.
Please let me know if there is a better place to submit this bug - I can't find it with The Guardian Project.
**Trac**:
**Username**: gmorehouseNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/9805Orbot needs updating on F-Droid/Guardian Project Repo2016-04-07T11:33:47ZcypherpunksOrbot needs updating on F-Droid/Guardian Project RepoThe lastest version shown at https://guardianproject.info/repo/ is 12.0.3, while the Play Store and https://guardianproject.info/releases/ have 12.0.5.
The default FDroid repo lists an even older version.
Please update... Thanks.The lastest version shown at https://guardianproject.info/repo/ is 12.0.3, while the Play Store and https://guardianproject.info/releases/ have 12.0.5.
The default FDroid repo lists an even older version.
Please update... Thanks.Nathan FreitasNathan 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/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/8933Do a security audit of Onion Browser2015-08-27T20:21:59ZMatt PaganDo a security audit of Onion BrowserThere exists a web browser for iOS that uses Tor[0]. It costs 0.99 USD from Apple's app store, but it is open source. The code is hosted on Github[1]. This project is actively maintained, with the last update being made on May 18, 2013 (...There exists a web browser for iOS that uses Tor[0]. It costs 0.99 USD from Apple's app store, but it is open source. The code is hosted on Github[1]. This project is actively maintained, with the last update being made on May 18, 2013 (The main page mistakenly says May 18, 2012, but the description says it has an update to tor version 0.2.12.4-alpha).
The project already maintains its own list of known issues[2]. Some of them (like # 26) already make me squirm. However, if Tor is ever going to make its way to iOS, working with someone who has already put considerable work into such a project might be easier than starting from scratch. The developer seems open to working with Tor people because (1)he's open-sourced the project and (2)he claims that he is donating a percentage of the proceeds to the Tor Project.
From responding to help desk tickets, I can say that there is considerable user demand for Tor on iOS. I think it would be great to make a list of things such that we could say "If Onion Browser stopped doing X and did Y all the time, the Tor Project could recommend it to users."
If there are other concerns here I am missing, please bring them up/modify this ticket/whatever.
[0]: https://mike.tig.as/onionbrowser/
[1]: https://github.com/mtigas/iOS-OnionBrowser
[2]: https://github.com/mtigas/iOS-OnionBrowser/issueshttps://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/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/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/8500Warn the user about possible transparent proxying failure2020-06-13T02:06:22ZTracWarn the user about possible transparent proxying failureThe transparent proxying feature is very likely to fail for a number of reasons, the most common is lack of a firmware supporting the needed iptables magic, or bugs like #3595.
Currently orbot doesn't warn the user when this occurs, lea...The transparent proxying feature is very likely to fail for a number of reasons, the most common is lack of a firmware supporting the needed iptables magic, or bugs like #3595.
Currently orbot doesn't warn the user when this occurs, leading to a false sense of security.
* It only mentions "(Requires root)" in the settings menu: true, but not enough: a special firmware is required too. It should be mentioned (possibly with a link to https://www.torproject.org/docs/android.html.en )
* At orbot startup, a system notification message is issued, saying that transparent proxying has been correctly enabled, even when this is not the case!
Orbot should check more toroughly if transparent proxying is really working, and issue a BIG WARNING in the user interface if this is not the case (or if this can not be detected).
Also the web page at https://www.torproject.org/docs/android.html.en could be improved, though it mentions the requirement for a suitable firmware, the warning could be made more evident (now you have to read the fine print to find out about this limitation).
We could also suggest the user to always check if a particular app is behaving as expected, for example checking the current network connections using a netstat-like tool like Os monitor
(see: http://f-droid.org/repository/browse/?fdfilter=os%20monitor&fdid=com.eolwral.osmonitor )
**Trac**:
**Username**: criNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/8344Orbot BUILD instructions incomplete2020-06-13T02:02:08ZTracOrbot BUILD instructions incompleteThe instructions for building Orbot are incomplete
https://gitweb.torproject.org/orbot.git/blob/9daaec2f84e59ad49cbff29c11eadbe52cc8f4d4:/BUILD
my NDK_BASE
`$NDK_BASEbash: /home/malaparte/src/android/android-ndk-r8c: Is a directory`
...The instructions for building Orbot are incomplete
https://gitweb.torproject.org/orbot.git/blob/9daaec2f84e59ad49cbff29c11eadbe52cc8f4d4:/BUILD
my NDK_BASE
`$NDK_BASEbash: /home/malaparte/src/android/android-ndk-r8c: Is a directory`
and
`make -C ./externalmake: Entering directory `/home/malaparte/src/tor/orbot/external'cd openssl-static && \ ndk-build/bin/sh: 2: ndk-build: not foundmake: *** [openssl-static/obj/local/armeabi/libcrypto.a] Error 127make: Leaving directory `/home/malaparte/src/tor/orbot/externa`
**Trac**:
**Username**: malaparte_https://gitlab.torproject.org/legacy/trac/-/issues/8079WARNING: error starting transparent proxying!2020-06-13T01:55:43ZTracWARNING: error starting transparent proxying!Hi,
I'm getting "WARNING: error starting transparent proxying!". Looks similar to https://trac.torproject.org/projects/tor/ticket/3891 but thing is:
- it was working just after Orbot installation (no warn message + I verified this for ...Hi,
I'm getting "WARNING: error starting transparent proxying!". Looks similar to https://trac.torproject.org/projects/tor/ticket/3891 but thing is:
- it was working just after Orbot installation (no warn message + I verified this for some apps and tethering on https://check.torproject.org/).
- I have CyanogenMod-7.2.0-vision installed (root access is granted for Orbot).
I was trying to use Orbot-bundled iptables but with no change.
I'll try to attach debug log ASAP. If you'll need additional information please let me know.
regards
milo
**Trac**:
**Username**: miloNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/7254Orbot WARNs DNSPort and TransPort public address specified2020-06-13T01:40:54ZcypherpunksOrbot WARNs DNSPort and TransPort public address specified"WARN You specified and public address for DNSPort (and TransPort). Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason."
I don't have a good reason an..."WARN You specified and public address for DNSPort (and TransPort). Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason."
I don't have a good reason and want to fix this. There are 4 WARN messages, 1 DNSPort, another TransPort, another DNSPort and another Transport. They repeat as the Orbot log updates itself.
Orbot version 0.2.3.23-rc-1.0.11-RC6 on Samsung EXhibit II running CyanogenMod version 9-20120826_UNOFFICIAL-aancora-tmo
Hopefully I'm posting correctly in the correct place.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/7210Orbot hides the errors of the iptables rules2020-06-13T01:40:12ZTracOrbot hides the errors of the iptables rulesThe transparent proxy of orbot doesn't run in my phone. It shows a error in the notification area.
Yesterday, I decided review the debug log with adb and I found a (in my opinion) important problem in orbot.
You're running the rules of...The transparent proxy of orbot doesn't run in my phone. It shows a error in the notification area.
Yesterday, I decided review the debug log with adb and I found a (in my opinion) important problem in orbot.
You're running the rules of iptables with "/whatever/iptables rules | | exit". I know that my problem is due to some iptables rules but I can't see the error because you hide the error using "| | exit".
You can run each rule individually and check the exit code each time. I think my suggestion is better than the use of "| | exit" because with this orbot doesn't hide the errors.
Sorry if I don't send a patch but my know about java code is near to 0 :)
**Trac**:
**Username**: juanfra684Nathan FreitasNathan 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/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/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/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/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 Freitas