Re:Important security vulnerabilities in OpenVPN
by curun1r on Wednesday June 21, 2017 @12:13PM
(#14605056)
For Mac users, Sidestep [1] offers a similar VPN over SSH experience. It's the only VPN product I've ever used that I've never had an issue with...it just works (no doubt due to the bulletproof nature of SSH).
Re:Important security vulnerabilities in OpenVPN
by rsync on Wednesday June 21, 2017 @03:57PM
(#14607321)
This interested me however it appears to be abandoned ... last commit was on 2013-10-25 and comments like the one at the end of this comment thread:
https://github.com/chetan51/sidestep/issues/62
indicate that it is abandoned ...
Re:Important security vulnerabilities in OpenVPN
by westbywest on Wednesday June 21, 2017 @10:58AM
(#14604323)
tinc is also a popular lightweight VPN, although it's targeted for embedded. It does nevertheless support the libreSSL fork mentioned upthread. https://www.tinc-vpn.org/
Re:Important security vulnerabilities in OpenVPN
by sr2 on Wednesday June 21, 2017 @12:29PM
(#14605240)
+1 for tinc
Re:Important security vulnerabilities in OpenVPN
by sigjuice on Wednesday June 21, 2017 @11:25AM
(#14604570)
The first line on the sshuttle GitHub page says 'does not require admin'. Why even have installation instructions via 'sudo' then?
Re:Important security vulnerabilities in OpenVPN
by ckuehl on Wednesday June 21, 2017 @11:38AM
(#14604711)
A benefit of installing using your system package manager is that you can rely on your distro to manage the security of the package. If you just `pip install` it, you need to personally watch for new security bugs and upgrade (or backport them to your current version, which is what e.g. Debian will do for you). You'd also need to do that for all of the dependencies.
Up to you if you trust your distro's security team, of course :). I trust mine.
Re:Important security vulnerabilities in OpenVPN
by sigjuice on Wednesday June 21, 2017 @12:12PM
(#14605043)
I did not say anything about package managers. I trust my distro and its suppplied packages just like you trust yours and aim to use official packages as much as I can.
The instructions in README.md say "sudo pip install" and "sudo ./setup.py". To me, that is a bad idea. Things that are manually installed should be kept in completely separate directories. My preference is to install such packages in my home directory, which should in no way require sudo.
It does require that you own an sshd running on an endpoint somewhere (like a VPS or an EC2 instance or your own server somewhere) - but if you can clear that hurdle, you end up with a very elegant and simple solution.
[1] https://github.com/sshuttle/sshuttle