Microsoft's Digital Leash: Why Centralized Key Control Threatens User Sovereignty Against Apple's True Encryption
Microsoft's control over encryption keys, particularly through BitLocker, is criticized for creating backdoors accessible via centralized services and mandatory account access.
Commenters split sharply on workarounds. Some point to local, non-Microsoft-account setups as 'technically safe for now' (neukenindekeuken). Others counter that Microsoft's infrastructure, especially within Azure, grants them visibility regardless of setup (SpikesOtherDog). The core technical critique comes from 'phil,' who insists Apple's true end-to-end encryption means keys stay only with the end-user, unlike BitLocker's centralized keys.
The prevailing sentiment targets Microsoft's behavior: accusations that the company engages in 'perfectly legitimate business behavior' by blocking open-source tools like VeraCrypt through mandatory signing, thereby eroding trust regardless of the technical safeguards implemented.
Key Points
Centralized key management diminishes privacy.
Users argue that Microsoft’s control over BitLocker keys is inherently risky compared to user-held keys, as stated by 'phil'.
Local setups offer temporary relief from mandatory linking.
'neukenindekeuken' noted that local, non-Microsoft-account setups are 'technically safe for now,' but 'SpikesOtherDog' pointed out Microsoft's persistent infrastructure reach.
Apple's model is cited as the gold standard for privacy.
'phil' established that Apple uses true E2EE where only the end-user possesses the keys, a key differentiator from BitLocker.
Microsoft allegedly suppresses open-source encryption alternatives.
'floofloof' accused Microsoft of blocking tools like VeraCrypt while bundling competing products, characterizing the action as 'perfectly legitimate business behavior'.
Linux/LUKS offers a non-Microsoft ecosystem alternative.
'BassTurd' promoted LUKS as a functional alternative because Linux bypasses Microsoft's key infrastructure entirely.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.