Opened 8 months ago

#30003 new defect

orbot .torrc fails

Reported by: untiedlaces Owned by:
Priority: Medium Milestone:
Component: Applications Version: Tor: 0.3.4.9
Severity: Normal Keywords: torrc
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Orbot version 16.0.5-RC-2-tor-0.3.4.9

Following .Torrc settings create errors within Orbot:

IsolateClientAddr
IsolateSOCKSAuth
IsolateClientProtocol
IsolateDestPort
IsolateDestAddr
KeepAliveIsolateSOCKSAuth
IPv6Traffic
PreferIPv6
NoDNSRequest

Error messages returned:

[warn] Failed to parse/validate config: Unknown option 'IsolateClientAddr'. Failing.

[warn] Failed to parse/validate config: Unknown option 'IsolateSOCKSAuth'. Failing.

[warn] Failed to parse/validate config: Unknown option 'IsolateClientProtocol'. Failing.

[warn] Failed to parse/validate config: Unknown option 'IsolateDestPort'. Failing.

[warn] Failed to parse/validate config: Unknown option 'KeepAliveIsolateSOCKSAuth'. Failing.

[warn] Failed to parse/validate config: Unknown option 'IPv6Traffic'. Failing.

[warn] Failed to parse/validate config: Unknown option 'NoDNSRequest'. Failing.

Apr 03 08:18:41.431 [err] Reading config failed--see warnings above.

WARN: Your application (using socks5 to port 443) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via privoxy or socat) instead. For more information, please see https://wiki.torproject.org/TheOnionRouter/TorFAQ#SOCKSAndDNS. Rejecting.

Without settings, Orbot functions desirably.

Child Tickets

Change History (0)

Note: See TracTickets for help on using tickets.