search

shadowsocks / shadowsocks-go

go port of shadowsocks (Deprecated)
http://shadowsocks.github.io/shadowsocks-go
Apache License 2.0
6.62k stars 3.34k forks source link

obfs4 obsessed with traffic support plan? #250

Open wpecker opened 6 years ago

wpecker commented 6 years ago

If the problem, confusing traffic, Go version does not support?

arthurkiller commented 6 years ago

@penhauer-xiao I will try, if necessary

elico commented 6 years ago

@arthurkiller I have tried google translate but it's not really working with this language(chines right?) Can you translate the issue?

testcaoy7 commented 6 years ago

@elico arthurkiller wants to use obfs4 from tor to disguise the ShadowSocks traffic as TLS traffic. This is not a great idea because obfs4 might get blocked too. The best solution is to use tools like Stunnel, to transport connection via REAL TLS. In my own case, I ditched ShadowSocks long ago. I think 3proxy + Stunnel is a better solution.

elico commented 6 years ago

@testcaoy7 thanks. I really can't read c\c++ that much compared to GoLang. Is there something similar to 3proxy in GoLang that you may know about?

wpecker commented 6 years ago

@testcaoy7 You mean 3proxy + Stunnel compare ShadowSocks better.

testcaoy7 commented 6 years ago

@penhauer-xiao I find that TLS is a better solution to bypass "China" firewall beacause it is a widely used protocol thus cannot be banned easily. It also allow you to bypass QoS system. You can replace stunnel to any tunnel you like, such as kcptun. It also works well with 3proxy.

Obfs4 alreadly get blocked in Kazakhstan (which means it can be blocked and this is why I don't want to use it).

wpecker commented 6 years ago

@testcaoy7 Ok， thanks

catrixs commented 6 years ago

how about this? any progress?

arthurkiller commented 6 years ago

looks cool, and wanna support

Best regards ✉️✉️✉️✉️✉️✉️✉️✉️✉️✉️✉️✉️✉️✉️

Arthur lee Sent from my iPhone

On 8 Mar 2018, at 12:05 PM, 陈飞 notifications@github.com wrote:

how about this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.