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
{{ message }}
This repository has been archived by the owner on Jan 4, 2019. It is now read-only.
Controlling permission for local sockets is much easier than controlling permission for tcp sockets. For Tor mode, we should support connecting to the Tor socks proxy via a local socket so that it is not accessible to anyone else on the system who can make tcp connections to 127.0.0.1:9150. This requires:
teaching net/proxy about notation for local socket addresses, and
teaching net/socket about making the socks connections via local sockets.
Controlling permission for local sockets is much easier than controlling permission for tcp sockets. For Tor mode, we should support connecting to the Tor socks proxy via a local socket so that it is not accessible to anyone else on the system who can make tcp connections to 127.0.0.1:9150. This requires:
Related:
The text was updated successfully, but these errors were encountered: