> Even today's modern 64-bit CPUs begin execution in 16-bit mode. In UEFI, this is called the SEC phase. Is that true even for the T2 Macs and such?
[0] https://youtu.be/3byNNUReyvE
[1] https://www.blackhat.com/us-19/briefings/schedule/#behind-th...
11–20 of 100 posts
> Even today's modern 64-bit CPUs begin execution in 16-bit mode. In UEFI, this is called the SEC phase. Is that true even for the T2 Macs and such?
[0] https://youtu.be/3byNNUReyvE
[1] https://www.blackhat.com/us-19/briefings/schedule/#behind-th...
If requisite credentials or remote attestation is sealed against a certain measurement value it should protect the system.
> Even today's modern 64-bit CPUs begin execution in 16-bit mode. In UEFI, this is called the SEC phase. Is that true even for the T2 Macs and such?
Apple has been moving their defenses earlier and earlier in the boot process. According to this talk[0] they are even able to foil malicious option ROM[1] and other early boot attacks. I don’t recall if they mention boot passwords specifically, but they claim to lead the industry in this regard. [0] https://youtu.be/3byNNUReyvE [1] https://www.blackhat.com/us-19/briefings/schedule/#behind-th...
https://docs.microsoft.com/en-us/windows-hardware/manufactur...
Earlier quoted context omitted.
I'm not that familiar with Macs, but if they're using an Intel CPU it almost definitely starts in 16-bit mode. From what I understand the T2 chip is more akin to what's called an embedded controller in other laptops.
According to the CPU processor manuals, they all boot in "real mode" which is a 16-bit legacy/bootstrap mode.
They start this way because at initial reset none of the required data structures for protected mode operation (page tables, GDT, IDT, etc.) are present. So the CPU starts up as a very fast 8086 who's purpose is to setup just enough page tables, a GDT, an IDT, etc. to be able to switch into protected mode and continue system bootstrap.
I'm curious if TPM measurements would catch these kind of manipulations. It's probably system specific but the configuration of the BIOS should (as far as I understand it) be captured as part of the measurement process. If requisite credentials or remote attestation is sealed against a certain measurement value it should protect the system.
[0]: https://trustedcomputinggroup.org/wp-content/uploads/TCG-EFI...
I was of the impression that BIOS passwords were in general not something one should rely even as a layer when assuming physical access. In the (not that) old days it was usually just a matter of removing the internal battery to reset it. Has this assumption changed in past years?
There are quite a few laptops on ebay at considerable discounts because the seller doesn't know the BIOS password. This could come in handy.