OpenVPN

The main novelties concern the switch to NotResolver as a DNS resolver, improvements to system stability, and fixes for specific issues related to VPNs and network configurations.

Among the key features introduced with this update are resolution of DNS issues for VPN clients, IPsec, WireGuard, OpenVPN.

Update of the Linux kernel to version six point eighteen point fifty-four to improve stability and security.

Fixes for importing WireGuard configurations with multiple subnets.

Like, what you have to do is...

How do I put this best? Instead of trying to terminate it with your own custom TLS thing, you just run OpenVPN or WireGuard.

Use non-good solutions that community actually maintains for you.

And don't expose anything else.

If I have, say, GLM 5.3 or Kim or Quinn, whatever, just pick any model you want, which is not even Gemini, and I- I'll come back to Gemini.

I'm not surprised today if I'm decently skilled in knowing what I would want the direction to be, or I can point to a blog of if I know that, let's just go back to the enterprise example for developers, I know that everyone has installed some version of OpenVPN, and I know there's a vulnerability because I found a CVE that was announced or a Kev one, whatever, whichever vulnerability platform you want to follow, and I go through a blog of, hey, how does this work? Unpack this for me.

Reverse engineer what was missing that led to the vulnerability.

And the models are so smart these days.

You don't even need to be a script kiddie anymore that people used to look down on.

You literally could just point at a website and go, "Hey, learn everything about SQL injection.

Learn everything on OpenVPN and use that to get me an entry point or a co- or a terminal into this machine." It would do that.

That's, that's why it doesn't surprise me anymore.

It started as a community idea.

The late John Hayes, was looking at what people were doing with OpenVPN and things like L2TP and IPsec and thinking there's got to be a way to get past the limitations of the IP-IP mesh arrangement and get 44-net addresses onto people's equipment through just about whatever infrastructure they have.

So they were working on...

Sorry, standby.

brought it up with the community, and people like Adam Lewis, who's now on staff, and Zachary Sagin, and Dave Gingrich, all these people were like, yeah, we love this idea, love to see it work.

And that community group came together with a proof of concept and a specifications document, and people like Ian Redden wrote up a really nice, you know, rundown on everything that it needed to do, and there was people looking at it from a security perspective.

And through all of this, OpenVPN wound up not working so well, but WireGuard hit the scene.

And it was like, this is it.

Uh, we looked at one other option.

We looked at OpenVPN Connect, um, just because that was a, a pretty simple solution to set up.

It was, uh, you know, you spin up the server, you create the accounts, and people can just connect.

It was, uh, it was, uh, very user-friendly, and it was, uh, easy to manage.

Um, getting into remote desktop was okay, uh, but there was a little bit of lag, and we also allow access to file shares and stuff like that over the VPN.

Mm-hmm.

And that's where OpenVPN was very limiting.

Uh, we were getting super slow connection speeds even though we have, you know, gig- a gigabit connection here.