You must log in or # to comment.
Microsoft is the absolute worst. I had to deal with them for a job once, we really really needed something from them and they ignored us. Eventually though they needed something from us, so I got on the horn with them and told them I’d help them with their thing if they helped us with ours. They agreed immediately. So I helped them.
And then they went back to ignoring us like nothing. Never even made a tiny attempt to hold up their end of the deal.
It sucks ass how there are many ways in which folks are forced to work with them. They’re fucking awful to work with.
Guessing a zero day exploit by US interest is in use…
Apparently it’s all sorted now after a Microsoft employee reached out to the developer on social media, but it’s yet another example of the bullshit you have to put up with when dealing with them.
And that only because this guy was a high profile dev. If you’re a typical prole you’re never getting your account back lmao
People tagged Microsoft employees on Twitter. And support request on the Microsoft forums still remain unanswered.
he has been locked out of his Microsoft developer account, and as a result cannot sign drivers or ship updates for WireGuard for Windows users
Windows users, specifically. Doesn’t sound like this is impacting the WireGuard codebase in general.
Somewhat telling that all the affected devs mentioned are security-related tho.
it’s funny that the damage is 100% isolated to windows loyalists and scavengers on the prowl for their last straw to leave.
Somewhat telling that all the affected devs mentioned are security-related tho.
For what’s is worth, it’s about signing stuff like device drivers. Fewer indivual/community projects that need that.
How convenient…