-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Support of SOCK5 password authentication for sslocal #788
Comments
Why is that useful in shadowsocks' use case? |
Selected people (or single user) could connect from local network using simple socks5 settings, avoiding use (and abuse) by other users from that network. Thus, getting simpler usage in the intranet (since many software support socks5 natively) but still getting encryption outside. |
I don't think this is useful because shadowsocks' SOCKS5 UDP port is fixed. SOCKS5's UDP authencation is done by TCP, but shadowsocks wouldn't allocate a new port for every authencated clients. |
What about authentication only for TCP? This still could be useful for http. |
@zonyitoo Thank you very much! |
Can you support SOCK5 authentication for incoming connections? This may extend use cases.
The text was updated successfully, but these errors were encountered: