You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
if get_global_tor ever got called, use that tor we launched (adding a SOCKS port if needed)
try connecting to 9151 as a control-port (and ask for the SOCKS port(s))
try connecting to 9051 as a control port (ask for SOCKS ports)
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.
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:
The text was updated successfully, but these errors were encountered: