-
Notifications
You must be signed in to change notification settings - Fork 370
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
[Feature Request] Add Authentication Support for SOCKS Service in wstunnel Client #312
Comments
Hello @dobelachaos 👋 This issue is being automatically closed because it does not follow the issue template. |
Hello, Thank you for the detailed explanation. Anyway, I am going to add the login/password for socks5 and let you know when it is done, so you can try it out |
Thank you very much for your work, and I agree with your opinion that username and password authentication is sufficient. Thank you again. |
Hi back, Would you mind trying this pre-release and let me know if it works for you ? You can specify login/password of your socks5 server like that let me know ! |
Okay, I will try it. Thank you for your work! |
Hello, I followed your example to specify the username and password for the SOCKS5 on the client, but the terminal returned an error message. Here is the error message: "error: the following required arguments were not provided: <ws[s]|http[s]://wstunnel.server.com[:port]>". I have tried both "wstunnel_9.7.3-rc1_windows_amd64.tar.gz" and "wstunnel_9.7.3-rc1_linux_arm64.tar.gz", and the error messages returned are the same. The command I used to start is: "wstunnel client --http-upgrade-path-prefix *********** -L socks5://192.168.2.192:1080?login=admin&password=admin wss://...:1843". |
You miss the quote around the argument of -L
|
Thank you for your guidance; I have successfully used it and resolved my needs. Thank you again! Now, I have two issues to report to you:
|
Happy to know it is working for you :0 For the performance I don't know, it is the socks5 lib that is supposed to handle it. The penalty should be very small, as the auth is only check at connection. Will try to take a look at it when I get some spare time. Regarding the 2nd point, it is normal, if you dont specify any password, it means you don't want any auth, so it allows everyone, like it is today |
Ok, I understand, thank you for your work. I'm using it very well now. ) : |
released in v9.7.4 |
How to set it up on the server ?? wstunnel server --restrict-http-upgrade-path-prefix 'xxxx' https://serverip:xxxx?login=admin&password=admin |
Description of the feature
I am using
wstunnel
for creating a SOCKS proxy to access resources behind firewalls and would like to request a feature that adds authentication support to the SOCKS service created by thewstunnel
client.Current Functionality
Currently,
wstunnel
allows the creation of a SOCKS5 service without authentication. This is useful for simple use cases but lacks the security needed for environments where access control is required.Proposed Feature
The feature I am proposing is the addition of an authentication option for the SOCKS service. This would involve the following:
wstunnel
client to enable authentication for the SOCKS service.Use Case
The ability to add authentication to the SOCKS service would greatly enhance the security and usability of
wstunnel
in environments where only certain users should have access to the proxy. For example, in corporate settings or shared hosting environments, adding authentication would ensure that only authorized users can use the proxy to access the internet or internal resources.Implementation Suggestions
Benefits
Adding authentication support would:
wstunnel
by preventing unauthorized access to the SOCKS proxy.wstunnel
more versatile and suitable for a wider range of use cases, including those with strict security requirements.Additional Information
wstunnel
.Thank you for considering this feature request. I look forward to any feedback or discussion on this proposal.
The text was updated successfully, but these errors were encountered: