From owner-freebsd-security@FreeBSD.ORG  Sat May 14 22:32:08 2005
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5512C16A4CE
	for <freebsd-security@freebsd.org>;
	Sat, 14 May 2005 22:32:08 +0000 (GMT)
Received: from dfmm.org (treehorn.dfmm.org [66.180.195.213])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 192DE43D72
	for <freebsd-security@freebsd.org>;
	Sat, 14 May 2005 22:32:08 +0000 (GMT)
	(envelope-from freebsd-security@dfmm.org)
Received: (qmail 33754 invoked by uid 1000); 14 May 2005 22:32:07 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 14 May 2005 22:32:07 -0000
Date: Sat, 14 May 2005 15:32:07 -0700 (PDT)
From: Jason Stone <freebsd-security@dfmm.org>
X-X-Sender: jason@treehorn.dfmm.org
To: Chris <chrcoluk@gmail.com>
In-Reply-To: <3aaaa3a050514000629cc8427@mail.gmail.com>
Message-ID: <20050514152716.D99949@treehorn.dfmm.org>
References: <245f0df105051318564b1ffb6b@mail.gmail.com> 
	<245f0df105051322354e8e86eb@mail.gmail.com>
	<3aaaa3a050514000629cc8427@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
cc: freebsd-security@freebsd.org
cc: Poul-Henning Kamp <phk@phk.freebsd.dk>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-05:09.htt [REVISED]
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2005 22:32:08 -0000


> I am somewhat confused by applying the patch, does this disable HTT 
> functionality? or does a patched server close the issue and keep HTT 
> enabled?

it disables htt by default.

I wasn't able to tell by looking at it, though, does it also disable the 
second core on a dual-core cpu, or is it specific to htt?

also, I wonder, is there an intention of advertising more loudly the fact 
that htt is henceforth always going to be disabled by default?  is there 
any intention of having the installer offer an option to set the loader 
tunable?


  -Jason