Wouldn't it be useful for a userspace application that is setuid root to be able to bypass the module's checks. Isn't setuid ROOT generally assumed to be a "non-restricted" condition? How does the new paradigm change that, specifically, and why SHOULD it do that? Just A Question, J. Melvin Jones |>------------------------------------------------------ || J. MELVIN JONES jmjonesat_private |>------------------------------------------------------ || Microcomputer Systems Consultant || Software Developer || Web Site Design, Hosting, and Administration || Network and Systems Administration |>------------------------------------------------------ || http://www.jmjones.com/ |>------------------------------------------------------ _______________________________________________ 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 : Thu Jan 24 2002 - 12:52:31 PST