On Tue, 10 Nov 2015, Theodore Ts'o wrote: > If you want to create a patch, my recommendation would be to do one > that turns off ambient capabilities as a CONFIG option, and hide it > under CONFIG_EXPERT. Or maybe adding a new securebit which disables > ambient capabilities. Whether or not that will be acceptable > upstream, I don't know, mainly because I think a strong case can be
That is already available and was submitted with the patch. commit 746bf6d64275be0c65b0631d8a72b16f1454cfa1 Author: Andy Lutomirski <[email protected]> Date: Fri Sep 4 15:42:51 2015 -0700 capabilities: add a securebit to disable PR_CAP_AMBIENT_RAISE Per Andrew Morgan's request, add a securebit to allow admins to disable PR_CAP_AMBIENT_RAISE. This securebit will prevent processes from adding capabilities to their ambient set. For simplicity, this disables PR_CAP_AMBIENT_RAISE entirely rather than just disabling setting previously cleared bits. Signed-off-by: Andy Lutomirski <[email protected]> Acked-by: Andrew G. Morgan <[email protected]> Acked-by: Serge Hallyn <[email protected]> Cc: Kees Cook <[email protected]> Cc: Christoph Lameter <[email protected]> Cc: Serge Hallyn <[email protected]> Cc: Jonathan Corbet <[email protected]> Cc: Aaron Jones <[email protected]> Cc: Ted Ts'o <[email protected]> Cc: Andrew G. Morgan <[email protected]> Cc: Mimi Zohar <[email protected]> Cc: Austin S Hemmelgarn <[email protected]> Cc: Markku Savela <[email protected]> Cc: Jarkko Sakkinen <[email protected]> Cc: Michael Kerrisk <[email protected]> Cc: James Morris <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
