Bug #2982
settings option to force all traffic through Orbot, to the point that when Orbot fails or exits, apps cannot connect: FAIL CLOSED
| Status: | New | Start date: | 02/20/2014 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | Spent time: | - | |
| Target version: | v14 - April Anons | |||
| Component: |
Description
As per https://dev.guardianproject.info/issues/2947:
"Orbot will only route apps through it if it is running. If it is not running, traffic will flow as normal."
This seems pretty much like what you would call "failing open". It seems understandable to do that in the interest of noob-user-friendliness; in other words to fail open so that there isn't intense aggravation and/or panic on the part of the user when the user's phone won't connect to anything and they aren't aware enough to check Orbot to see if it is running and remember that they probably set it to "Tor Everything".
However, obviously there are users who, for reasons of tighter/better security, do.not.want. to connect to anything if Tor is unavailable, and certainly not unexpectedly - there aren't always noticeable notifications when Orbot disconnects,crashes, or closes.
On other platforms, when someone sets up a proxy, and it goes down, and they automagically connect anyway without it, they'd probably freak out. So it's kind of weird to have that happen here.
Having a setting available somewhere in the preferences that is disabled by default would tie up all of these threads nicely.
No connectivity without Tor!!