Can someone please explain the implications for current Windows users of VeraCrypt?
Microsoft terminated the account VeraCrypt used to sign Windows drivers
131–140 of 526 posts
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#132Anyone here who could reach out to specific persons inside Microsoft who could fix this?
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#133This 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…
I am astounded that the maintainer and inventor of Wireguard is in this position. Microsoft even supports Wireguard in Azure Kubernetes Service.
Is this another example of their old modus operandi:
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
?
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#134Jesus, sourceforge is still on the go?
I understand that most people want to move to other more modern tools, it's up to you. However, what baffled me is why the author's choice not to move is a problem? Did we pay them to move and they did not move as promised? Was there some crowd funding to move that was not fulfilled?
> what baffled me is why the author's choice not to move is a problem?
Because Sourceforge is horrible to use and was at one point actively pushing malware? It's pretty obvious tbh.
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#135Microsoft disabled the developer's certificate so no windows releases can be made.
As someone who is just planning to publish signed desktop software for Windows, this is deeply worrying. What reasons could there be for cancelling a certificate, especially when it has been used for years and the identity is already established? Are there some ways to combat such decisions legally?
You just have to start living like they do in Russia and comply in advance. Don't do anything "interesting", no encryption, or if you do, make sure you leave breadcrumbs, scratch that, a bread trail for them to easily get access to customer data. An Oracle or Sharepoint integration maybe?
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#136This 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…
Has your Apple account been suspended for the last few years?
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#137This 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…
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!
"Never attribute to malice that which is adequately explained by stupidity"
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#138This 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…
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!
Alternatively they asked copilot to scan for crypto projects and ban them
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#139This 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…
[flagged]
What are you basing your remark here on?
Re: Microsoft terminated the account VeraCrypt used to sign Windows drivers
#140Earlier quoted context omitted.
likely chose to shut down rather than bend over, same as Lavabit a year prior. I find it more plausible than the other theory.
I went on a Wikipedia dive and discovered this funny bit regarding the court process surrounding Lavabit and FBI's desire of the TLS private keys. > The contempt of court was caused by Levison providing the keys printed in a tiny (4 point) font, which was deemed "largely illegible" by an FBI motion, which went on to complain that "To make use of these keys, the FBI would have to manually input all 2560 characters, an…
> The court ordered Levison to be fined $5,000 a day beginning 6 August until he handed over electronic copies of the keys. Two days later Levison handed over the keys hours after he shuttered Lavabit.