Issue Details
Sometimes some applications (such as banking applications or others from large providers) scan local ports for open HTTP/SOCKS proxies. When such a proxy is detected, they make an unauthorized connection to it and make a request to their server through that proxy. This reveals the proxy's IP address, allowing it to be blacklisted globally on country provider level. This is currently a serious problem—the local SOCKS server is unprotected, and sometimes we need that local proxy running
Article - https://habr.com/ru/articles/1020080/
POC application - https://github.com/runetfreedom/per-app-split-bypass-poc
Proposed solution
SOCKS server authentication has been added using login and password, which can be configured in a separate settings section.
Alternative solution
No response
Issue Details
Sometimes some applications (such as banking applications or others from large providers) scan local ports for open HTTP/SOCKS proxies. When such a proxy is detected, they make an unauthorized connection to it and make a request to their server through that proxy. This reveals the proxy's IP address, allowing it to be blacklisted globally on country provider level. This is currently a serious problem—the local SOCKS server is unprotected, and sometimes we need that local proxy running
Article - https://habr.com/ru/articles/1020080/
POC application - https://github.com/runetfreedom/per-app-split-bypass-poc
Proposed solution
SOCKS server authentication has been added using login and password, which can be configured in a separate settings section.
Alternative solution
No response