Sigh, sorry, ignore me. Wrong kernel branch!
icouldasworn... -serge Quoting Andrew Morgan ([EMAIL PROTECTED]): > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > [EMAIL PROTECTED] wrote: > > Quoting Andrew Morgan ([EMAIL PROTECTED]): > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> Serge E. Hallyn wrote: > >>> I defined CAP_NS_UNSHARE as bit 32 as an experiment, and had to do some > >>> finagling/combination of both of your trees to do so... Though that > >>> aside I'm pleased to say it all worked perfectly. > >> In my tree, you should be able to simply add it to the convenience copy > >> of libcap/include/linux/capability.h and recompile. > > > > Andrew and Kaigai, > > > > I'm having libcap troubles. > > > > Kaigai, did you in fact take your googlecode version down? > > > > Andrew, I tried libcap 2.02 on a test system with 2.6.24-rc3. setcap > > results in binaries which won't load with a new kernel. When I use > > setfcaps from the googlecode version, it works fine. setcap also takes > > the older argument versions (i.e. not -c caps, but just caps). I don't > > care about the arguments, but thought maybe that meant an older version > > of the code snuck into the new libcap? > > > > (I haven't looked deeper into the code, since I assume there's a very > > simple explanation or solution...) > > I guess I'll need an example to look further. I'm not sure why it > wouldn't work, does strace offer any clue? > > Thanks > > Andrew > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHYFyL+bHCR3gb8jsRAtlSAJ0b/RzYdz8nCqTVSbe3xrxpmcIM8wCgnBZm > cf7yPslg05u43TnFTnqZbgQ= > =PXZE > -----END PGP SIGNATURE----- - To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
