Hi all, With the addition of MODULE_LICENSE in 2.4.10, I got to thinking about the license of our security.h file. Personally I think closed source security products are bad things for a variety of reasons, and I think that most people on this project also agree with me. Toward that, I've added a few words to security.h keeping any closed source modules from using the security module interface to the kernel. I've attached the patch that I came up with below (and accidentally committed it to the tree, sorry, I didn't mean to do that without some discussion first, it can be backed out or changed.) The wording isn't the best, but I think it gets the idea across. Does anyone have any better wording they can think of for this? Or does anyone object to this change? thanks, greg k-h
This archive was generated by hypermail 2b30 : Sun Sep 23 2001 - 18:46:12 PDT