gfw-report/trojan-go v0.10.10

on GitHub

版本介绍

在这个版本中，我们将trojan-go客户端的使用的uTLS从v1.1.5升级到了v1.2.0。

我作为一名用户需要做什么？

• 您需要根据自己的操作系统，选择对应的客户端下载并更新。
• 您不需要更新你的服务器。因为这次更新只对客户端做了改变。
• 您应该考虑将配置文件中的sni设置为服务器的域名。因为如果不配置SNI，客户端发送的Clienthello的指纹还是很特殊。
• 您不必在配置文件中特意设置fingerprint。因为默认值(Chrome)已经是最流行的指纹了。

为什么我使用了最新版本的客户端但是服务器还是被封锁了？

您是否在用这里提供的客户端的同时还通过其他客户端（比如手机上的软件）连接了相同的服务器？如果是的话，那就不能排除端口被封锁的是其他客户端的指纹或行为导致的。

我们现在缺少用户的使用情况汇报，如果您可以肯定在一段时间内只用了我们提供的客户端，我们非常欢迎您汇报您的使用情况（被封锁或是没被封锁对我们来说同样重要）。

配置文件示例

{
    "run_type": "client",
    "local_addr": "127.0.0.1",
    "local_port": 1080,
    "remote_addr": "your-domain-name.com",
    "remote_port": 443,
    "password": [
        "your_awesome_password"
    ],
    "ssl": {
        "sni": "your-domain-name.com",
	"fingerprint": "Chrome"
    }
}

感谢

我们感谢uTLS的开发者@gaukas 和 @jmwample。

Release notes

In this release, we upgrade trojan-go client's uTLS library from v1.1.5 to v1.2.0.

What do I need to do as a user?

• You need to update your client by downloading the corresponding binaries below.
• You don't need to update your server because all changes are made from the client side.
• You may want to set the sni value to your domain name in configuration file, because, your TLS Clienthello can still look very unique without the SNI extension.
• You don't have to specify the fingerprint value, because the default fingerprint (Chrome) is already the most popular one.

Why my server still got blocked when I used the latest trojan-go client?

Did you use any other trojan clients (eg. on your phone) to connect to the same server? If so, it cannot be determine whether the blocking is caused by this trojan-go client or other client's fingerprint and behaviors anymore.

We really want more users to report the status of their servers. If you are sure that you have been exclusively using the trojan-go clients we provided, please consider to report the status of your server (reporting not being blocked is as important as reporting blocking).

Example configuration file

{
    "run_type": "client",
    "local_addr": "127.0.0.1",
    "local_port": 1080,
    "remote_addr": "your-domain-name.com",
    "remote_port": 443,
    "password": [
        "your_awesome_password"
    ],
    "ssl": {
        "sni": "your-domain-name.com",
	"fingerprint": "Chrome"
    }
}

Credits

We thanks uTLS developers @gaukas and @jmwample for their time and efforts.