From 7dd4ad9c628aca5025e173c170aae4d9b06c5f94 Mon Sep 17 00:00:00 2001 From: Akari Naebushi Date: Mon, 25 Nov 2024 16:39:26 +0300 Subject: [PATCH] Update ss.md (fixes #614) Added note regarding auther usage with shadowsocks handler --- en/docs/tutorials/protocols/ss.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/en/docs/tutorials/protocols/ss.md b/en/docs/tutorials/protocols/ss.md index f0f4972..1f0c9a7 100644 --- a/en/docs/tutorials/protocols/ss.md +++ b/en/docs/tutorials/protocols/ss.md @@ -29,6 +29,8 @@ GOST's support for shadowsocks is based on the [shadowsocks/shadowsocks-go](http type: tcp ``` +!!! caution "Shadowsocks Handler" The Shadowsocks handler cannot use authenticator, and only supports setting single authentication information as encryption parameter. + !!! tip "Delay Sending" By default, the shadowsocks protocol will wait for request data, and when it receives the request data, it will send the protocol header information to the server together with the request data. When the client option `nodelay` is set to `true`, the protocol header information will be sent to the server immediately without waiting for the user's request data. When the server connected through the proxy actively sends data to the client (such as FTP, VNC, MySQL), this option needs to be turned on to avoid abnormal connection. @@ -174,4 +176,4 @@ Shadowsocks proxy can be used in combination with various data channels. type: ss listener: type: kcp - ``` \ No newline at end of file + ```