3 ms·
I think the answer is mostly that it's hard to route most traffic over SOCKS, most applications don't obey the system-wide proxy settings, you might be leaking
by StavrosK 9y ago
I think the answer is mostly that it's hard to route most traffic over SOCKS, most applications don't obey the system-wide proxy settings, you might be leaking DNS queries, things like that.
- gcb0 9y agoif you are willing to let a vpn client abuse your system, you might also want to set a network interface that routes all traffic to the ssh tunnel. might be trivial to add as a module if not available already.
- zylent 9y agoIn most configurations, it’s trivial to use the os native VPN client, with some minor caveats. This creates a tunnel device and does what 99% of end-users working remotely need.
- gcb0 9y agothe OS vpn still have the same problems. For example, you can run an application that asks the OS to not use the vpn. That is why most vpn clients will break your ability to set proxies (try to enable cisco enterprise vpn client on OSX and then open charles proxy and see how sad you will be) my point is: on all setups you have traffic that might go around the vpn tunnel, that is an application defect not that ssh tunels are worse.
- cookiecaper 9y agoStill not as thorough as a full-fledged "real" VPN, but for most ad-hoc purposes, something like sshuttle [0] works well and doesn't require application-specific configuration. [0] https://github.com/sshuttle/sshuttle https://github.com/sshuttle/sshuttle
- rsync 9y agoI am very excited about sshuttle (and in fact, rsync.net has sponsored work on it). The most compelling aspect of sshuttle, in my opinion, is that any host running sshd can be an endpoint - no software is required. As long as the sshd in question has python available, you can use it as an endpoint.