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

"find a tor" for client-side "tor:" endpoints #128

Open
meejah opened this issue Sep 22, 2015 · 1 comment
Open

"find a tor" for client-side "tor:" endpoints #128

meejah opened this issue Sep 22, 2015 · 1 comment

Comments

@meejah
Copy link
Owner

meejah commented Sep 22, 2015

If a user currently uses a "tor:" client-side endpoint, it currently just tries 9050 and 9150 as SOCKS endpoints. This isn't sufficient, nor particularly safe.

What it should do instead is something like the server-side ("onion:") endpoints, and do the following:

  1. if get_global_tor ever got called, use that tor we launched (adding a SOCKS port if needed)
  2. try connecting to 9151 as a control-port (and ask for the SOCKS port(s))
  3. try connecting to 9051 as a control port (ask for SOCKS ports)
  4. call get_global_tor() ourselves, thus launching one.
@meejah meejah added this to the 1.0 milestone Oct 9, 2015
@david415
Copy link
Contributor

yes and if the endpoint descriptor string specifies a socks port then only that socks port should be used; here i'm thinking of people who use sandboxing to isolate various application... they might prefer an application to use a specific instance of tor.

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

No branches or pull requests

2 participants