Anyway, if you rely on BitLocker in TPM mode (boot without PIN), you should know that anyone can steal your computer, sniff 32 bytes off of the LPC bus, stick them into libbde, and decrypt your disk. Yes, it's that easy. Solder 7 wires to $favorite_fpga_board, decrypt drive.
-
Show this thread
-
We all knew it was going to be this dumb, but today I'm here to tell you it *is* this dumb and I just implemented it.
4 replies 29 retweets 139 likesShow this thread -
Replying to @marcan42 @mjos_crypto
Great work! Do you think a similar attack could be made against Android "DE" storage on a Pixel phone?
1 reply 0 retweets 0 likes -
Replying to @ciphergoth @mjos_crypto
ARM devices are usually a few orders of magnitude closer to being potentially secure than x86 systems. The "TPM" on those is integrated into the SoC. I'm sure you could still find a way in though, like a glitching attack. This is why I refuse to use Android FBE.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @mjos_crypto
You prefer FDE to FBE? Because all storage is CE, none is DE? Would be interested to know more about the kind is attack you have in mind...
1 reply 0 retweets 0 likes -
Replying to @ciphergoth @mjos_crypto
Yes, except I use a different (much longer) FDE passphrase that is not my normal unlock code (this is possible on rooted devices). Also FDE encrypts *everything*, including all metadata, so I'm immune from "someone used the wrong data class" bugs.
2 replies 0 retweets 0 likes -
Replying to @marcan42 @mjos_crypto
Metadata is DE encrypted on the Pixel 3. I think reading DE data would be pretty hard on it, and reading CE (assuming eg a 6-digit random PIN) very very very hard.
1 reply 0 retweets 0 likes -
Replying to @ciphergoth @mjos_crypto
If you can compromise TrustZone then you can easily compromise both DE and CE. A 6-digit PIN provides ~zero cryptographic security, it all relies on the Keymaster implementation for both CE and DE.
1 reply 0 retweets 0 likes
I'm not saying it's easy, but I'm not betting the security of my data on someone having implemented a complet TrustZone stack securely, given what attempts I've seen so far. And that's not counting hardware attacks.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.