Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2011-10-31T03:39:00Zhttps://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/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/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/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/3387Status bar Notification constructor is depreciated2016-01-22T04:25:27ZSathyanarayanan GunasekaranStatus bar Notification constructor is depreciatedpublic Notification (int icon, CharSequence tickerText, long when) is [depreciated](http://developer.android.com/reference/android/app/Notification.html#Notification()). Use [Notification.Builder](http://developer.android.com/reference/a...public Notification (int icon, CharSequence tickerText, long when) is [depreciated](http://developer.android.com/reference/android/app/Notification.html#Notification()). Use [Notification.Builder](http://developer.android.com/reference/android/app/Notification.Builder.html) in the TorService.java activity to create Status bar Notifications instead.Sathyanarayanan GunasekaranSathyanarayanan Gunasekaranhttps://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/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/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/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/3225New Orbot Wizard Flows2011-10-31T03:41:07ZTracNew Orbot Wizard Flows**Moving this enhancement over from github**
latest mockups from gsathya: http://i.imgur.com/1vcXW.png
There are 2 things to take away from this release(?) -
* The TransProxy screen - we still need to work on the image/graphic
* Permis...**Moving this enhancement over from github**
latest mockups from gsathya: http://i.imgur.com/1vcXW.png
There are 2 things to take away from this release(?) -
* The TransProxy screen - we still need to work on the image/graphic
* Permissions screen for non-root users - does the "NOTE" work ? or do we need a checkbox ?
**Trac**:
**Username**: djhallidaySathyanarayanan GunasekaranSathyanarayanan Gunasekaranhttps://gitlab.torproject.org/legacy/trac/-/issues/3211Orbot won't start on Nexus 2.3.42013-01-11T12:07:17ZNathan FreitasOrbot won't start on Nexus 2.3.4nexus one
anroid 2.3.4
build grj22nexus one
anroid 2.3.4
build grj22Jacob AppelbaumJacob Appelbaumhttps://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/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/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/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/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/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/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/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/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 Freitas