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

101–110 of 175 posts

Re: WireGuard makes new Windows release following Microsoft signing resolution

#101

Post by walrus01 »

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…

The broader general problem is that it should not be necessary to attempt amplification of a message via HN or X or other platforms to get a company to have a real human pay attention to something, and write a hand crafted response.

This seems to increasingly be the norm with people who have had their accounts locked, deleted or restricted by automated systems. You have to hope that you can write a message and get it amplified via some sort of platform read by hundreds of thousands of people, and get people to reshare your message, in order to get any form of traction.

If you're not somebody well known, noteworthy or somehow significant in a community your likelihood of having your message successfully amplified is much lower.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#102

Post by walrus01 »

SturgeonsLaw wrote: post #62
sammy2255 wrote: post #23

Earlier quoted context omitted.

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

I understand it's because it's a device driver, but why should a pure software publisher which has no hardware product of any sort be required to go through a "hardware program" gatekeeper of what binaries a person can choose to install and run on their own computer?

Re: WireGuard makes new Windows release following Microsoft signing resolution

#103

Post by rstupek »

walrus01 wrote: post #102
SturgeonsLaw wrote: post #62

Earlier quoted context omitted.

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

I understand it's because it's a device driver, but why should a pure software publisher which has no hardware product of any sort be required to go through a "hardware program" gatekeeper of what binaries a person can choose to install and run on their own computer?

They started it because the drivers people used to use from hardware vendors would routinely blue screen windows, which made MS look like the reason windows would crash. Hardware vendors are notoriously inept at software.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#104

Post by aaronmdjones »

looneysquash wrote: post #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!

> and had to go through the normal process?

There is no normal process. The error message clearly states "There are no appeals available, we have closed your application".

If the company makes it impossible for you to communicate with them, the only recourse is to draw public attention to it in order to shame them. This only works if you can gather enough public support and kick up enough of a stink about it. All of the small developers still locked out of their accounts are screwed.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#105

Post by VertanaNinjai »

rstupek wrote: post #103
walrus01 wrote: post #102

Earlier quoted context omitted.

I understand it's because it's a device driver, but why should a pure software publisher which has no hardware product of any sort be required to go through a "hardware program" gatekeeper of what binaries a person can choose to install and run on their own computer?

They started it because the drivers people used to use from hardware vendors would routinely blue screen windows, which made MS look like the reason windows would crash. Hardware vendors are notoriously inept at software.

Í think their point was that Wireguard has no physical hardware, so it’s strange as a software project they’d be forced to go through verification for a hardware program.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#106

Post by rlpb »

walrus01 wrote: post #102
SturgeonsLaw wrote: post #62

Earlier quoted context omitted.

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

I understand it's because it's a device driver, but why should a pure software publisher which has no hardware product of any sort be required to go through a "hardware program" gatekeeper of what binaries a person can choose to install and run on their own computer?

It sounds more like a "driver program" gatekeeper so you are arguing about semantics. I'm not claiming that there is no problem, just that an argument based on the distinction between "hardware" and "driver" is void.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#107

Post by technion »

walrus01 wrote: post #102
SturgeonsLaw wrote: post #62

Earlier quoted context omitted.

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

I understand it's because it's a device driver, but why should a pure software publisher which has no hardware product of any sort be required to go through a "hardware program" gatekeeper of what binaries a person can choose to install and run on their own computer?

Outside of these unfortunuate situations, a lot of people are quite happy for developers of eg kernel anti cheat to have a difficult time.

We do need to recognise, a long history of "windows always bluescreens" was somewhat reigned in by this policy with a lot of crashes coming down to third party drivers.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#108

Post by pixl97 »

elcritch wrote: post #100
sillysaurusx wrote: post #67

Earlier quoted context omitted.

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 miracl…

It makes me think tech communities need to lobby for more laws to ensure fair access to platforms, app stores, etc. Be that at least side loading apps, etc. Otherwise we’ll eventually all get lost in the kafkaesque technocracies. Less for moral reading, but to keep from being squashed by the weight of tech.

>tech communities need to lobby for more laws to ensure fair access to platforms

I'm surprised someone didn't reply saying this would affect the freedom of companies to do whatever they want, whenever they want.

Re: WireGuard makes new Windows release following Microsoft signing resolution

#109

Post by nine_k »

VertanaNinjai wrote: post #105
rstupek wrote: post #103

Earlier quoted context omitted.

They started it because the drivers people used to use from hardware vendors would routinely blue screen windows, which made MS look like the reason windows would crash. Hardware vendors are notoriously inept at software.

Í think their point was that Wireguard has no physical hardware, so it’s strange as a software project they’d be forced to go through verification for a hardware program.

Because it's a kernel driver anyway?

Re: WireGuard makes new Windows release following Microsoft signing resolution

#110

Post by [deleted] »

walrus01 wrote: post #102
SturgeonsLaw wrote: post #62

Earlier quoted context omitted.

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

I understand it's because it's a device driver, but why should a pure software publisher which has no hardware product of any sort be required to go through a "hardware program" gatekeeper of what binaries a person can choose to install and run on their own computer?

[deleted]
Post reply on HN