I use ipsec-tools, as circa 2012 when I was originally setting this up, it was the only free software IPsec solution I could get to work with iOS clients, but based on this vulnerability I've now disabled it and will try StrongSWAN again.
https://www.bestvpn.com/blog/5919/how-to-hide-openvpn-traffi...
Plus, I wanted to better secure my home network AND make it accessible remotely (in a dorm-like accomodation with enterprise-grade NAT with Cisco gear), I thought an IPSec tunnel would be optimal as well.
https://github.com/jlund/streisand
EDIT: Forgot the link, like a proper idiot.
The article mentions Vista and Window Server 2008, but it applies to Windows 7 and Windows 8 as well. There are some Stack Overflow threads as well.
For the VPN setup, I largely followed these instructions:
http://www.stormacq.com/build-a-private-vpn-server-on-amazon...
There are a few typos in the scripts cited in the article especially around saving the iptables rules.
OS X's native VPN client worked out of the box
IPSec is still the enterprise defacto standard. Its pretty much everywhere.
Yeah, it a little different for the FOSS home hobbyist, but for companies with a budget, its a trivial addition to their infrastructure (Cisco, Sonicwall, etc). FOSS IPSec implementations seem to be pretty non-existant in practice from my own experience and I only see FOSS-only shops using OpenVPN, which is OpenSSL based (which, of course, suffered from heartbleed).
Exactly. I'd love to see a simple, auditable and secure open source VPN software. (not OpenVPN)
Heck, Cisco's "Small Business" RV router series (RV042/RV082/RV016/RV042G and possibly others) are still being sold after several hardware revisions (still kind of long in the tooth), and they support all of two VPN types: IPSec and PPTP.
So definitely write about that. There is so much bullshit and misinformation I have read this week alone on VPN config in *nix environments, it's astounding. My shakiness was only confirmed by this article.
I'm in a meeting and drawing a blank on what the primary reason was for avoiding password-only... I'll update if I can remember the reason besides "passwords are easier to crack"
Maybe the certificates could be stored in LDAP.
And the difference between FreeSWAN, LibreSWAN, and StrongSWAN was very confusing to me unitl I read this.
http://serverfault.com/questions/173158/strongswan-vs-opensw...
I mean setting up VPN is no trivial pursuit, but the amount of effort to set any of these up to use native VPN clients for my mobile (Android devices) encouraged me to potentially consider StrongSWAN once I really review the documentation and learn as much as I can.
What are others doing?
Thanks for the cool article either way.