Jiri Kosina <jikos@xxxxxxxxxx> wrote: > > This prevents crypto data theft by analysis of execution patterns, and, if > > in future ftrace also logs the register contents at the time, will prevent > > data theft by that mechanism also. > > I fail to see how this fits into the secure boot security model, could you > please explain? The idea is to prevent cryptographic data for filesystems and other things from being read out of the kernel memory as well as to prevent unauthorised modification of kernel memory. > Secure boot is about having a constant proof / verification that the code > you're running in ring0 can be trusted (IOW is the one that has been > signed and verified by the whole boot chain). > > Checking execution patterns doesn't seem to fit at all. I'll defer this question to Alexei since he suggested I needed to deal with this too. David -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
