You must log in or # to comment.
I’ll say it; this is why age verification/developer verification is rubbish.
Well, it’s one reason it’s rubbish anyhow.
“We’ve been trying to resolve this for over a month, and getting nowhere. Support is non-existent,” Windscribe said in its post. “Anyone know a human with a brain that still works at Microsoft and can help?”
Microslop. The word is Microslop, for reasons you have just experienced first-hand.
I did a doubletake because I read the article like 12 hours ago about VeraCrypt’s dev getting locked out of their MS account, then could have sworn it wasn’t Wireguard that was affected.
they’re both software that’s can be used to protect against government surveillance
Two bits of security software.
Makes me wonder if there’s been a concerted effort to hack these accounts, and some automated security process has locked them out.
Or maybe it’s the governments dislike of VPNs being used to bypass surveillance
The article mentions wireguard having similar issues, so there are probably lots of articles for each case
deleted by creator
Windows is making a move to destroy my favorite type of tunnel. The only problem with that Macroslop is that I don’t use them on windows machines at all. FreeBSD and Linux sure but the only thing a windows machine is good for is to be a shitty server or a workstation for those who wont learn something new.
Another reason to never use anything bigtech.
Then stop pushing updates to Windows?
Donenfeld, the WireGuard developer, told TechCrunch in an email: “If there were a critical vulnerability to fix right now — there isn’t! I just mean hypothetically — then users would be totally exposed.”
Well, the Windows users would. I assume that they’d still release builds for the other platforms.
I wonder if it’s a coincidence that this happened right as Anthropic launched their new private LLM to find security vulnerabilities in software.
Looking at the licensing of WireGuard VPN holds the answer to the way MicroSlop prioritized this:
The kernel components are released under the GPLv2, as is the Linux kernel itself. Other projects are licensed under MIT, BSD, Apache 2.0, or GPL, depending on context.
Nire reason to move to codeberg then. Probably should’ve done it sooner.
This wouldn’t fix the issue. Drivers need to be signed, otherwise they won’t run on Windows. Only Microsoft can sign them, it’s got nothing to do with where the code is stored. They simply can’t ship unsigned software.
It’s like you neither read the article, nor do you understand how software works.
But otherwise I agree, fuck Microsoft and GitHub.
I believe the issue is because both VeraCrypt and Wireguard use kernal level drivers which can’t run without signing, though they can be bypassed but that isn’t good for security.
https://learn.microsoft.com/en-us/windows-hardware/drivers/install/windows-driver-signing-tutorial
Microsoft doesn’t believe in good security. That is why the gatekeep like this.
It’s like you neither read the article, nor do you understand how software works.
That’s a bit of a reach.
Yup, this is on him. Ignoring the warning signs for all those years, especially this last half year, has come back to haunt him.