Here is a great technical rundown: https://blog.trailofbits.com/2016/02/17/apple-can-comply-wit...
Here is a great technical rundown: https://blog.trailofbits.com/2016/02/17/apple-can-comply-wit...
They don't, see https://www.techdirt.com/articles/20160218/10371233643/yes-b...
I can't entirely figure out how much the former Apple engineer quoted there was involved. He clearly knows how the SE firmware is loaded, but I'm not clear about the level of his knowledge from the SE side. The described mechanism of running a signed blob from RAM doesn't exclude some sort of wipe-on-update mechanism, but it would have to be very low level, part of the hardwired secure boot stuff.
The blog post that's quoted afterwards is total speculation and contains no information about this, even though it claims to.
So, probably, but still lacking a properly definitive statement.
You might want a third field, so you can store both "old" and "new" firmware hashes to temporarily bridge the gap in case the procedure got interrupted at just the wrong moment. But the point being, you could allow updates without this vulnerability, and it shouldn't be particularly hard.
Obviously, that doesn't mean they've actually done it yet. I imagine they will do something like your scheme or mine for the next hardware design.