Microsoft Locks Developers: WireGuard Updates Stalled as Privacy Tools Face Windows Blackout
Jason Donenfeld explicitly stated he was locked out of his Microsoft developer account, citing this as the direct reason WireGuard cannot push necessary Windows driver updates.
Opinions are sharply divided on the crisis's severity. While some focus entirely on the alleged Microsoft lockout as the root cause, others, like Davel23, argue that fixes exist elsewhere, specifically referencing resolution paths for VeraCrypt. Furthermore, users like microcapybara dismiss the outcry by pointing to a trend toward Linux adoption among power users.
The prevailing belief centers on a developer-access choke point: Microsoft's controls are allegedly crippling essential open-source software on the Windows platform. The core fault line exists between those demanding immediate fixes for locked accounts and those who believe the community should adapt to platform shifts.
Key Points
Microsoft restricted access is stopping WireGuard's Windows updates.
Sepia reported Donenfeld's specific lockout of his Microsoft developer account.
The lockout problem isn't exclusive to WireGuard.
rbn noted that a similar account issue reportedly affected VeraCrypt.
The VeraCrypt issue might already have a workaround.
Davel23 provided a link suggesting an alternative resolution path exists for VeraCrypt.
The crisis misses the point of user migration.
microcapybara suggested the most impacted users are already the 'easier Linux converts,' minimizing the perceived severity.
Windows users might be unwilling or unable to switch OS.
fuckwit_mcbumcrumble stated that WireGuard's Windows user base might simply prefer staying on the platform despite the difficulties.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.