Edge Security

Tweets from @zx2c4. Security Research & Consulting. Support WireGuard development via . Or hire us.

[Edge Security @EdgeSecurity]

@copenseethen @phoronix https://t.co/jChkVKZqoN Let me know if that fixes it for you with the v1.0.1 update I released 3 minutes ago.

[Phoronix @phoronix]

WireGuard For Windows Reaches v1.0

https://t.co/KGi3Wp3l8z

[Edge Security @EdgeSecurity]

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: https://t.co/AsbgTMm4Z7

[Edge Security @EdgeSecurity]

@KiPos_info https://t.co/knts99zd0F
https://t.co/1hVbMsqEZd

[Edge Security @EdgeSecurity]

WireGuardNT v0.11 and WireGuard for Windows v0.6 have been released: https://t.co/frTtoylDU4

[Edge Security @EdgeSecurity]

@TechCrunch Microsoft resolved the issue, and now a new version has been released: https://t.co/52vXdhQ3hS

[Edge Security @EdgeSecurity]

WireGuardNT v0.11 and WireGuard for Windows v0.6 have been released: https://t.co/frTtoylDU4

[Edge Security @EdgeSecurity]

@TheRegister Microsoft resolved the issue, and now a new version has been released: https://t.co/52vXdhQ3hS

[Edge Security @EdgeSecurity]

WireGuardNT v0.11 and WireGuard for Windows v0.6 have been released: https://t.co/frTtoylDU4

[Edge Security @EdgeSecurity]

@PCMag Microsoft resolved the issue, and now a new version has been released: https://t.co/52vXdhQ3hS

[Edge Security @EdgeSecurity]

WireGuardNT v0.11 and WireGuard for Windows v0.6 have been released: https://t.co/frTtoylDU4

[Edge Security @EdgeSecurity]

@Cybernews Microsoft resolved the issue, and now a new version has been released: https://t.co/52vXdhQ3hS

[Edge Security @EdgeSecurity]

WireGuardNT v0.11 and WireGuard for Windows v0.6 have been released: https://t.co/frTtoylDU4

[Edge Security @EdgeSecurity]

@AlternativeTo Microsoft resolved the issue, and now a new version has been released: https://t.co/52vXdhQ3hS

[Edge Security @EdgeSecurity]

WireGuardNT v0.11 and WireGuard for Windows v0.6 have been released: https://t.co/frTtoylDU4

[Edge Security @EdgeSecurity]

You can download the fetcher installer from https://t.co/bfD9gbG8HC, 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`.

[Edge Security @EdgeSecurity]

All sorted now. WireGuardNT 0.11 will be released soon, with a new WireGuard for Windows out after some testing. Thank you to @shanselman for helping.

[Edge Security @EdgeSecurity]

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.

[Edge Security @EdgeSecurity]

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.

[Edge Security @EdgeSecurity]

WireGuard is sunsetting support for old Windows versions: https://t.co/6RX2CRlXtc

[Edge Security @EdgeSecurity]

vDSO getrandom() objective complete!

[Phoronix @phoronix]

The @gnutools GNU C Library Merges Support for getrandom vDSO

https://t.co/90v3a1jKej

[Edge Security @EdgeSecurity]

Glibc 2.41 will support vDSO getrandom(): https://t.co/Er6FTXJ2Yo

[Phoronix @phoronix]

Golang Now Enables Speedier getrandom() On Linux

https://t.co/C88cOe8H5g

[Edge Security @EdgeSecurity]

Golang now supports vDSO getrandom() for huge speedups: https://t.co/QIul56QHuG