[GH-ISSUE #254] Maybe a bug in socks proxy process when using tcp without authentication in backend. #172

New issue

Closed

opened 2026-02-27 23:15:47 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 23:15:47 +03:00

Owner

Originally created by @laikee99 on GitHub (Apr 2, 2019).
Original GitHub issue: https://github.com/snail007/goproxy/issues/254

During socks5 proxy progress, we tested for serval auth situations,
In this 👇 section , A is the front server as downstream, so B is the backend server as upstream.

A	B
A is encrypted	B is none encrypted
A is none encrypted	B is encrypted
A is encrypted	B is encrypted

SO, whatever I tested using command such as:

a ./proxy socks -t tcp -p "0.0.0.0:1080" -T tcp -P "B:1080" -g "A"
b ./proxy socks -t tcp -p "0.0.0.0:1080" -T tcp -P "B:1080" -g "A" --auth-url "http://AUTH_URL/account.cgi"
In the a command, I can input any user & pass. I can not use udp proxy due to wrong password , but I can use tcp well.
In the b command, I can not input anything except the correct user and pass, but My tcp and udp proxy IP shows the server A's.
Why I am doing this:
IF B server would down I can change it easily due to domain host name , but I require user/pass to let out stuff have access to server.
What I want to improve:
I want to Use Correct account to send proxy requests , not just verify users when they go through the UDP but also TCP.

Originally created by @laikee99 on GitHub (Apr 2, 2019). Original GitHub issue: https://github.com/snail007/goproxy/issues/254 During socks5 proxy progress, we tested for serval auth situations, In this 👇 section , A is the front server as downstream, so B is the backend server as upstream. | A | B | |----------------------- |--------------------------------| | A is encrypted | B is none encrypted | | A is none encrypted | B is encrypted | | A is encrypted | B is encrypted | **SO, whatever I tested using command such as:** - **a** ./proxy socks -t tcp -p "0.0.0.0:1080" -T tcp -P "B:1080" -g "A" - **b** ./proxy socks -t tcp -p "0.0.0.0:1080" -T tcp -P "B:1080" -g "A" --auth-url "http://AUTH_URL/account.cgi" In the **a** command, I can input any user & pass. I can not use udp proxy due to wrong password , but I can use tcp well. In the **b** command, I can not input anything except the correct user and pass, but My tcp and udp proxy IP shows the server A's. **Why I am doing this:** IF B server would down I can change it easily due to domain host name , but I require user/pass to let out stuff have access to server. **What I want to improve:** I want to Use Correct account to send proxy requests , not just verify users when they go through the UDP but also TCP.

kerem closed this issue

2026-02-27 23:15:47 +03:00

kerem commented

2026-02-27 23:15:47 +03:00

Author

Owner

@laikee99 commented on GitHub (Apr 2, 2019):

Thank you for your precious time and value!
:)
👍

@laikee99 commented on GitHub (Apr 2, 2019): Thank you for your precious time and value! :) 👍

kerem commented

2026-02-27 23:15:48 +03:00

Author

Owner

@snail007 commented on GitHub (Apr 2, 2019):

you should using function sps instead of that.Fully access control is supported by the sps.

@snail007 commented on GitHub (Apr 2, 2019): you should using function sps instead of that.Fully access control is supported by the sps.

kerem commented

2026-02-27 23:15:48 +03:00

Author

Owner

@snail007 commented on GitHub (Apr 2, 2019):

in your case,you should noticed argument with --always

@snail007 commented on GitHub (Apr 2, 2019): in your case,you should noticed argument with --always

kerem commented

2026-02-27 23:15:48 +03:00

Author

Owner

@snail007 commented on GitHub (Apr 3, 2019):

you can disable each of http(s) \ss \sockks with --disable-xxx,
reading outputting of proxy help sps

@snail007 commented on GitHub (Apr 3, 2019): you can disable each of http(s) \ss \sockks with --disable-xxx, reading outputting of `proxy help sps`