guardianproject / guardianproject/orbot-android
[Feature Request] Change routing from opt in to op out
- Dominant language
- Kotlin
- Stars
- 3.5k
- Forks
- 485
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 24
Description
Making it so easy to accidentally deanonymize yourself, which can be life or death, I believe is unacceptable. If one wants to use the tor browser and Orbot at the same time they have to toggle off Block connections without VPN making themselves more vulnerable to ip leakage. (If someone has a solution to keep this toggled on while keeping access to browsing on tor browser or an equivalent and still routing all traffic through tor I would greatly appreciate that information)
To decrease the possibility of deanonymizingg people I think Orbot some change its policy from an opt in system to opt out. It's hard me to imagine accident tor access can be as consequential as accidental clearnet access.
Contributor guide
No contributing guide indexed for this repository
Research direction
This issue concerns Orbot's Android routing policy and asks to change it from opt-in to opt-out to reduce accidental clearnet access. No files, tests, or entry points are named; first clarify the intended VPN and Tor Browser behavior, then identify the routing-policy entry point and define done as preventing unintended clearnet access without blocking intended Tor browsing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100