From: Paul Moore <pmoore@redhat.com>
To: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
libseccomp-discuss@lists.sourceforge.net
Subject: ANN: libseccomp 2.0.0 released
Date: Mon, 28 Jan 2013 11:11:04 -0500 [thread overview]
Message-ID: <1761584.CAfxVeTaQM@sifl> (raw)
I would like to announce a new major release for the libseccomp library,
libseccomp version 2.0.0. The libseccomp library provides an easy to use,
platform independent, interface to the Linux enhanced syscall filtering
mechanism that was first introduced in Linux 3.5.
* http://sourceforge.net/projects/libseccomp
* http://sf.net/projects/libseccomp/files/libseccomp-2.0.0.tar.gz/download
This new version of libseccomp is source compatible with version 1.0.0 and
later of the library. Both the libseccomp v2.x and libseccomp v1.x libraries
should be able to coexist on the same system but all users are encouraged to
upgrade to the new version at their earliest convenience.
Changes in the 2.0.0 release include:
* Fixes for the x86 multiplexed syscalls
* Additions to the API to better support non-native architectures
* Additions to the API to support multiple architectures in one filter
* Additions to the API to resolve syscall name/number mappings
* Assorted minor bug fixes
* Improved build messages regardless of build verbosity
* More automated tests added as well as a number of improvements to the test
harness
Finally, thank you to everyone who has submitted suggestions, provided testing
help, and contributed patches to the project.
--
paul moore
security and virtualization @ redhat
reply other threads:[~2013-01-28 16:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1761584.CAfxVeTaQM@sifl \
--to=pmoore@redhat.com \
--cc=libseccomp-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox