Skip to content

Embedded Tor client initializes even when Orbot is running #1691

Description

@basantagoswami

From the output in my terminal:

I/flutter (27817): CONFIG	Starting Tor...
I/flutter (27817): INFO	Waiting for Tor to be ready...
x21
I/flutter (27817): CONFIG	Tor enabled
I/flutter (27817): INFO	Waiting for Tor to be ready...
x10
I/flutter (27817): CONFIG	Tor started
I/flutter (27817): CONFIG	Tor ready
I/flutter (27817): FINE	Tor started in 103s on port 38899
I/flutter (27817): FINE	Recoverbull server ready after 1 attempts
I/flutter (27817): FINE	Recoverbull server ready after 1 attempts

I had seen previously that Recoverbull didn't work when Orbot is running.

Output of adb logcat -d | grep -i "tor\|recoverbull" | tail -100:

11-27 19:14:35.449 21847 29570 D Orbot :
WARN: Not attempting connection to [scrubbed]:10444 because the network would reject it.
Are you trying to send Tor traffic over Tor? This traffic can be harmful to the Tor network.
If you really need it, try using a bridge as a workaround.

We had fixed it by only initializing embedded Tor when Orbot is not running. If it's running, we use it to route the Recoverbull traffic through Orbot

So I am not sure how this bug popped up or how it's working

Metadata

Metadata

Labels

No labels
No labels

Type

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions