mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.1.0 released
Date: Tue, 11 Jun 2013 14:18:51 -0400	[thread overview]
Message-ID: <1651731.uq3eGijaMq@sifl> (raw)

I would like to announce a new libseccomp release, libseccomp version 2.1.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.1.0.tar.gz/download

This new version of libseccomp builds upon the previous release and should be 
a drop-in replacement for the 2.x releases with v1.x users requiring only a 
recompile.  All users are encouraged to upgrade to the new version at their 
earliest convenience.

Changes in the 2.1.0 release include:

 * Support for the x32 and ARM architectures/ABIs; removes the need for ABI 
specific seccomp BPF code, libseccomp handles this all internally
 * Improvements to the PFC code generator and the inclusion of a syscall 
number-to-name and name-to-number resolver to aid application developers
 * The usual collection of bugfixes, both large and small

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-06-11 18:19 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=1651731.uq3eGijaMq@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

all inboxes | Powered by JetHome®