Urgh, I don't really have time to do this migration but guess I'm planning it in anyway.
Past me was a lazy bum. But I'm confident that future me is all over this. Time for a nap.
This is a most excellent place for technology news and articles.
Urgh, I don't really have time to do this migration but guess I'm planning it in anyway.
Past me was a lazy bum. But I'm confident that future me is all over this. Time for a nap.
Damn you sir, you didn't need to call me out with that last paragraph.
No, I know it wasn't my shoe, but look at how well it fits!
A bit annoying for all the things that don't support openvpn, like old Synology NAS devices.
WG was always so much better anyway.
Well it was written to replace open VPN right? So that makes sense
Because OpenVPN is fiddly to set up and modern Wireguard setups seem to scale well enough.
I remember maybe 12-15 years ago, setting OpenVPN on my TomatoUSB flashed router, invoking all kind of openssl command to generate certificates, keys, signing stuff, setting the router, setting the TAP/TUN clients etc. but once setup it works for years on my laptop, phone, etc.
Now with WG I basically scan on my phone a QR code generated on my Merlin router and that's it.
merlin has built-in wireguard support??
Good! That shit needs to be phased out.
I only have one problem with this. When they say wireguard being crypto opinionated is a good thing. I am weary to agree with that statement entirely.
While it is good for stability (only one stack to support and get right, and to be secure and efficient) I do wonder about overall and future security. Saying "You must use this specific cipher suite because we think it's the best" is a bit of a dangerous road to take.
I say this just because Curve 25519 is considered a very secure elliptic curve, to the best of my very limited knowledge on this subject. But we had a certain dual elliptic curve pseudo random number generator was pushed as "best practice" (NIST backed) some time ago, which didn't turn out so well, even omitting possible conspiracy scenarios, it had known weaknesses even before it was recommended. [1]
Since then I've generally not been a huge fan of being given one option as "the right way" when it comes to cryptography. Even if it is the "best" it gives one target to try to find a weakness in, rather than many.
I say all this as a wireguard user, it's a great, fast and reliable VPN. I just have concerns when the choice of using other algorithms and especially putting my own chosen chain together is taken away. Because it puts the exact same target to break on every one of us, rather than having to work out how to break multiple methods and algorithms and multiple combinations.
I think the idea behind opinionated cryptography is not only the idea of "We think this is the best, so you have to use it", but most importantly it removes all requirements of the protocol supporting cipher negotiation. This makes the protocol much simpler, easier to audit and as a result more secure. And if the cryptography in the protocol ever shows a weakness, then Wireguard v2 needs to be released as a breaking change. See all the SSL/TLS versions
Yep. I entirely agree about the good points. I am just always weary about removing options like this, regardless of intention.
I'd be fine if for example I'm running my own wireguard implementation, I could choose the suite to use, not negotiate anything and ensure my client has the same configuration.
I'd probably not use it, but I like the option, and knowing that anyone that wants to try to break this now also needs to guess what options I'm running.
knowing that anyone that wants to try to break this now also needs to guess what options I’m running.
Unless your security model has you being specifically targeted by advanced threat actors, the most likely scenario is that you’ll be affected by randomly discovered security vulnerabilities and not individuals tailoring an attack for your configuration.
Obfuscation of your configuration doesn’t add much security and using obscure settings could just as easily result in security vulnerabilities of their own. Vulnerabilities which, due to the obscurity of your configuration, may not be discovered by white hats for much longer.
I know that, if wireguard is exploitable, it’s very unlikely to be me that would be targeted. There are larger and more lucrative targets acting as honeypots for everyone else.
No. You are making assumptions about security and ultimately assuming you're the only one who thought this along the way.
mullvad and windscribe are the only two i support <3
Do you have a stance on IVPN?
I’ve had an active iVPN sub for almost 8 years now. Cannot say anything bad about them whatsoever
why yall need a vpn?
Privacy
recently switched from mullvad to ivpn, and the servers are noticeably slower. with mullvad all the servers I used achieved my connections max speed 500 mb/s but on ivpn they usually do 50 - 300, and sometimes i need to switch server because they go down (i use european servers). only reason i switched was because mullvad causes a wakelock on mint cinnamon and it drives me nuts.
Is that a Mint Cinnamon issue primarily?
it hasn't happened on other distros but i have other bigger issues on them so i never could test for a longer period. took me a year to find what caused it and it hasn't happened since i switched from mullvad. fun bonus: ovpn destroyed my nvidia drivers on mint...
I started on mint years ago and it was an okay foot in the door, but would not recommend to anyone (including beginners). Fedora is my goto for new users these days. I use arch (btw) and have had much more luck on rolling release.
Not gonna try to convince you off Mint, but it does sound like you're having issues with it.
Bummer. For whatever reason I always get much better speeds on openvpn servers.
Sounds like an issue with your network or routes. By design, WG is faster.
Only the opposite has ever happened for me.
That's not something you hear very often.
That’s very strange. WireGuard was specifically created in part because of speed limitations.