Live data from Hacker News

WireGuard makes new Windows release following Microsoft signing resolution

lists.zx2c4.com

61–70 of 175 posts

Re: WireGuard makes new Windows release following Microsoft signing resolution

#61
post #6

Earlier quoted context omitted.

Conspiracy 1: rules from on-high about encryption projects to be suppressed. Debunked. Conspiracy 2: Copilot all the things! Probably not too far off.

i think they have explicitly made it clear that they want to copilot all of the things (unfortunately), so i dont quite file it under the conspiracy label.

If it's not a conspiracy (and to be clear, I don't think it is one) its still a failure on multiple levels of the organisation

We can probably blame copilot for the email about new verification reqirements not going out to everyone. Maybe even for the reports of people who jumped through all the hoops and still got blocked as if they hadn't. But rolling out new verification reqirements, then not monitoring how many developers fulfill your new reqirements and following up is entirely on Microsoft employees. That's management failure and disregard for developers on their platform

Re: WireGuard makes new Windows release following Microsoft signing resolution

#62
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…

Good to know everything was resolved, but did you ever find out why your signing account was suspended? That's not something you brush off as haha silly Microsoft..

Microsoft are saying it's because those accounts didn't undergo verification for the Windows Hardware Program

https://www.theregister.com/2026/04/09/microsoft_dev_account...

Re: WireGuard makes new Windows release following Microsoft signing resolution

#63

Earlier quoted context omitted.

All this doesn't matter. What matters is the destructive potential and a breach of trust. CAs have been distrusted for less.

> CAs have been distrusted for less. root programs are super specific about root cause analysis, what actions lead up to distrust, differentiating deliberate maliciousness from systemic incompetence, etc. its like the exact opposite of "all this doesnt matter". of course they still look at the outcome (danger to users, etc.), typically as a first step. but they take great care to determine exactly what lead up to a s…

It really depends on the scale of the breach, for example DigiNotar was immediately killed for their gross incompetence. In this case even the scale is unclear, with heavy suspicion towards malice and little hope on fixing any process inside that monstrous bureaucracy or even making it meaningfully care if it's not. I see no reason to trust Microsoft anymore, regardless of it being a fuckup or malice.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#64
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.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#65
post #16

Earlier quoted context omitted.

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…

Microsoft's incompetence is certainly reckless at a minimum, and often manifests in ways that come across as misanthropic toward their users. They don't really fit the pattern of mere bumbling fools.

what about pattern of bumbling fools on crack ?

Re: WireGuard makes new Windows release following Microsoft signing resolution

#66

Earlier quoted context omitted.

What has LibreOffice got to do with any of this?

MS has a history of fucking up LibreOffice installs. https://wiki.documentfoundation.org/Faq/General/General_Inst...

I am sure this is by accident, MS would never try to discourage users from installing free alternatives to their offerings.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#67
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…

They would be ignored. Having an audience is key to getting problems solved, whether it’s a lone hacker or a large corporation. Without an audience, you have no leverage. At that point you might as well create a new Windows account and re-apply, since that would have more luck than getting around a “we’ve closed your account and there’s no appeal process” barrier.

If that sounds Kafkaesque, it is. It’s a small miracle that getting a post to the top of HN can surmount such bureaucracy at all.

The best way to get an audience is to tell a compelling story. Make it interesting. There are ways of doing that for even the least known developers.

My point is to push back against the idea that it should be fair to everyone and that what’s morally right should prevail in every case. The hardware developer program doesn’t exist to treat every developer fairly. They exist to make money for Microsoft. pg puts it more eloquently here: https://paulgraham.com/judgement.html

Re: WireGuard makes new Windows release following Microsoft signing resolution

#69
But what would have happened if they weren't able to get Microsoft's attention through an outside channel (this site) and had to go through the normal process?

I'm glad it was resolved quickly for WireGuard, but I'm concerned the results won't generalize.

Also, thanks for WireGuard!

Re: WireGuard makes new Windows release following Microsoft signing resolution

#70
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…

I really appreciate what you wrote in that post re: dropping support for pre-Windows 10 operating systems.
Post reply on HN