Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267186AbUJLSFH (ORCPT ); Tue, 12 Oct 2004 14:05:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266538AbUJLSFH (ORCPT ); Tue, 12 Oct 2004 14:05:07 -0400 Received: from mx1.redhat.com ([66.187.233.31]:20130 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S267186AbUJLSEn (ORCPT ); Tue, 12 Oct 2004 14:04:43 -0400 Date: Tue, 12 Oct 2004 14:04:28 -0400 (EDT) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Andrea Arcangeli cc: Andrew Morton , Subject: Re: secure computing for 2.6.7 In-Reply-To: <20041012174605.GH17372@dualathlon.random> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1006 Lines: 26 On Tue, 12 Oct 2004, Andrea Arcangeli wrote: > On Tue, Oct 12, 2004 at 12:28:48PM -0400, Rik van Riel wrote: > > Looks like it should work, though really only for the > > purposes of cpushare and nothing else. > However as said boinc and seti would better start using it too. Are they interested ? > And people could start using it for other things too every time they > deal with untrusted data or bytecode. Would be interesting for eg. browser plugins, though I don't know whether the current seccomp infrastructure is powerful enough for that ... -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/