A full VPN is not always necessary. In addition, VPN connections may be unavailable because of restrictions imposed by a local or national internet provider. For the same reasons, a direct connection to an external SOCKS proxy may not work. Sometimes an alternative network route is needed not for the entire system, or even the entire browser, but only for specific addresses: an external API, an admin panel, documentation, a registry, a test environment, or another resource that is unavailable through the usual route.
In this article, we’ll look at a narrower approach to solving this problem:
This article has been indexed from DZone Security Zone
Read the original article:
Building a Windows App for a Resilient SSH SOCKS Proxy and Selective Browser Routing