From: Paul Moore <pmoore@redhat.com>
To: libseccomp@googlegroups.com, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: ANN: libseccomp v2.2.0 released
Date: Thu, 12 Feb 2015 16:40:51 -0500 [thread overview]
Message-ID: <6143762.g4BTK3eOEQ@sifl> (raw)
We've just released a new version of libseccomp, libseccomp version 2.2.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.
* https://github.com/seccomp/libseccomp/releases/tag/v2.2.0
This new version of libseccomp builds upon the previous release and should be
a drop-in replacement for the 2.x releases. All users are encouraged to
upgrade to the new version at their earliest convenience.
Changes in the 2.2.0 release include:
* Migrated the build system to autotools
* Added support for the aarch64 architecture
* Added support for the mips, mips64, and mips64n32 architectures
* Added support for the new seccomp() syscall and thread sync
* Added Python bindings
* Updated the internal syscall tables to Linux v3.19
* Added documentation to help contributors wishing to submit patches
* Numerous minor bug fixes
In addition, the libseccomp project has migrated away from SourceForge and to
a combination of Github and Google Groups, please use the new git repository
and mailing list:
* https://github.com/seccomp/libseccomp
* https://groups.google.com/d/forum/libseccomp
Finally, thank you to everyone who has submitted suggestions, provided testing
help, and contributed patches to the project.
--
paul moore
security @ redhat
reply other threads:[~2015-02-12 21:40 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=6143762.g4BTK3eOEQ@sifl \
--to=pmoore@redhat.com \
--cc=libseccomp@googlegroups.com \
--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
all inboxes | Powered by JetHome®