From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:45517) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeuEs-0005H3-Un for qemu-devel@nongnu.org; Wed, 13 Jun 2012 16:32:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SeuEr-0000v1-Ax for qemu-devel@nongnu.org; Wed, 13 Jun 2012 16:32:26 -0400 Received: from mx1.redhat.com ([209.132.183.28]:24970) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeuEr-0000um-2o for qemu-devel@nongnu.org; Wed, 13 Jun 2012 16:32:25 -0400 From: Paul Moore Date: Wed, 13 Jun 2012 16:31:58 -0400 Message-ID: <1598797.KYtkCSSkRj@sifl> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [Qemu-devel] [RFC] [PATCHv2 0/2] Sandboxing Qemu guests with Libseccomp List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: libseccomp-discuss@lists.sourceforge.net, Eduardo Otubo On Wednesday, June 13, 2012 04:20:20 PM Eduardo Otubo wrote: > Hello all, > > This is the second effort to sandbox Qemu guests using Libseccomp[0]. ... > [0] - http://sourceforge.net/projects/libseccomp/ [1] - > http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=e2c > fabdfd075648216f99c2c03821cf3f47c1727 It is worth pointing out that you no longer need to fetch libseccomp from the git repository, we did our first release (v 0.1.0) last Friday, June 8th: * https://sourceforge.net/projects/libseccomp/files Packages are available for Debian/Ubuntu and Fedora packaging is currently in progress. -- paul moore security and virtualization @ redhat