Quoting KaiGai Kohei ([EMAIL PROTECTED]): > [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? > > Because the repository on the google code is a bit confusable > for anyone trying to use recent capability features, I noticed > an infomation to refere Andrew's git-tree on the top of the project > page for a while, and now the repository on the googlecode is > only visible for me.
Ok - I didn't remember you saying you were going to take it down, so I wanted to make sure that was intended. thanks, -serge >> 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...) >> thanks, >> -serge > > > -- > OSS Platform Development Division, NEC > KaiGai Kohei <[EMAIL PROTECTED]> - 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
