From: Paul Moore <paul@paul-moore.com>
To: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
libseccomp-discuss@lists.sourceforge.net
Subject: ANN: libseccomp 2.1.1 released
Date: Thu, 31 Oct 2013 12:04:25 -0400 [thread overview]
Message-ID: <5205940.GnC9iqXGhX@sifl> (raw)
I would like to announce a maintenance release for the libseccomp library,
libseccomp version 2.1.1. 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
This new version of libseccomp is binary compatible with versions 2.0.0 and
greater while retaining source compatibility with versions 1.0.0 and greater.
All users are encouraged to upgrade to the new version at their earliest
convenience.
Changes in the 2.1.1 release include:
* Fixes to the internal syscall rule filtering database
* Improvements to the build and automated test systems
* Coding style verification tools
Finally, thank you to everyone who has submitted suggestions, provided testing
help, and contributed patches to the project.
--
paul moore
www.paul-moore.com
reply other threads:[~2013-10-31 16:04 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=5205940.GnC9iqXGhX@sifl \
--to=paul@paul-moore.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
Powered by JetHome