• Home
  • History
  • Annotate
  • only in /external/libcap-ng/libcap-ng-0.7/
NameDateSize

..14-Feb-20134 KiB

aclocal.m414-Feb-201343.7 KiB

AUTHORS14-Feb-201367

autogen.sh14-Feb-2013109

bindings/14-Feb-20134 KiB

ChangeLog14-Feb-20132.7 KiB

compile14-Feb-20136.7 KiB

config.guess14-Feb-201343.6 KiB

config.h.in14-Feb-20132.3 KiB

config.sub14-Feb-201334.5 KiB

configure14-Feb-2013441.1 KiB

configure.ac14-Feb-20134.5 KiB

COPYING14-Feb-201317.6 KiB

COPYING.LIB14-Feb-201325.9 KiB

depcomp14-Feb-201319.9 KiB

docs/14-Feb-20134 KiB

INSTALL14-Feb-201315.4 KiB

install-sh14-Feb-201313.7 KiB

libcap-ng.spec14-Feb-20133.1 KiB

ltmain.sh14-Feb-2013276.8 KiB

m4/14-Feb-20134 KiB

Makefile.am14-Feb-20131.1 KiB

Makefile.in14-Feb-201324.4 KiB

missing14-Feb-201310.1 KiB

NEWS14-Feb-20130

py-compile14-Feb-20134.2 KiB

README14-Feb-2013721

src/14-Feb-20134 KiB

utils/14-Feb-20134 KiB

README

1The libcap-ng library should make programming with posix capabilities
2easier. The library has some utilities to help you analyse a system
3for apps that may have too much privileges.
4
5NOTE: to distributions. There is a "make check" target. It only works
6if the headers match the kernel. IOW, if you have a chroot build system
7that is using a much older kernel, the macros in the kernel header files
8will do the wrong thing when the capng_init function probes the kernel
9and decides we are doing v1 rather than v3 protocol. If that is your case,
10just don't do the "make check" as part of the build process.
11
12Report any bugs in this package to  sgrubb@redhat.com  or better yet,
13file them here: https://bugzilla.redhat.com/
14