Tree [e67459] /
 History

HTTPS access


File Date Author Commit
 doc 2012-05-21 Paul Moore Paul Moore [91ccc5] doc: fix the manpage comments
 include 2012-04-26 Paul Moore Paul Moore [340c43] api: rename the seccomp_gen_*() functions to se...
 src 2012-04-26 Paul Moore Paul Moore [340c43] api: rename the seccomp_gen_*() functions to se...
 tests 2012-04-26 Paul Moore Paul Moore [340c43] api: rename the seccomp_gen_*() functions to se...
 tools 2012-04-10 Paul Moore Paul Moore [d3f6e6] bpf_sim: fix some problems with syscall argumen...
 .gitignore 2012-04-16 Paul Moore Paul Moore [c6ffe2] build: generate a pkgconfig file at configure time
 CREDITS 2012-05-22 Paul Moore Paul Moore [4f844f] doc: create a CREDITS file
 LICENSE 2012-04-09 Paul Moore Paul Moore [160e7c] all: relicense the library from GPLv2 to LGPLv2.1
 Makefile 2012-04-16 Paul Moore Paul Moore [8154e0] build: install the pkg-config file
 README 2012-05-22 Paul Moore Paul Moore [e67459] doc: refresh the README file
 configure 2012-04-16 Paul Moore Paul Moore [c6ffe2] build: generate a pkgconfig file at configure time
 install.mk 2012-04-15 Paul Moore Paul Moore [c402e9] build: cleanup some of the build macros and Mak...
 libseccomp.pc.in 2012-04-16 Paul Moore Paul Moore [c6ffe2] build: generate a pkgconfig file at configure time
 macros.mk 2012-05-18 Paul Moore Paul Moore [8dac93] build: build the shared library with a versione...
 version_info 2012-04-16 Paul Moore Paul Moore [b692c0] build: generate version_info.mk at configure time

Read Me

libseccomp: An Enhanced Seccomp (mode 2) Helper Library
===============================================================================
http://libseccomp.sf.net

The libseccomp library provides and easy to use, platform independent,
interface to the Linux Kernel's syscall filtering mechanism: seccomp.  The
libseccomp API is designed to abstract away the underlying BPF based syscall
filter language and present a more conventional function-call based filtering
interface that should be familiar to, and easily adopted by application
developers.

* Documentation

The "doc/" directory contains all of the documentation aside from the README
file (this file) and the LICENSE file which can be found in the top level
directory.

* Building and Installing the Library

In order to build the library you should follow the familiar three step
process used by most applications:

	# ./configure
	# make
	# make install

As usual, running "./configure -h" will display a list of build-time
configuration options.

* Testing the Library

There are a number of tests located in the "tests/" directory and a script
which can be used to help automate their execution, "regression".  If you want
to run all of the tests you can simply run the script:

	# ./configure
	# make
	# cd tests
	# ./regression

However, the script takes a number of options to customize its execution; the
options can be displayed by running "./regression -h".

* Other Useful Tools

The "tools/" directory includes a number of tools which may be helpful in the
development of the library, or applications using the library, but for various
reasons are not installed by default.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks