First pass at having TorChat2 running with an external tor instance. #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(This is part of the solution for Issue #12, running TorChat pidgin
plugin under TAILS.)
It uses two configuration options:
"StandaloneTor" : 1,
"HiddenServiceName" : "the-hidden-service-name"
(The hidden service name is the content of the hostname file for the
hidden service without the .onion extension)
The tor instance has to include the following entries:
HiddenServiceDir /path/to/hidden-service-folder/
HiddenServicePort 11009 127.0.0.1:11009
LongLivedPorts 11009
SocksListenAddress 127.0.0.1:11109
What is missing: being able to specify the ports for the hidden service
and socks ports in the UI and maybe some script to create the hidden
service first time it is being run.
I tested this running under pidgin 2.10.6-2, tor 0.2.3.25-1 and torchat
0.9.9.550-2.