On Sun, Mar 29, 2015 at 10:47 AM, Andrei Borzenkov
I would very interested to see full values of PK, KEK and db EFI variables from systems affected by mentioned bugs for a start.
So you need to see the contents of efivars for this? Like, a complete hexdump -C for every "file" in efivars directory? There are definitely screwy things happening here, there are even fake boot entries now happening as kludges by some companies who can't otherwise figure out how to make standard methods work. So they work around their own bugs with fake boot entries. Idiots. And this is just one example of how some hardware must have NVRAM named entries as "Windows Boot Manager" even if those boot entries aren't Windows. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org