3 ms·
Agree. Single point of failure. One developer, one account. Crazy.
by nelox 6mo ago
Agree. Single point of failure. One developer, one account. Crazy.
- ptx 6mo agoHaving multiple accounts wouldn't help, as Microsoft could easily suspend all the accounts of everyone associated with the project if any account looks suspicious. The single point of failure is Microsoft.
- jamesnorden 6mo agoHow would more than one account help in this scenario, exactly?
- hirako2000 6mo agoAny account can sign any (same) piece of software. Of course Microsoft could detect the it's signing a software related to a banned signed and ban the new account. So veracrypt (and wireguard) is stuck. It's outrageous. MS is simply enforcing some Government crackdown on encryption software that would interfere with backdoors.
- raxxorraxor 6mo agoNo, that is not the issue here. The source of the problem is something different. This is a wrong root cause analysis.
- pjc50 6mo agoYou're not actually allowed to avoid this by having multiple accounts, that falls under "ban evasion". But yes, there's a lot of critical single maintainer projects.