Hot answers tagged hardware
Can This be done? I would say yes, but with some caveats. Depending on the cable and the data, you would need some very expensive / sensitive equipment to pull this off. To me this is a similar issue to the old Van Eck Phreaking (http://en.wikipedia.org/wiki/Van_Eck_phreaking). Intel has some tech to circumvent this kind of attack: ...
One solution is to require all firmware to be signed and have the device check the signature before writing that firmware image to its memory; my current laptop has an option to enable this in its BIOS (the option is permanent - if I enable it now I can't disable it anymore, that's why I didn't enable it). There are many drawbacks however : induces a ...
This is a great question! Never thought about this until you asked. Firstly, code running inside a secure enclave runs in ring 3. So all restrictions that apply to untrusted non enclave ring 3 code apply. So an enclave cannot write to MSR's. Next, the specs don't explicitly mention anything about MSR's but it does tell you about interaction with IA32 ...
Intel Q35 from your link is Intel AMT 3, it's last version of AMT which had some problems with "hack-methods". AMT4+ didn't hack, AMT6+ have even more security. If you are afraid of Intel AMT/ME, you can disable it in your BIOS or MEBx. But you must remember that all modern systems are constructed to use Intel ME by default.
Only top voted, non community-wiki answers of a minimum length are eligible