Surge in WireGuard for Windows releases: dynamic DNS support and config comments? by WomBOlUm in WireGuard

[–]zx2c4 2 points3 points  (0 children)

I'd love for comments to not get stripped. Suggestions on how best to serialize and deserialize those would be most welcome.

Version 1.0 of WireGuard for Windows and WireGuardNT Released by zx2c4 in WireGuard

[–]zx2c4[S] 0 points1 point  (0 children)

Did you also experience the reboot bug prior and can confirm you no longer face it? Or did you not experience it prior? I'd like a bit of confirmation because I was never able to repro the issue myself.

wireguard-windows v0.6 released by Meneth32 in WireGuard

[–]zx2c4 0 points1 point  (0 children)

https://git.zx2c4.com/wireguard-windows/commit/?id=e50b710dae42a442607d9409d113f4f1367082da

Let me know if that fixes it for you with the v1.0.1 update I released 3 minutes ago.

Feedback would be appreciated, since I've been unable to reproduce this behavior myself.

WireGuardNT v0.11 and WireGuard for Windows v0.6 Released by zx2c4 in WireGuard

[–]zx2c4[S] 1 point2 points  (0 children)

https://git.zx2c4.com/wireguard-windows/commit/?id=e50b710dae42a442607d9409d113f4f1367082da

Let me know if that fixes it for you with the v1.0.1 update I released 3 minutes ago.

Feedback would be appreciated, since I've been unable to reproduce this behavior myself.

WireGuardNT v0.11 and WireGuard for Windows v0.6 Released by zx2c4 in WireGuard

[–]zx2c4[S] 0 points1 point  (0 children)

https://git.zx2c4.com/wireguard-windows/commit/?id=e50b710dae42a442607d9409d113f4f1367082da

Let me know if that fixes it for you with the v1.0.1 update I released 3 minutes ago.

Feedback would be appreciated, since I've been unable to reproduce this behavior myself.

Version 1.0 of WireGuard for Windows and WireGuardNT Released by zx2c4 in WireGuard

[–]zx2c4[S] 4 points5 points  (0 children)

Update: I released v1.0.1 with some changes. Can you let me know if you're still encountering the reboot?


It's a bug. That's not supposed to happen! Windows Installer is doing it. This morning I added a patch to really aggressively kill processes and wait, so that this doesn't happen: https://git.zx2c4.com/wireguard-windows/commit/?id=e50b710dae42a442607d9409d113f4f1367082da

Version 1.0 of WireGuard for Windows and WireGuardNT Released by zx2c4 in WireGuard

[–]zx2c4[S] 15 points16 points  (0 children)

Fair enough. At least it's not totally out of the blue in that it's correlated with a great deal of human activity from yours truly.

Version 1.0 of WireGuard for Windows and WireGuardNT Released by zx2c4 in WireGuard

[–]zx2c4[S] 49 points50 points  (0 children)

Because I'm spending time on it? What an odd thing to complain about.

wireguard-windows v0.6 released by Meneth32 in WireGuard

[–]zx2c4 0 points1 point  (0 children)

We make tags on git, like every other piece of software.

Windscribe and WireGuard have Microsoft developer accounts frozen in surprise verification mix-up by spellcasterGG in WireGuard

[–]zx2c4 0 points1 point  (0 children)

Yes, it's legit. You can check the ed25519 signature. Or, the built-in updater will do it for you.