Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262543AbTFTJVL (ORCPT ); Fri, 20 Jun 2003 05:21:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262562AbTFTJVK (ORCPT ); Fri, 20 Jun 2003 05:21:10 -0400 Received: from dyn-ctb-203-221-72-161.webone.com.au ([203.221.72.161]:18963 "EHLO chimp.local.net") by vger.kernel.org with ESMTP id S262543AbTFTJVI (ORCPT ); Fri, 20 Jun 2003 05:21:08 -0400 Message-ID: <3EF2D500.40707@cyberone.com.au> Date: Fri, 20 Jun 2003 19:33:52 +1000 From: Nick Piggin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030527 Debian/1.3.1-2 X-Accept-Language: en MIME-Version: 1.0 To: Xavier Bestel CC: Linus Torvalds , Nuno Silva , Samphan Raruenrom , Vojtech Pavlik , Linux Kernel Mailing List Subject: Re: Crusoe's persistent translation on linux? References: <1056100114.2978.31.camel@nomade> In-Reply-To: <1056100114.2978.31.camel@nomade> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 945 Lines: 28 Xavier Bestel wrote: >Le ven 20/06/2003 ? 02:16, Linus Torvalds a ?crit : > >>So no, it wouldn't really benefit from it, not to mention that it's not >>even an option since Transmeta has never released enough details to do it >>anyway. Largely for simple security concerns - if you start giving >>interfaces for mucking around with the "microcode", you could do some >>really nasty things. >> > >Did you just write: "the Crusoe has special backdoors built-in which >would allow a userspace program to takeover the machine, and Transmeta >choose security through obscurity to avoid this problem" ? >Nice call for crackers :) > > Hmm, did you just write: "Linus, I take you for an imbecile" ? ;) - 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/