Linux Security *Module* Framework (Was: LSM conversion to static interface

I currently have an LSM that only handles permissions for socket_bind and socket_listen, I load it and then "capability" as secondary on boot - but now I can't because the LSM framework is now just the LS framework.

Why can't this "static LSM" change be a Kconfig option? (I don't want to have to maintain my own reverted copy of security/, or compile this into the kernel because then I can't ever modify and reload it without rebooting.) -- Simon Arlott - To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

• This message: [ Message body ]
• Next message: Pravin: "userspace Process Classifier based on SELinux Security Contexts for CPUSET, ELSA and Containers"
• Previous message: Greg KH: "Re: LSM conversion to static interface"
• Next in thread: Adrian Bunk: "Re: Linux Security *Module* Framework (Was: LSM conversion to static interface"
• Reply: Adrian Bunk: "Re: Linux Security *Module* Framework (Was: LSM conversion to static interface"
• Reply: Tetsuo Handa: "Re: Linux Security *Module* Framework (Was: LSM conversion to static interface"

• Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject ] [ By Author ]