From owner-cvs-src@FreeBSD.ORG  Sun May 15 10:59:33 2005
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id AF8EE16A4CE; Sun, 15 May 2005 10:59:33 +0000 (GMT)
Received: from lists.soekris.com (lists.soekris.com [64.105.92.243])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id ACF4543D8D; Sun, 15 May 2005 10:59:32 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by lists.soekris.com (8.12.11/8.12.11) with ESMTP id j4FAxnA1053977;
	Sun, 15 May 2005 03:59:49 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
To: Colin Percival <cperciva@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sun, 15 May 2005 02:05:25 EDT."
             <4286E6A5.4030902@freebsd.org> 
Date: Sun, 15 May 2005 12:59:26 +0200
Message-ID: <97079.1116154766@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: Jacques Vidrine <nectar@freebsd.org>
cc: cvs-src@freebsd.org
cc: src-committers@freebsd.org
cc: cvs-all@freebsd.org
cc: Nate Lawson <nate@root.org>
Subject: Re: cvs commit: src/sys/amd64/amd64 mp_machdep.c
	src/sys/amd64/include cpufunc.h src/sys/i386/i386 mp_machdep.c
	src/sys/i386/include cpufunc.h 
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 May 2005 10:59:33 -0000

In message <4286E6A5.4030902@freebsd.org>, Colin Percival writes:
>Nate Lawson wrote:
>> That is at best, hyperbole.
>
>Have you been talking to Intel lately?
>
>>  Crypto implementations which properly
>> implement blinding or operate in constant time are not vulnerable.
>
>Crypto implementations which implement blinding are vulnerable.

This is not just about crypto.

There are many processes which a random process should not be allowed
to spy on in a multiuser system.

Your boss text-procssing or email program for one thing.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.