From owner-freebsd-arch@FreeBSD.ORG  Sun May 22 05:09:48 2005
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: freebsd-arch@freebsd.org
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5CEA116A41C;
	Sun, 22 May 2005 05:09:48 +0000 (GMT)
	(envelope-from boris@brooknet.com.au)
Received: from bloodwood.hunterlink.net.au (smtp-local.hunterlink.net.au
	[203.12.144.17])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D752E43D1F;
	Sun, 22 May 2005 05:09:47 +0000 (GMT)
	(envelope-from boris@brooknet.com.au)
Received: from ppp2C32.dyn.pacific.net.au (ppp2C32.dyn.pacific.net.au
	[61.8.44.50])j4M59i0m018860;	Sun, 22 May 2005 15:09:45 +1000
From: Sam Lawrance <boris@brooknet.com.au>
To: Colin Percival <cperciva@freebsd.org>
In-Reply-To: <429012D3.6070803@freebsd.org>
References: <428FC00B.3080909@freebsd.org>
	<aef05e1ae6104223181ad3cf03e11390@xcllnt.net>
	<428FD710.4060200@freebsd.org>
	<9e8314b53980a379445cc8c07086901d@xcllnt.net>
	<428FE788.8020408@freebsd.org><42900C01.10904@freebsd.org>
	<429012D3.6070803@freebsd.org>
Content-Type: text/plain
Date: Sun, 22 May 2005 15:10:28 +1000
Message-Id: <1116738628.867.33.camel@dirk.no.domain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
cc: freebsd-arch@freebsd.org
Subject: Re: Scheduler fixes for hyperthreading
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 22 May 2005 05:09:48 -0000

On Sat, 2005-05-21 at 22:04 -0700, Colin Percival wrote:
> Sam Lawrance wrote:
> > I'm just curious here... would the mac_seeotheruids policy help in
> > obscuring the value of any information collected by a spy process?
> 
> Yes.  It would mean that the spy could steal an SSL certificate, but
> not know whose SSL certificate it was. :-)

Can the spy  be sure that it's not just stealing fortunes though?

I mean for example, can the cache timings shown on page 7 of your paper
be used to reliably identify what the other thread on the CPU is?