also sprach Jurij Smakov <jurij@wooyd.org> [2005.06.10.0258 +0200]: > In order for the capability stuff to function the capability.ko > module should be loaded. The situation you describe indeed occurs > when capability.ko is not loaded into the kernel. So I would say > that this is lcap bug, as it is fails to inform the user that > capabilities cannot be removed. Yes, I agree with you. Alternatively, it should just load the module if not present. > I have also tried it with capability module loaded, and then the > command 'lcap CAP_SYS_MODULE' strips _all_ the capabilities, so it > seems to be broken in more than one way. After that loading the > modules is, in fact, impossible. I'll file the bug against lcap > once I have a confirmation that it indeed misbehaves. I can confirm this behaviour on both, Debian sid with 2.6.11 and lcap 0.0.6, and SuSE 9.2 with 2.6.8 and lcap 0.0.3. Cheers, -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! "in any hierarchy, each individual rises to his own level of incompetence, and then remains there." -- murphy (after dr. laurence j. peter)
Attachment:
signature.asc
Description: Digital signature