3 ms·
> meant to address a vulnerability that allowed attackers to bypass BitLocker encryption by using the Windows Recovery Environment (WinRE). How can you screw u
by dijit 3y ago
> meant to address a vulnerability that allowed attackers to bypass BitLocker encryption by using the Windows Recovery Environment (WinRE).
How can you screw up so badly that you even have the ability to bypass the entire reason for a security feature existing?
Sorry to be mean to Microsoft, I am certain there's usability reasons for this, but sincerely: principle of least surprise please.
I'd be incredibly surprised if Linux kept a copy of my unlock keys around somewhere that were available to anyone except me. That is a truly monumental fuck-up.
- smileybarry 3y agoIt's possible partly by the user shotgunning their own foot. WinRE gets auto-decrypt access to your drive because upon setting up BitLocker, the user chose "automatically unlock this drive on startup" instead of a PIN unlock. (Which then utilizes the TPM to auto-unlock so it's not like your keys are on the storage device directly) If you use any non-auto unlock -- PIN, passphrase, network -- then WinRE can't magically access your data and needs that code to then retrieve a key from the TPM.
- dist-epoch 3y ago> I'd be incredibly surprised if Linux kept a copy of my unlock keys around somewhere that were available to anyone except me You can set it up to auto unlock: https://devicetests.com/decrypting-luks-encrypted-filesystem-ubuntu https://devicetests.com/decrypting-luks-encrypted-filesystem...