[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #12411 [Orbot]: Orbot broke using DNSPort
#12411: Orbot broke using DNSPort
-------------------------+-------------------------------------------------
Reporter: isis | Owner: n8fr8
Type: defect | Status: closed
Priority: normal | Milestone:
Component: Orbot | Version:
Resolution: fixed | Keywords: orbot-14.0.3.1, orbot-14.0.4, wtf,
Actual Points: | software-engineering
Points: | Parent ID:
-------------------------+-------------------------------------------------
Changes (by n8fr8):
* status: new => closed
* resolution: => fixed
Comment:
Nothing is leaking. DNS might not be resolving for apps expecting it on
localhost:5400 but why would that cause a leak?
Most users rely on Orbot's built in transproxy support. This is enabled by
granting Orbot root and enabling the transproxy option. If you do this, it
will turn on transport and dnsport. You do not need to turn on the
everything or app-by-app options.
It is two taps to enable this. Any user who has followed Mike's
instructions is likely capable of tapping twice.
Orbot now supports custom torrc entries via Orbot Settings menu near the
bottom. You can set whatever entries you would like there.
The reason we disabled the ports by default is related to issues with
Samsung devices and port conflicts. We will reconsider having these ports
back on by default with an easy option to turn them off for users who
don't need them.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12411#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs