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

SOCKS Authentication fails for CONNECT if username contains special characters #548

Closed
mschfh opened this issue Aug 21, 2024 · 2 comments · Fixed by #550
Closed

SOCKS Authentication fails for CONNECT if username contains special characters #548

mschfh opened this issue Aug 21, 2024 · 2 comments · Fixed by #550
Assignees
Labels
backend Issues related to the platform backend. bug Something isn't working. medium priority Medium priority issues to be done in a couple of sprints. t-platform Issues with this label are in the ownership of the platform team. validated Issues that are resolved and their solutions fulfill the acceptance criteria.

Comments

@mschfh
Copy link

mschfh commented Aug 21, 2024

SOCKS authentication fails for CONNECT requests when the username contains a @:

proxyChain.anonymizeProxy({url: "socks5://[email protected]:[email protected]:1080", port: 12345})

For a HTTP request, everything works as expected (the username is sent as-is).

curl -v --proxy 'http://127.0.0.1:12345' 'http://ifconfig.co'
image

For a HTTPS / CONNECT request, the username sent to the upstream SOCKS5 proxy is URL escaped (e.g. foo%40bar.baz, as seen in a packet capture) and the SOCKS authentication request fails due to incorrect credentials, the proxy returns a 597 error.

curl -v --proxy 'http://127.0.0.1:12345' 'https://ifconfig.co'
image
@fnesveda fnesveda added t-platform Issues with this label are in the ownership of the platform team. bug Something isn't working. medium priority Medium priority issues to be done in a couple of sprints. backend Issues related to the platform backend. labels Aug 21, 2024
@jirimoravcik
Copy link
Member

Fixed in #550

@mschfh
Copy link
Author

mschfh commented Aug 21, 2024

Thank you, the fix works as expected.

@jirimoravcik jirimoravcik added the validated Issues that are resolved and their solutions fulfill the acceptance criteria. label Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Issues related to the platform backend. bug Something isn't working. medium priority Medium priority issues to be done in a couple of sprints. t-platform Issues with this label are in the ownership of the platform team. validated Issues that are resolved and their solutions fulfill the acceptance criteria.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants