Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advice on obfs #1030

Closed
Anonymous-Someneese opened this issue Jan 3, 2017 · 1 comment
Closed

Advice on obfs #1030

Anonymous-Someneese opened this issue Jan 3, 2017 · 1 comment
Labels

Comments

@Anonymous-Someneese
Copy link

I though obfs is a good idea to get though naive QoS of some ISPs. However it would increase the flow characteristics, like UA always set to curl, 101 upgrade to WebSocket everytimes. The original shadowsocks protocol is designed to be no-characteristics, anonymous thus hard to be distinguished from the normal encrypted flows. I worried that obfs may be a weakness for the YOU KNOW WHO to detect shadowsocks protocol.
Further more, we cannot customize the request and response header. If this feature is widely used, it would be easy to collect all the shadowsocks server:port.

@madeye
Copy link

madeye commented Jan 3, 2017

The proposal has been deprecated: shadowsocks/shadowsocks-org#26

@madeye madeye closed this as completed Jan 6, 2017
@madeye madeye added the question label Jan 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants