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 1.0.1 released
Date: Mon, 12 Nov 2012 16:51:13 -0500 [thread overview]
Message-ID: <2742323.xTGOeEdtc5@sifl> (raw)
I would like to announce a maintenance release for the libseccomp library,
libseccomp version 1.0.1. The libseccomp library provides an easy to use,
platform independent, interface to Linux's enhanced syscall filtering
mechanism.
* http://sourceforge.net/projects/libseccomp
* http://sf.net/projects/libseccomp/files/libseccomp-1.0.1.tar.gz/download
All users of libseccomp are strongly encourage to update to this latest
release. Changes in the 1.0.1 release include:
* Fixes for the following:
** memory leaks
** small filters, e.g. filtering only a single syscall
** filters with syscall arguments
* Documentation corrections
* Support for C++ in the header file
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:[~2012-11-12 21:51 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=2742323.xTGOeEdtc5@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.