> Capabilities can be seen as related to this patch set, but it cannot > be seen as a blocker. This logic is needed today, it's implemented, > and it clearly marks where the known problems are. If an overhaul of > capabilities happens, it can happen separately. A working version is needed today - but the implementation assumes things like the idea you can blacklist a few boot parameters and all is good. The reality is the reverse. So this at the moment is security theatre at least for the EFI and PC case. At the minimum you need to do module and kernel command line parameter whitelisting/signing. It's also rather odd to suggest the solution is to splatter changes all over the kernel causing mass churn and maintainer headache... so that we can do the whole mass churn again fixing what was added. Alan -- 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
