Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T03:16:33Zhttps://gitlab.torproject.org/legacy/trac/-/issues/12413Orbot doesn't use separate torrcs, and overrides & overwrites user-set torrcs2020-06-13T03:16:33ZIsis LovecruftOrbot doesn't use separate torrcs, and overrides & overwrites user-set torrcsYou _can_ use multiple `torrc` files simultaneously. [RTFM](https://gitweb.torproject.org/tor.git/blob/HEAD:/doc/tor.1.txt#l52)You _can_ use multiple `torrc` files simultaneously. [RTFM](https://gitweb.torproject.org/tor.git/blob/HEAD:/doc/tor.1.txt#l52)Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/12412Orbot broke using TransPort2020-06-13T03:16:32ZIsis LovecruftOrbot broke using TransPortOrbot (as of 14.0.3.1 and later) [sets `TransPort 0`](https://gitweb.torproject.org/orbot.git/commitdiff/2ce9ea92f14f7b5c04798809f0c262475766977e), which disables tor's `TransPort` entirely. This means that people who use iptables script...Orbot (as of 14.0.3.1 and later) [sets `TransPort 0`](https://gitweb.torproject.org/orbot.git/commitdiff/2ce9ea92f14f7b5c04798809f0c262475766977e), which disables tor's `TransPort` entirely. This means that people who use iptables scripts outside of Orbot (as described in [Mike Perry's recent blog post](https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy)) to redirect TCP traffic to the `TransPort` cannot do so.
Related, see #12411.
>
> Leaks are not the problem; they are the symptom. --Heather Brooke
>Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/12411Orbot broke using DNSPort2020-06-13T03:16:31ZIsis LovecruftOrbot broke using DNSPortOrbot 14.0.3.1 completely breaks networking, if you have firewall scripts which don't allow leaks.
**THIS MEANS THAT ORBOT IS LEAKING LIKE THE FUCKING PENTAGON PAPERS, EXCEPT NOT IN A GOOD WAY.**
This is because Orbot (as of 14.0.3.1 ...Orbot 14.0.3.1 completely breaks networking, if you have firewall scripts which don't allow leaks.
**THIS MEANS THAT ORBOT IS LEAKING LIKE THE FUCKING PENTAGON PAPERS, EXCEPT NOT IN A GOOD WAY.**
This is because Orbot (as of 14.0.3.1 and later) [sets `DNSPort 0`](https://gitweb.torproject.org/orbot.git/commitdiff/2ce9ea92f14f7b5c04798809f0c262475766977e), which disables tor's `DNSPort` entirely. This means that people who use iptables scripts outside of Orbot (as described in [Mike Perry's recent blog post](https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy)) to redirect UDP DNS traffic to the `DNSPort` cannot do so. It also means that _every other application will leak traffic all over the place_.
Currently, the only way to fix this mess is to force stop and uninstall Orbot, download an older (14.0.1) .apk onto another device, and copy it over manually to the broken one to reinstall it. This is ridiculous. You're practically bricking people's devices, and you're forcing them to jump through extreme hoops to preserve their anonymity.Nathan FreitasNathan Freitas