On Wed, 31 Oct 2012, Chris Friesen wrote: > > That would do it on my system. > > Maybe in theory you could solve this by the kernel invalidating images > > it hasn't written itself and forbidding to change the resume partition from > > the > > kernel command line, but that would break user space hibernation. > > If the resuming kernel refuses to resume from images it didn't create itself, > why do you need to forbid changing the resume partition from the kernel > command line?
Yeah, it can definitely be solved by pushing keys around from shim to kernel (and kernel discarding the private keys at right moments). It just needs to be implemented. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
