Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T00:59:12Zhttps://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/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/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/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/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/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/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/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/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/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/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 Freitas