Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WireGuard makes new Windows release following Microsoft signing resolution

lists.zx2c4.com

Post reply on HN
Print view View original

71–80 of 175 posts

Re: WireGuard makes new Windows release following Microsoft signing resolution

#71

Post by zx2c4 »

e12e wrote: post #64
zx2c4 wrote: post #3

As I mentioned in the mailing list post, the Microsoft paperwork shuffling matter got dealt with rather quickly, following all the attention the HN thread from the other day got. And now we're finally out with an update! NT programming is a lot of fun, though this release was quite challenging, because of all of the toolchain updates. On the plus side, we got to remove pre-Win10 support -- https://lists.zx2c4.com/pip…

Somewhat on the side - but is there a wireguard that works well for ReactOS? Does the windows version just work fine? Just curious how/if the version support might work out for ReactOS.

Good question! I've never tried. The NT driver makes use of some of the more advanced features of the networking stack, so possibly not. But you never know. I'd love a Wg4React.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#72

Post by Aurornis »

There was a lot of speculation about this issue because readers assumed that WireGuard's was the only account that got locked. There was actually a wave of account locks that happened at the same time. If you only saw one of the headlines you might assume it was targeted or the result of some directed conspiracy, not the result of a widespread process.

Microsoft did a (very!) bad job of communicating what was happening, but The Register has more information:

> He explained that both deactivations were executed as part of the Windows Hardware Program's account verification procedures.

> The company published a blog in October, giving devs a two-week warning that if their accounts had not been verified since April 2024, Microsoft would issue mandatory account verification notifications.

> "We worked hard to make sure partners understood this was coming, from emails, banners, reminders," said Davuluri.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#73

Post by politelemon »

zx2c4 wrote: post #3

As I mentioned in the mailing list post, the Microsoft paperwork shuffling matter got dealt with rather quickly, following all the attention the HN thread from the other day got. And now we're finally out with an update! NT programming is a lot of fun, though this release was quite challenging, because of all of the toolchain updates. On the plus side, we got to remove pre-Win10 support -- https://lists.zx2c4.com/pip…

Your work is always appreciated.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#74

Post by NetMageSCW »

c0l0 wrote: post #12

As a wireguard user myself (even on the lone Windows machine that I still begrundingly have), I am happy that this problem could have been resolved. I am just wondering - if there had not been this kind of public outcry and outrage that Mr. Donenfeld discounts in his announcement message, would the issue have been fixed by now? What are individual developers of "lesser" (less important, less visible, less used) softw…

While this is a small problem for software (and hardware) that needs custom kernel drivers, or software that needs to run as administrator, you seem to have jumped a long way past that to rant about FOSS on Windows with no justification- general unsigned software works just fine on Windows as it always has.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#76

Post by izacus »

john_strinlai wrote: post #7
anonymous908213 wrote: post #4

Earlier quoted context omitted.

> incompetence is always more likely than malice. "Incompetence" of this degree is malice . It is actively malicious to create a system that automatically locks people out of their accounts with absolutely no possibility for human review or recourse short of getting traction in the media. "No sir, I didn't grind those orphans up. It was this orphan grinding machine I made that did it, teehee!"

i am positive that you understand the spirit of what that saying means. incompetence is always more likely than [intentional, directed] malice. microsoft employees did not deliberately attack the wireguard project with a goal of taking it down for whatever grand scheme people's hatred cooks up. if you have evidence that microsoft did this deliberately to ruin the wireguard project, please forward it along to jason (t…

Except that the system that removes culpability, visibility and consequences of this kind of abuse is set up deliberately to avoid liability and consequences of such actions.

This isn't a tee-hee accident, this is deliberate organizational design which removed any kind of bad consequences or even thought about what the software does to user from the engineers at Microsoft. They're happy about that. They now don't need to deal with that. And if you'll ask them, they will refuse a change that will make them responsible for abuse of their users.

So, to hell with them :)

Re: WireGuard makes new Windows release following Microsoft signing resolution

#78

Post by themafia »

john_strinlai wrote: post #2

> The comments that followed were a bit off the rails. There's no conspiracy here from Microsoft. But the Internet discussion wound up catching the attention of Microsoft, and a day later, the account was unblocked, and all was well. I think this is just a case of bureaucratic processes getting a bit out of hand, which Microsoft was able to easily remedy. I don't think there's been any malice or conspiracy or anythin…

Who needs conspiracy?

Microsoft has entitled itself to decide what I can and cannot run on the computer and OS that I paid for, this earns them no additional revenue, so they don't care to do a good job.

This system will never work properly.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#79

Post by redeeman »

and imagine for those guys that dont have the reach wireguard/veracrypt does.

NEVER trust microsoft, NEVER trust any mechanism people dont 100% control themselves. having to rely on microsoft to sign stuff is an abomination and something nobody should do

Re: WireGuard makes new Windows release following Microsoft signing resolution

#80

Post by EvanAnderson »

zx2c4 wrote: post #71
e12e wrote: post #64

Earlier quoted context omitted.

Somewhat on the side - but is there a wireguard that works well for ReactOS? Does the windows version just work fine? Just curious how/if the version support might work out for ReactOS.

Good question! I've never tried. The NT driver makes use of some of the more advanced features of the networking stack, so possibly not. But you never know. I'd love a Wg4React.

ReactOS was, at one time, targeting a Windows Server 2003-level of compatibility. With that in mind I can't imagine current Wireguard would have even a shred of hope of working on ReactOS.
Post reply on HN