On Sat, 26 Jan 2002 05:16, Casey Schaufler wrote: > This has been a longstanding issue in the trusted systems world. > Any change to the policy makes 3rd party installation scripts > fail, especially those which check for access and proceed > based on the information returned. Yes, I know, all applications > should be written to deal with failures. To do so, they > need to know the policies being enforced. They need a way > to find this out. Why not just ship the application in question in RPM or DEB form and have the package manager deal with this? You can build a RPM or DEB package on a machine without any LSM support and then install it on an LSM machine. As long as the package dependencies were correct then it would work fine. -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page _______________________________________________ linux-security-module mailing list linux-security-moduleat_private http://mail.wirex.com/mailman/listinfo/linux-security-module
This archive was generated by hypermail 2b30 : Fri Jan 25 2002 - 18:21:43 PST