Am I missing something or is this the same TPM bus sniffing for the key exchange attack (from @marcan maybe?) that was detailed some years back but using a cheap Pi? Is this attack BitLocker specific somehow? It looks like it would affect LUKS or others just as well. Just trying to understand the novelty of this particular method or if it's tied to BitLocker in particular.<p>Anyway, not to detract from the nice work of the author or to tout my own horn but I can hack a lot of encryptions in seconds with a simple keylogger. For the sake of this exercise I'll consider the key exchange (user typing password) is an integral part of any encryption scheme :).<p>More seriously, I think fTPM or TPM+PIN+USB key would be good ways to avoid this scenario.
This particular bus sniffing attack is easily prevented... it's just that Microsoft _chose_ to avoid implementing the protection.<p>Mission critical embedded devices are not designed by Microsoft, and would normally have tpm parameter encryption...<p><a href="https://security.stackexchange.com/questions/253776/why-does-windows-not-enable-tpm-2-0-parameter-encryption-to-protect-against-bus" rel="nofollow">https://security.stackexchange.com/questions/253776/why-does...</a>
Remember when Microsoft told you you can't have Windows 11 because of your missing/old TPM wouldn't be secure enough?<p>Turns out it's all security theater.
I'm not familiar at all with this kind of low-level knowledge so probably a stupid question but: does that require the device to be connected when the user types their password to actually retrieve the key, or is it an actual "crack" as in it can unlock BitLocker without key nor password ever being inputted on the device?
TFA:
> If your hardware is vulnerable, mitigation can be achieved through the use of a PIN.<p>Or, encryption passphrase on boot.<p>But in that case, you just need two accesses: Add h/w keylogger, read h/w keylogger.<p>You can at least make it somewhat more difficult by using ubsguard to prevent the most obvious keylogger ingress points.
Impressive technical feat, even if not completely new.<p>However, as tech people we need to stop downplaying our accomplishments. “43 seconds” (plus the lifetime of learning that allowed them to figure out how to do all these things: decoding the wire signals, writing a custom firmware, knowing how to probe the motherboard for the correct signals, etc.)