feat: Add ACL in tuic-server and reject client's access to server's localhost by default, implement SOCKS5 outbound #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Altough you suggest me to contribute to wind in the previous PR,
I think this PR is crucial as it fixes a security pitfall of tuic.
Also, this implements SOCKS5 outbound, which is marked as TODO in the previous PR.
This PR includes:
The syntax is inspired by Hysteria
Currently, Tuic allows the client to access services not publicly exposed(i.e. bind to 127.0.0.1 / ::1) on the server. However, users having access to Tuic are not necessarily supposed to have SSH access to server, thus, this may lead to unwanted and unaware intrusions into local services.
To expose services on the server to client users deliberately, explicitly whitelist those ports or use '*' to allow access to all ports on localhost.
I think after this PR, Tuic's outbound and ACL feature is on par with Hysteria.