Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added options to connect over TOR #31

Merged
merged 5 commits into from
Dec 29, 2018
Merged

Conversation

mpieters93
Copy link
Contributor

TL;DR

Added options to connect over TOR.

Full explanation

For those who value privacy, it might be important to be able to connect over TOR. This PR adds two command line arguments:

  • --tor or -t: set up a TOR circuit to connect to all websites using the torrequest package.
  • --unique-tor or -u: sets up a unique TOR circuit for each website using the torrequest package.

As connecting over TOR is only possible when TOR is installed/in the system PATH, this requirement is also referred to in the documentation of the CL arguments. The documentation now also mentions that connecting over TOR (especially establishing new circuits) adds to the runtime of the program.

Finally, as can happen with any IP, some services might decide to block requests coming from known TOR exit nodes. This might increase connection errors and thus a warning message was added to inform the user about this potential consequence.

@mpieters93
Copy link
Contributor Author

Noticed that the CSV PR made that this PR had merge conflicts. Just resolved those, so it is ready to be merged again as far as I'm concerned :-)

@hoadlck hoadlck merged commit 9b83571 into sherlock-project:master Dec 29, 2018
@hoadlck
Copy link
Contributor

hoadlck commented Dec 29, 2018

Thanks for rebasing your development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants