How will you handle backward compatibility?
Kernel X has 75 function definitions in 'struct check_struct'. Kernel
X+1 has 76. Doesn't a module that was built for version X break in the
face of this? Are you going to rely on kernel module versioning to help
address this issue - namely, refuse to load a mis-matched module?
Thanks
Andrew
Chris Wright wrote:
> > init_module()
> > {
> > struct check_struct mymodule_checks = {
> > check_fs_open: & mymodule_fs_read,
> > check_fs_read: & mymodule_fs_open,
> > check_fs_write: & mymodule_fs_write,
> > check_socket_open: & mymodule_socket,
> > check_socket_read: & mymodule_socket,
> > check_socket_write: & check_socket_write_refuse,
> > ...
> > check_kernel_checkpolicy_set: & mymodule_kernel_checkpolicy_set,
> > /* How we accept other security modules...*/
> > };
> >
> > kernel_set_check_policy (&mymodule_checks);
_______________________________________________
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 : Mon Apr 16 2001 - 20:29:45 PDT