With regard to security_ops->module_id This raises some issues with my stackable modules. If we're defining a single module_id that is to be trusted as unique for a module or family of modules, how will these identifiers be assigned to assure they're unique? Since everybody will be implementing this hook (it's required to pass the sanity check for installation), is it really useful or necessary to check the module identity outside the module? I don't necessarily see the value of copying data to and from kernel space outside the module, but it does seem to be something that will be very common. If most are likely to do it, putting it in one place makes sense. Would doing it and passing BOTH the user and kernel pointer to the hook solve both cases, or just clutter up kernel memory hopelessly with something generally useless? (Depends on how many use which pointer.) 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 Aug 09 2001 - 09:57:31 PDT