Am Donnerstag, 23 Juni 2016, 09:57:51 schrieb Balbir Singh: > On 23/06/16 03:02, Thiago Jung Bauermann wrote: > >>> 3. have IMA pass-on its event log (where integrity measurements are > >>> > >>> registered) accross kexec to the second kernel, so that the event > >>> history is preserved. > >> > >> OK.. and this is safe? Do both the kernels need to be signed by the > >> same certificate? > > > > They don't. The integrity of the event log (assuming that is what you > > mean by "this" in "this is safe") is guaranteed by the TPM device. Each > > event in the measurement list extends a PCR and records its PCR value. > > It is cryptographically guaranteed that if you replay the PCR extends > > recorded in the event log and in the end of the process they match the > > current PCR values in the TPM device, then that event log is correct. > > What I meant was how does the new kernel know that the old kernel did not > cheat while passing on the values? I presume because we trust that kernel > via a signature. Sorry, I still don't understand your concern. What kind of cheating? Which values? If it's the values in the event log, there's no need to trust the old kernel. The new kernel knows that the old kernel didn't pass wrong measurement values in the event log because it can recalculate the PCR extend operations recorded in the log and compare the results of the replay with the current PCR values stored in the TPM device. If they match, then the event log is guaranteed to be correct. If they don't match, either the memory was corrupted somehow during the kexec process, or the old kernel tried to pass a falsified event log. There's no known way to construct an alternative series of PCR extend operations that will result in the same final value in the PCR register of the TPM device. If you can do that, you discovered a hash collision attack on the SHA-1 or SHA-256 algorithms (depending on which algorithm is being used by IMA in the event log). Or a bug in the TPM device implementation. > and > > How do we know the new kernel is safe to load - I guess via a signature > that the new kernel is signed with (assuming it is present in the key > ring). Correct. That goal is met by signature verification, not by integrity assurance. I'll note that even with both of my patch series there's still code missing for kernel signature verification in PowerPC. I believe there's not a file format defined yet for how to store a signature in a PowerPC kernel image. Integrity assurance doesn't depend on kernel signature verification though. There's value in both my patch series even without kernel signature verification support. They're complementary features. []'s Thiago Jung Bauermann IBM Linux Technology Center
