Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267565AbUJLS35 (ORCPT ); Tue, 12 Oct 2004 14:29:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267576AbUJLS3q (ORCPT ); Tue, 12 Oct 2004 14:29:46 -0400 Received: from mail-relay-1.tiscali.it ([213.205.33.41]:43498 "EHLO mail-relay-1.tiscali.it") by vger.kernel.org with ESMTP id S267565AbUJLS3E (ORCPT ); Tue, 12 Oct 2004 14:29:04 -0400 Date: Tue, 12 Oct 2004 20:29:42 +0200 From: Andrea Arcangeli To: Rik van Riel Cc: Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: secure computing for 2.6.7 Message-ID: <20041012182942.GA17849@dualathlon.random> References: <20041012174605.GH17372@dualathlon.random> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-GPG-Key: 1024D/68B9CB43 13D9 8355 295F 4823 7C49 C012 DFA1 686E 68B9 CB43 X-PGP-Key: 1024R/CB4660B9 CC A0 71 81 F4 A0 63 AC C0 4B 81 1D 8C 15 C8 E5 User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 981 Lines: 25 On Tue, Oct 12, 2004 at 02:10:52PM -0400, Rik van Riel wrote: > On Tue, 12 Oct 2004, Andrea Arcangeli wrote: > > > However as said boinc and seti would better start using it too. > > Thinking about it some more, I'm not convinced they can. > > After all, they need to get new data to perform calculations > on, and pass the results of previous calculations on to the > server. > > In order to do that, the user needs to run code that's not > restricted by seccomp. [..] Getting new data to performance calculations and pass the results up to the buyer is what I'm doing too and it's the ideal workload to use with seccomp or trusted computing. But this is very offtopic discussion for this list. jpeg sure can be decompressed too. - 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/