> > >>I'm going to try another way first: I've done multiple re-builds of my >>kernel and although I think I've used the correct procedure, I wonder if >>actually there's not part of former security modules (SELinux etc) that >>are still somehow used and that would be the cause of my 'security >>framework already loaded'. >> >> > >I'd expect that something like that is the problem. SELinux will >generate a message when it's loaded, do you see anything in dmesg? > Well, I did not see it, but since then, I've recompiled from scratch and it works, so I believe I've done something wrong meanwhile ... However, there's still a problem: - when I try to load the root_plug module alone I get multiple complaints about some capability symbols missing. - so, I thought, let's load the capability module before.. but then, I can no longer load root_plug (security framework already initialized of course). Just to test, I tried to compile the LSM capability directly in the kernel (not as a module), and then load the root-plug module, but it's the same. I understand root_plug is only an example, but isn't it meant to load at all ? Cheers Axelle. _______________________________________________ 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 : Wed May 21 2003 - 14:26:18 PDT