-
Notifications
You must be signed in to change notification settings - Fork 91
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
forward TCP port to http proxy or socks5 server "Segmentation fault" when using wrong pwd #37
Comments
@osnosn Thank you for your detailed bug report. I will confirm the bug as soon as possible. |
run it 192.168.1.200:1080 is a "3proxy" service run in debian, provides http proxy(8888) and socks5(1080) that requires account authentication.
I change If I use correct password for socks5 or http proxy. |
I will test and fix it on weekend. |
Now we add a debug version of xfrpc with asan that can detect memory errors in pr. cmake -DCMAKE_BUILD_TYPE=Debug .. |
I don't know how to compile. Downloaded the SDK for openwrt. |
#37 run
|
system "Debian GNU/Linux 11 (bullseye)" , x86_64
build Failed
build OK
build OK
Works fine. Port forwarding to HTTP proxy or socks5. On Debian x86_64 systems. No bugs were found. |
thanks, I will try to fix it. |
In Openwrt 22.03 , xfrpc - 2.1.606-1,
system type : MediaTek MT7620A
CPU model : MIPS 24KEc V5.0
run it
/usr/bin/xfrpc -c frpc.ini
127.0.0.1:1080 is a local socks5 service that requires account authentication.
"frps-0.42.0" is running in my Debian system (x86_64).
I use ssh with
ProxyCommand ncat --proxy-type socks5 --proxy 127.0.0.1:31080 --proxy-auth usr:12345 %h %p
connect to the remote server,If wrong password used, xfrpc crashes with "Segmentation fault".
I change 127.0.0.1:1080 to http proxy.
I use ssh with
ProxyCommand ncat --proxy-type http --proxy 127.0.0.1:31080 --proxy-auth usr:12345 %h %p
connect to the remote server,If wrong password used, xfrpc crashes with "Segmentation fault".
If use correct password for socks5 or http proxy.
xfrpc works fine.
The text was updated successfully, but these errors were encountered: