Delivery-Date: Tue, 01 Sep 2015 01:41:40 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 4A7851E03D0;
	Tue,  1 Sep 2015 01:41:38 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 63FED367E6;
	Tue,  1 Sep 2015 05:41:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 66C7136C1B
 for <tor-talk@lists.torproject.org>; Tue,  1 Sep 2015 05:41:31 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id J2R3QxGZJyoy for <tor-talk@lists.torproject.org>;
 Tue,  1 Sep 2015 05:41:31 +0000 (UTC)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com
 [IPv6:2607:f8b0:4001:c06::22a])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 4731F367E6
 for <tor-talk@lists.torproject.org>; Tue,  1 Sep 2015 05:41:31 +0000 (UTC)
Received: by ioeu67 with SMTP id u67so41447407ioe.1
 for <tor-talk@lists.torproject.org>; Mon, 31 Aug 2015 22:41:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :cc:content-type;
 bh=/Hc7jDQ6DeXcszTBar2li+eDXA4PYRYt7odHmN9G8s0=;
 b=Wd+bOuOwzDIxO9UIp754CJ+tvey8JKbb2JKgm6uagup/OUSgdshw5UGWr9W83p5FBb
 fyQsGwX2vom6+5WJjCHJL3Vgx25ze2JcxPYK0kgjo15TgE/hwMB0dPYRkTwy8JVprhts
 5YtvOrnqDj/CBTbNnJy59Pistp797YyaNRQ97ezA9Fb78P94JF3Y2bPP/P7ZDuu1uaLQ
 b3VYMXr/PEpv9/4l5CxCCSQrz8D+wdIDWIT/xfZWlXNISNAw9tW1IwEzsYjKDIxPT6Lo
 p4E3eAyxceOM8OPbQgkqG0IcZPSL1WNmjudXIBp3J/IBcng8yKxUCcdLr1xXDLlXUmHg
 vUdg==
X-Received: by 10.107.10.30 with SMTP id u30mr33036997ioi.7.1441086088992;
 Mon, 31 Aug 2015 22:41:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.77.77 with HTTP; Mon, 31 Aug 2015 22:41:09 -0700 (PDT)
In-Reply-To: <CAFggDF0pMYEWjEgLxAA10wumDLOLsx-Hhc9G0eV4Nfr8Veg0Kw@mail.gmail.com>
References: <55E17366.1050205@openmailbox.org>
 <CAFggDF0pMYEWjEgLxAA10wumDLOLsx-Hhc9G0eV4Nfr8Veg0Kw@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
Date: Tue, 1 Sep 2015 01:41:09 -0400
Message-ID: <CAD2Ti28-dipppms6MZe75mEERgvzLvfu72ND-0fuU+cv6e1o3g@mail.gmail.com>
To: tor-talk@lists.torproject.org
Cc: cypherpunks@cpunks.org
Subject: Re: [tor-talk] hardware recommendations
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Sun, Aug 30, 2015 at 5:49 PM, Jacob Appelbaum <jacob@appelbaum.net> wrote:
> Intel has AMT and opaque microcode updates, other CPU vendors have
> similar fun hardware features.
>
> Further reading regarding AMT from the FSF:
>
>   https://www.fsf.org/blogs/community/active-management-technology

Some Intel docs indicate that remote AMT requires their "LM" series lan
controllers. The Intel programming guides and block diagrams indicate
an ability to update (and perhaps by that to zero) the AMT and related firmware.
Their general CPU microcode is signed. Didn't read far enough yet to
tell the full scope of what is in their programming guides in these areas.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

