IMO, common core utilities shouldn't be linking with specialized
libraries.
However, if SELinux has been adopted by "Gnu.org" as the standard
security mechanism, and SELinux is part of the Linux-Standard-Base
then it might not be unreasonable to include support for it.
Is SELinux part of the Linux-Standard Base now?
Alternatively, maybe there should be a applications-security-module
API to abstract calls to a specific security policy. It seems poor
practice to tie a specialized security policy into the general
versions of all application utilities, but I suppose this would
require much planning, cooperation and foresight. ;^/
-l
Ivan Gyurdiev wrote:
I had a pretty good idea about the motivation. However, it introduces
dependencies on uncommon libraries, and does not have wide
applicability, so I am trying to figure out if it can be done using
existing mechanisms.
Well, this would be an optional feature, only active in a SELinux
environment. Also, those are rather common libraries on a
SElinux-enabled system, many things link to them, including
shadow-utils, coreutils, init, and cron.
_______________________________________________
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
