/etc/tor/torsocks.conf 不工作

Til*_*Til 5 authentication socks

我尝试激活的用户名和密码验证使用的字段我的Tor安装SOCKS5UsernameSOCKS5Password在/etc/tor/torsocks.conf文件。我在配置更改后重新启动了服务并检查它是否真的重新启动。但是在我的机器上没有用户名和密码的情况下仍然可以使用 tor。

我已经从 EPEL 仓库安装了 Tor。有关安装的更多信息:

Installed Packages
Name        : tor
Arch        : x86_64
Version     : 0.2.7.6
Release     : 5.el7


Current OS
CentOS Linux release 7.2.1511 (Core)


Tor Configuration
[root@torproxy ~]# cat /etc/tor/torsocks.conf | grep -v "^#"
TorAddress curl 10.0.0.43
TorPort 18009
OnionAddrRange 127.42.42.0/24
SOCKS5Username test
SOCKS5Password 1234

[root@torproxy ~]# cat /etc/tor/torrc | grep -v "^#"
ControlSocket /run/tor/control
ControlSocketsGroupWritable 1
CookieAuthentication 1
CookieAuthFile /run/tor/control.authcookie
CookieAuthFileGroupReadable 1
SOCKSPort 10.0.0.43:18009
SOCKSPolicy accept *
Run Code Online (Sandbox Code Playgroud)

Mic*_*ton 5

Tor 实际上并未尝试验证 SOCKS 客户端提供给它的身份验证信息。它可以完全未经身份验证使用,并且没有强制身份验证的配置。因此,强烈建议您不要将 SOCKS 端口暴露给您不想直接连接到它的任何 IP 地址。

从手册页:

       NOTE: Although this option allows you to specify an IP address
       other than localhost, you should do so only with extreme caution.
       The SOCKS protocol is unencrypted and (as we use it)
       unauthenticated, so exposing it in this way could leak your
       information to anybody watching your network, and allow anybody to
       use your computer as an open proxy.
Run Code Online (Sandbox Code Playgroud)

什么的Tor确实做的认证信息流隔离。Tor 可以配置为使用完全不同的电路,用于使用不同凭据“验证”的客户端。

       IsolateSOCKSAuth
           Don’t share circuits with streams for which different SOCKS
           authentication was provided. (On by default; you can disable it
           with NoIsolateSOCKSAuth.)
Run Code Online (Sandbox Code Playgroud)