Hacker News new | past | comments | ask | show | jobs | submit
zx2c4 | on: Veracrypt project update
This is the same problem I'm currently facing with WireGuard. No warning at all, no notification. One day I sign in to publish an update, and yikes, account suspended. Currently undergoing some sort of 60 days appeals process, but who knows. That's kind of crazy: what if there were some critical RCE in WireGuard, being exploited in the wild, and I needed to update users immediately? (That's just hypothetical; don't freak out!) In that case, Microsoft would have my hands entirely tied.

If anybody within Microsoft is able to do something, please contact me -- jason at zx2c4 dot com.

onehair | parent | next
Now this is even more alarming! Wireguard's creator has their Microsoft account suspended...

<Tin foil hat on> Microsoft doesn't want to allow software that would allow the user to shield themselves, either by totally encrypting a drive, or by encrypting their network traffic! </Tin foil hat on>

loading story #47688075
ngetchell | root | parent
Or more likely, some automated security system flagged popular but suspicious apps for further review.
Gigachad | root | parent | next
Automated systems breaking things without any human contact to get them resolved seems to be the theme of the last 10 years.
loading story #47688636
loading story #47688261
teruakohatu | parent | next
I am astounded that the maintainer and inventor of Wireguard is in this position.

Microsoft even supports Wireguard in Azure Kubernetes Service.

loading story #47688221
loading story #47688280
loading story #47689228
loading story #47689056
jchw | parent | next
I tried to set up a partner account for driver signing last year (as a business entity) and it already seemed basically impossible. I think they're getting ready to just simply not allow it at all.

This is stupid. If Microsoft wants people to stop writing kernel drivers, that's potentially doable (we just need sufficient user mode driver equivalents...) but not doing that and also shortening the list of who can sign kernel drivers down to some elite group of grandfathered companies and individuals is the worst possible outcome.

But at this point I almost wish they didn't fix it, just to drive home the point harder to users how little they really own their computer and OS anymore.

gib444 | parent | next
Y'all need to form an alliance or something, get some press coverage (wireguard, veracrypt, libreoffice)
loading story #47688052
loading story #47689030
loading story #47688269