-
Updated
Jun 27, 2020 - C#
shadowsocks
Here are 635 public repositories matching this topic...
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Open Shadowsocks app
- Click on bottom of the screen "Connected, tap to check ..."
- "Success: HTTPS handshake took ..." info cannot display the 2nd line
Expected behavior
The info should be displayed in full.
Screenshots
 to Outline. I don't understand protocol at all: what is password, what is host, what is port, which encryption used by Outline and why my third-party client doesn't work.
Outline client is easy to use, but it
-
Updated
Jul 6, 2020 - C#
-
Updated
Jun 30, 2020
Use md5(username + password) to store login password is not secure, please consider use sha256.
用 md5(username + password) 的方式存储密码是不安全的,建议至少使用 sha256.
Starting with v1.2.1, keys can be sorted by name or utilized bandwidth. I find the feature very useful for identifying both heavy users and unused keys.
It’d be even nicer to have chosen sorting settings preserved between launches.
-
Updated
Dec 17, 2019 - Shell
-
Updated
Jun 4, 2020
-
Updated
Jul 3, 2020 - Shell
关于项目Archive的一些解释
本人最近时间有点紧,加上最近身体有些问题。想着issue太多看了就有点遭不住了就archive了。想了好久还是unarchive了这个项目。接下来这个项目会更新的比较缓慢,但是不会停更。。你们的每个issue我都有看,感谢大家一如既往的支持。本项目将不会接受捐赠并且开源。下载前请验证checksum是否一致。
-
Updated
Jun 14, 2020 - Python
Improve this page
Add a description, image, and links to the shadowsocks topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the shadowsocks topic, visit your repo's landing page and select "manage topics."
对于使用云服务的负载均衡器(Azure 或者 Google cloud)以及 CDN 的用户,因为负载均衡器和 CDN 是可以直接接管证书和 TSL 甚至 HTTP/2 、 QUIC 的,所以希望 v2ray 作为客户端使用时也能够支持像浏览器一样自动协商底层传输协议是 HTTP 1.1 还是 HTTP/2 或 QUIC 。相当于在入站协议上提供一个尽量简单、不占资源的 HTTP 类型的底层传输协议,如 #1644 所需求的,再由客户端在出站协议上与负载均衡器自动协商。当然如果入站协议也能够提供一个支持多版本协商的 HTTP 底层传输协议那也再好不过。
以及目前 WebSocket 是直接使用 WebSocket 连接的,与浏览器的 HTTP 协商升级为 ws 的行为有所不同,跟据[谷歌云的表述](https://cloud.google.com/load-balancing/docs/