heads VS tpm2-totp

I downloaded the VGA ROM for my Thinkpad W530 for both the Intel IGPU and Nvidia Quadro K1000M using this and configured the build config to use them with the correct PCI ports (8086,0166 10de,0ffc). Everything works fine except the output for both the VGA and the mini DP port. Does anyone have any ideas of what I could be missing here?

You may be interested in Heads, which is available on Purism laptops under the name PureBoot. Though this really needs a coreboot-capable machine, I think, and isn't something you can just add to your existing UEFI boot chain.

You don't need to encrypt anything to verify those images, you just need to sign them. See how Heads does this.

https://github.com/osresearch/heads

Unfortunately there is also the Heads secure firmware: https://osresearch.net/ as well. Otherwise my vote would go to Heads. Liive OS could be pretty hard to optimize in a search engine, they'll think it's misspelled. Could call it "Miles" and just never ack the reference...

Heads, https://osresearch.net/

If you worried about malicious changes, there is the write lock protection feature in coreboot that prevents internal flashing. This would require you to flash externally whenever you want to update coreboot. If worried someone will also flash your BIOS externally, you may want to look into Heads

You need a TPM 2.0 compatible CPU, but something like this sounds really excellent: https://github.com/tpm2-software/tpm2-totp

This means your laptop itself would be your hardware device, the TOTP secret would be stored in the TPM and theoretically impossible to steal/copy. Of course this means you will probably want a mobile device (possibly a second laptop also) as a backup.)

>But okay, you may extend my attack by saying that you exchange the motherboard between the victim and the attacker laptop, so that you don't need to replicate the chassis.

Modern computers has tamper detection and if you open them you'll need to type the BIOS password.

However, replacing the motherboard is going to replace the TPM. This is easily detectable with something like tpm2_totp in the bootchain.

https://github.com/tpm2-software/tpm2-totp

You could also use TOTP for a kind of remote attestation (e.g., with your phone computing TOTP). In this setup, the CPU sends the timestamp to the TPM, and it returns the TOTP value. So instead of you looking at your phone to give the TOTP to a service provider to prove that you're in possession of your phone, the computer gives you a TOTP value to prove that it's in possession (inside the TPM, sealed to the boot chain hashes) of the TOTP secret, and you use your phone to verify this. A possible weakness (short of a full-blown TPM compromise) would be to send a bunch of forged timestamps to the TPM while your computer is running and store the resulting TOTP values, then tamper with Secure Boot and emit the precomputed TOTP corresponding to the current timestamp whenever you boot up your computer. But this would require running malicious code on your compute while you're logged in with the trusted boot chain.