summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* | update makefile to support PLUTO buildsNathan Freitas2015-12-16
| |
* | add link for new iconNathan Freitas2015-12-16
| |
* | update for OrfoxNathan Freitas2015-12-16
| |
* | update binariesNathan Freitas2015-12-16
| |
* | update external versions of Tor 0.2.7.6 and OpenSSL 1.0.1qNathan Freitas2015-12-16
| |
* | use a browser constant here, with the new constant being OrfoxNathan Freitas2015-12-16
| |
* | deleted these graphicsNathan Freitas2015-12-16
| |
* | update style, icons and graphicsNathan Freitas2015-12-16
|/
* update to 15.0.1-RC-3 with openssl 1.0.2a15.0.1-RC-3Nathan Freitas2015-07-14
| | | | also this build adds x86 back in
* move back to 1.0.2a for x86_64 supportNathan Freitas2015-07-14
|
* fix translations for common issuesNathan Freitas2015-07-13
|
* update localizations for strings and app descriptionNathan Freitas2015-07-13
|
* update changelog15.0.1-RC-2Nathan Freitas2015-07-13
|
* 15.0.1-RC-2-PIENathan Freitas2015-07-13
|
* update tor version constant to 0.2.6.10Nathan Freitas2015-07-13
|
* update to tor 0.2.6.10Nathan Freitas2015-07-13
|
* Merge pull request #15 from aelmahmoudy/openssl_updaten8fr82015-07-09
|\ | | | | Update OpenSSL to v1.0.2a to fix build for x86_64 arch.
| * Update OpenSSL to v1.0.2a to fix build for x86_64 arch.أحمد المحمودي (Ahmed El-Mahmoudy)2015-07-09
| |
* | Merge pull request #14 from aelmahmoudy/mipsfixn8fr82015-07-09
|\ \ | |/ |/| Define __MIPSEL__ to workaround OpenSSL build failure for mips arch.
| * Define __MIPSEL__ to workaround OpenSSL build failure for mips arch.أحمد المحمودي (Ahmed El-Mahmoudy)2015-07-09
|/
* update to 15.0.1-RC-1 (PIE only)15.0.1-RC-1Nathan Freitas2015-07-08
|
* update changelog15.0.1-beta-3Nathan Freitas2015-06-26
|
* update to beta 3Nathan Freitas2015-06-26
|
* final fixes for AppsVPN mode on boot and Android 4.x supportNathan Freitas2015-06-26
|
* update changelog for v15.0.115.0.1-beta-2-signed15.0.1-beta-2Nathan Freitas2015-06-25
|
* v15.0.1 beta 2Nathan Freitas2015-06-25
|
* Enable support for app selection to work with VPN mode on Lollipop+Nathan Freitas2015-06-25
| | | | For now we will re-use/overload the app selection transproxy UI in Settings
* update to sdk 22Nathan Freitas2015-06-25
|
* don't try to build external folders in eclipseNathan Freitas2015-06-25
|
* update tun2socks binariesNathan Freitas2015-06-25
|
* update submodule pinNathan Freitas2015-06-25
|
* enable background starts by default only for Service intent callsNathan Freitas2015-06-22
|
* update manifest for v15.0.1 beta 1Nathan Freitas2015-06-22
|
* Merge branch 'the-big-start-stop-makeover' of ↵Nathan Freitas2015-06-22
|\ | | | | | | | | | | | | | | https://github.com/eighthave/orbot into eighthave-the-big-start-stop-makeover Conflicts: src/org/torproject/android/OrbotMainActivity.java src/org/torproject/android/service/TorService.java
| * on start, check for running tor daemon, and if TorService stopped, then startHans-Christoph Steiner2015-06-17
| | | | | | | | | | | | | | If Orbot was killed when the tor daemon was running, the tor daemon will still be running when Orbot starts again. OrbotMainActivity then checks to see if tor daemon is running while TorService is stopped. If so, TorService is started so that the state of everything is in sync.
| * init file path variables (tor, polipo, etc) when the app startsHans-Christoph Steiner2015-06-17
| | | | | | | | | | | | | | | | These file path variables can be set at the very start, OrbotApp.onCreate() and they will not change during the lifetime of the app, so represent them as globally accessible static variables. This is needed for things like OrbotMainActivity detecting whether the tor daemon is still running, even though TorService is not.
| * "Allow Background Starts" prefs also controls the old START_TOR IntentHans-Christoph Steiner2015-06-17
| |
| * remove delayed handling of Intents in OrbotMainActivityHans-Christoph Steiner2015-06-17
| | | | | | | | | | | | This is a leftover bit from the old structure, it should no longer be needed and it causes the status updates to be noticeably delayed so when OrbotMainActivity is started after being killed, it flashes OFF then ON.
| * prevent a status request from starting TorServiceHans-Christoph Steiner2015-06-17
| | | | | | | | | | | | | | | | If some internal bit of Orbot is requesting the status of TorService, it should not cause it to start. So only request status from TorService if it is running, otherwise keep status as OFF. the big imports change is because of the Android auto-formatter
| * when OrbotMainActivity starts, query TorService for current statusHans-Christoph Steiner2015-06-17
| | | | | | | | | | | | If OrbotMainActivity gets killed while TorService is running, then when OrbotMainActivity starts again, it needs to get the current status from TorService to correctly represent things to the user.
* | Merge branch 'eighthave-the-big-start-stop-makeover'Nathan Freitas2015-06-22
|\ \
| * | fix handling of foreground intent starts, and set bg start off by defaultNathan Freitas2015-06-22
| | |
| * | improve status request/callback interaction and status UI layoutNathan Freitas2015-06-22
| | |
| * | update tor to 0.2.6.9Nathan Freitas2015-06-22
| |/
| * include all status messages with "start" in them in the starting sequenceHans-Christoph Steiner2015-06-12
| | | | | | | | | | | | Before, the startup sequence showed "Orbot is starting..." for a long time, then quickly showed the final tor percentage messages. This adds a few more messages to provide useful feedback.
| * drive main screen UI updated entirely from TorService status updatesHans-Christoph Steiner2015-06-12
| | | | | | | | | | | | Now that STATUS_STARTING is sent in TorService.onCreate(), the response time is snappy enough that we don't need hacks in OrbotMainActivity to show that long press happened.
| * set STATUS_STARTING in TorService.onCreate(), that's where it beginsHans-Christoph Steiner2015-06-12
| | | | | | | | | | | | | | | | The very first place that the whole tor start sequence starts is from TorService's onCreate(), so that is where STATUS_STARTING should be announced from. The open question is whether Intents besides ACTION_START ever cause TorService to start. In theory, TorService should already be running when any Intent is sent besides ACTION_START.
| * rename TorStarter to IncomingIntentRouter, it handles all IntentsHans-Christoph Steiner2015-06-12
| | | | | | | | TorStarter does lots of things besides starting Tor
| * announce Orbot is ON once the first circuit is completeHans-Christoph Steiner2015-06-12
| | | | | | | | | | | | | | Before, it was announcing tor was started when it had completed starting the daemons. But that does not guarantee that Tor is actually connected and working. So instead, this waits for the first circuit to be built, then announces Tor is ON.
| * include dynamic proxy config info in ACTION_STATUS repliesHans-Christoph Steiner2015-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This includes extras in the Intents that are sent as replies to the two different requests to start tor (ACTION_START and ACTION_START_TOR). These extras give all of the current SOCKS and HTTP proxy settings, so that the app can dynamically use the correct settings. Sometimes there are port conflicts, so apps should dynamically adjust in order to reliably find tor. closes #3612 https://dev.guardianproject.info/issues/3612 refs #4419 https://dev.guardianproject.info/issues/4419 refs #3690 https://dev.guardianproject.info/issues/3690 refs #3687 https://dev.guardianproject.info/issues/3687 refs #3859 https://dev.guardianproject.info/issues/3859
generated by cgit v1.2.1 (git 2.18.0) at 2024-02-08 07:31:45 +0000