Linux is the only hope at this point for the future of computing. Windows and macOS are just too risky to do any business with. Waste of all resources.
and yet... still unusable by the mass majority of people.
Microsoft terminated the account VeraCrypt used to sign Windows drivers
151–160 of 526 posts
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#152Never was, isn't and I guess won't be.
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#153Linux is the only hope at this point for the future of computing. Windows and macOS are just too risky to do any business with. Waste of all resources.
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#154Earlier quoted context omitted.
But making money at the expense of people is not a Tinfoil conspiracy - it's a factual statement.
It is also a factual statement, that tinfoil shields (somewhat) from electromagnetic radiation.
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#155Earlier quoted context omitted.
Now this is even more alarming! Wireguard's creator has their Microsoft account suspended... 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!
> Microsoft doesn't want to allow software that would allow the user to shield themselves I don't think Microsoft cares (about anything besides making mo' money), but there are plenty of (state) actors that can influence the decision-making at Microsoft when it comes to these issues. No tinfoil needed.
If Microsoft amounts to a sentient entity (i.e. is able to care about things), we have a bigger problem.
If we put the wall of metaphor between us and that interpretation, it still remains likely that "users shielding themselves" is of primary concern to Microsoft's bottom line.
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#156Any chance this is the issue? https://techcommunity.microsoft.com/blog/windows-itpro-blog/...
From TFA: "I have encountered some challenges but the most serious one is that Microsoft terminated the account I have used for years to sign Windows drivers and the bootloader."
My guess was that he got caught up in some house-cleaning. My theory being that he's still signing his code the way malware authors also do and got flagged by some automated review that's meant to force him to go get WHCP certified or whatever the new route is.
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#157This 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 f…
Honestly, anyone still using Windows probably deserves it.
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#158Earlier quoted context omitted.
It's not forced, especially for normal software, you just get a popup. It's a bit of a pain to disable the requirement for drivers, though.
I don't think you can install VeraCrypt, at least for system encryption, unless the installer is signed
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#159Earlier quoted context omitted.
We can still install, right? It just comes up with a scary warning. Still not great but at least we aren't locked out.
You can, but it's more than a warning. VeraCrypt has a signed kernel driver, which has higher requirements. You'll need to boot into a special Windows mode and disable Driver Signature Enforcement.
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#160Earlier quoted context omitted.
There's more to it. Signed desktop software can be signed by any CA. Veracrypt has kernel drivers. Microsoft's ability to control what you can sign is specific to kernel drivers, and Microsoft's trigger finger around bans exists in the world where bad drivers BSOD machines. In general this isn't your problem.
Speculation as well and highly unlikely. Microsoft drivers can very well BSOD your machine as well, not a significant or convincing threat scenario and certainly not something that lead to certificate revocation of driver developers. There is zero quality control or review by Microsoft here. Not for their own products and not for third party ones.