search

CellularPrivacy / Android-IMSI-Catcher-Detector

AIMSICD • Fight IMSI-Catcher, StingRay and silent SMS!
https://cellularprivacy.github.io/Android-IMSI-Catcher-Detector/
GNU General Public License v3.0
4.71k stars 943 forks source link

Support Orbot(SOCKS5 proxy) to connect to the internet. #907

Open ghost opened 7 years ago

ghost commented 7 years ago

I tried your app from F-Droid, and I found that I can't download/upload anything because I use(and must) Orbot, the Tor proxy. Please consider adding an option to define SOCKS5 and/or HTTP proxy to connect.

darkerego commented 7 years ago

I second this, it'd be a great feature. We have to assume that we're all being monitored for not only collaborating on this project, but using this app in general...

TurtleEggs commented 7 years ago

@ghost @darkerego I have researched thus far on how can we port an android application to communicate through TOR server.....without rooting your phone the other available option is to use the guradian project Tor based library. I am currently researching if there is a server that is up and running or proxies that directly communicate to Tor

TurtleEggs commented 7 years ago

https://blog.torproject.org/category/tags/android <--- a link i found referencing how orWall can be used to bypassing an extra java file that incorporates socks5/proxies, as quoted "OrWall provides the networking component of this access control. It allows the user to choose which apps route through Tor, which route through non-Tor, and which can't access the Internet at all. It also has an option to let a specific Voice over IP app, like Signal, bypass Tor for the UDP voice data channel, while still sending call setup information over Tor.".....this is just an option to consider unless there is preference for uniqueness or customization, any thoughts gentlement ? @darkerego

darkerego commented 7 years ago

@TurtleEggs ,

Well yes, we could always force traffic through tor, using either the built-in VPN feature that Orbot already has, or by using something like OrWall, as you mentioned. However, ideally we want the app to natively support socks5 proxies, so that the end user could (from within the app) simply tick a box to choose to enable an option, like "Send All App Traffic Through a Proxy"; and than ask the user to provide a socks proxy address, defaulting to socks5:127.0.0.1:9050 (or something like that).

I would much prefer this instead of having to rely on ip/routing tables, or another app to torify the traffic.