WireGuardNT and WireGuard for Windows version 1.0 have been released. Big milestone! For a brief technical discussion of some reverse engineered improvements, see the announcement: lists.zx2c4.com/pipermail/wi…

You can download the fetcher installer from wireguard.com/install/, which checks ed25519 signatures and always downloads the latest version, or get direct MSIs for enterprise usage. Or, apparently, now you can run `winget install wireguard`.

WireGuardNT v0.11 and WireGuard for Windows v0.6 have been released: lists.zx2c4.com/pipermail/wi…

WireGuard has some big updates ready to go on Windows, our first on the platform in nearly 4 years. We've done some nice modernizations and improvements, fixed bugs, added features, updated the toolchain, and more. But our release is currently blocked by @Microsoft. The recent thread on Hacker News encouraged me to write this up, rather than just grumbling to myself privately about it as I have the last two weeks. I logged in to get the WireGuardNT driver signed -- a necessary step for driver authors -- and was greeted by this vague message that the account has been suspended. Looking further into it, it seems like they instituted an identity verification policy, didn't notify me about it, and then I guess they suspended accounts who didn't do the verification. So of course I did the ID card verification immediately, but now an appeal is necessary. The appeals process requires filing a support ticket, but filing a support ticket requires a non-suspended account... Catch-22, eventually resolved by filing one through Azure and getting it rerouted to the right department. That was two weeks ago. Now they've told me there's a 60 day appeal review period. Wish us luck! It's a little crazy, because what if there was some critical ring 0 RCE vuln that was being exploited in the wild and that needed to be patched immediately? (Just hypothetical; there isn't.) In that case, telling users "sorry, you've got to wait 60 days" would be sort of bad. And users of WireGuard for Windows are also Microsoft Windows users, so I can't see how this is good for Microsoft either. I think it must just be a case of bureaucracy gone slightly off the rails. Happens. If any Microsofters are able to make this take not-sixty-days, please do get in touch.

WireGuard is sunsetting support for old Windows versions: lists.zx2c4.com/pipermail/wi…

vDSO getrandom() objective complete!

Direct APK downloads for WireGuard for Android are now available: lore.kernel.org/wireguard/ZG…

WireGuard is the first reproducible build package on F-Droid that has a fully verified signature path. The WireGuard Project builds WireGuard from source, and then signs the resultant APK with a private key stored in an HSM. F-Droid’s build server downloads that source and does the same build process. Then, F-Droid downloads the APK that the WireGuard Project built, makes sure it matches the APK that it build itself, and then, critically, *makes sure that the APK is signed with the WireGuard Project’s HSM-resident signing key.* Other reproducible packages on F-Droid don’t have this final signature checking step, which means there’s a problem if the upstream developer's git repo and download server are serving up malicious source and binaries, two things that often live on the same server or GitHub account. (And F-Droid doesn’t have the ability to check git tag signatures.) So, barring other issues, the APK that F-Droid puts on their server for users to download is verified to be the same one from the WireGuard Project built. A nice consequence of this week’s Android reproducible builds announcement: xitter.cf/EdgeSecurity/sta…

Also wrote up some @Yubico #YubiHSM 2 tidbits in github.com/Yubico/yubihsm-sh… in case it's useful for other projects in the future.