Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2010-08-04T03:00:02Zhttps://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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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 Freitas