From plug-discuss-bounces@lists.phxlinux.org Wed Jan 3 00:43:13 2018 Return-Path: X-Original-To: lurker@lists.phxlinux.org Delivered-To: lurker@lists.phxlinux.org Received: from phxlinux.org (localhost [127.0.0.1]) by phxlinux.org (Postfix) with ESMTP id 8C82732A01BD; Wed, 3 Jan 2018 00:43:13 -0700 (MST) X-Original-To: plug-discuss@lists.phxlinux.org Delivered-To: plug-discuss@lists.phxlinux.org Received: from mail-io0-f174.google.com (mail-io0-f174.google.com [209.85.223.174]) by phxlinux.org (Postfix) with ESMTPS id 900D032A01BC for ; Wed, 3 Jan 2018 00:43:11 -0700 (MST) Received: by mail-io0-f174.google.com with SMTP id k18so1228514ioc.11 for ; Tue, 02 Jan 2018 23:43:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=McXeDKwAQ5+sp0JBzjUNrqQKXomTFgRy9DnEiFwaoMw=; b=C3tNxEPON4mT9ycT4rvunLbUVRZI0iC0jUL/NhiR6GmXkP4vkdb7HN5AEo/bSuSxN/ KWr2yeYhFO38iSWHEGdsHbeGBlNhdeOsP/RJTgksdNnaYkz+mq0g1dZtoZbdtEMqjRhC YGX7vmWXik/E7Z7IUb7dx7tbrCZSBjOcxZEuQbk0B/bolziZgBQXLxZdMWyd/o/Y+iQ/ BZy+yT18F9VtzL/WhjibHxj8BCPP84qZ8gMMTsgFnI6jJFeLan+apGHg3raWx7Nc9kFt 2sJ57KQUk2Vn505/dIxG4ay7gOWOs5zk+4aRJ1gyQ50hFjth9dmFbLaSVwWIsvs0R1lM md+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=McXeDKwAQ5+sp0JBzjUNrqQKXomTFgRy9DnEiFwaoMw=; b=ZpUJpov9fBnB5zFoRQL80jPcxacDchSuPQt1Lp+04ZAQnGqyAIJ2WOAwMtvUE0oOXx td67/r5zUuRUsyM59fpKx4YtVIfgGzuszvv8mh32NZYoiwf99z86w7C8mEF1ZExNJL5x 8uLDtnJMq6RnKtnjX6UkInuDykHrvph1uJoce1Pvk8FQxcF5WvvwXYIVWaLAUQpaP1fQ iAMUFVdsJrOlX2I6qVDavL/FtyIWmPwcfeC594fQBoBIHcUKmqs/Ib+nxk0dLFZ34DTa SibkjofWa52VsT9z3givG5F+K5pH7SbiFUAaI5MG8Lm2u6mmYdY61REQd2rvoJdkZWgJ 9zVw== X-Gm-Message-State: AKGB3mJqn6EohrskNx1CBVmSmxsd/2Ak736YKYErOrzImMxRxmIKFZuj hJVOygX+JpUoc9Ho/h9x3g0lrSBp X-Google-Smtp-Source: ACJfBovYv+BFPVqQF3jUHOw3omybYwHFEsy+JTPwZi9unbWkPyLbvjHc/whS426y/mi4heP27MDDmw== X-Received: by 10.107.198.73 with SMTP id w70mr664411iof.56.1514965390816; Tue, 02 Jan 2018 23:43:10 -0800 (PST) Received: from [192.168.0.22] (71-211-124-167.phnx.qwest.net. [71.211.124.167]) by smtp.gmail.com with ESMTPSA id 140sm6324848itx.3.2018.01.02.23.43.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Jan 2018 23:43:10 -0800 (PST) From: Aaron Jones Mime-Version: 1.0 (1.0) Date: Wed, 3 Jan 2018 00:43:09 -0700 Subject: Re: Major Intel Memory Vulnerability Message-Id: References: <16BB4047-2DBC-44DE-9535-7A676E043A14@icloud.com> In-Reply-To: <16BB4047-2DBC-44DE-9535-7A676E043A14@icloud.com> To: Main PLUG discussion list X-Mailer: iPhone Mail (15C153) X-BeenThere: plug-discuss@lists.phxlinux.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Main PLUG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Main PLUG discussion list Content-Type: multipart/mixed; boundary="===============9157268393723370791==" Errors-To: plug-discuss-bounces@lists.phxlinux.org Sender: "PLUG-discuss" --===============9157268393723370791== Content-Type: multipart/alternative; boundary=Apple-Mail-43F3F31A-716A-4561-8FFC-96F6CC09D595 Content-Transfer-Encoding: 7bit --Apple-Mail-43F3F31A-716A-4561-8FFC-96F6CC09D595 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I read the performance hit for Intel chips will be %35 or so after the fix.=20= > On Jan 2, 2018, at 7:49 PM, Eric Oyen wrote: >=20 > so, does this mean that the UEFI might get patched first? OR, does the OS e= cology have to do so first? Lastly, how much of a performance hit will this r= epresent? >=20 > -eric > from the central offices of the Technomage Guild, the "oh look! yet anothe= r bug!" Dept. >=20 >> On Jan 2, 2018, at 3:39 PM, Matthew Crews wrote: >>=20 >>=20 >> https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/ >>=20 >> In a nutshell, it is a major security flaw in Intel hardware dating back a= decade that is requiring a complete kernel rewrite for every major OS (Linu= x, Windows, Mac, etc) in order to patch out. It cannot be patched out with a= CPU microcode update. Major enough that code comments are redacted in the p= atches until an embargo period is expired. Also the reported fix will have a= huge performance impact. >>=20 >> Also crucial to note is that AMD chips are not affected by this. >>=20 >> How the heck does something like this go unnoticed for so long? >>=20 >>=20 >>=20 >>=20 >> Sent from ProtonMail, Swiss-based encrypted email. >>=20 >>=20 >>=20 >>=20 >> --------------------------------------------------- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >=20 > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss --Apple-Mail-43F3F31A-716A-4561-8FFC-96F6CC09D595 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I read the performance hit f= or Intel chips will be %35 or so after the fix. 

On Jan 2= , 2018, at 7:49 PM, Eric Oyen <er= ic.oyen@icloud.com> wrote:

so, does this mean that the UEFI might get patched first? OR, does the OS e= cology have to do so first? Lastly, how much of a performance hit will this r= epresent?

-eric
from the central offices of the= Technomage Guild, the "oh look! yet another bug!" Dept.

=
On Jan 2, 2018, at 3:39 PM, Matthew Crews wrote:


https://www.theregister= .co.uk/2018/01/02/intel_cpu_design_flaw/

In a nutshell, it is a m= ajor security flaw in Intel hardware dating back a decade that is requiring a= complete kernel rewrite for every major OS (Linux, Windows, Mac, etc) in or= der to patch out. It cannot be patched out with a CPU microcode update. Majo= r enough that code comments are redacted in the patches until an embargo per= iod is expired. Also the reported fix will have a huge performance impact.
Also crucial to note is that AMD chips are not affected by this.
How the heck does something like this go unnoticed for so long?



Sent from ProtonMail, Swiss= -based encrypted email.




---------------------------------= ------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe= , unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman= /listinfo/plug-discuss

-----------------------------------------= ----------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
= To subscribe, unsubscribe, or to change your mail settings:
= ht= tp://lists.phxlinux.org/mailman/listinfo/plug-discuss
= --Apple-Mail-43F3F31A-716A-4561-8FFC-96F6CC09D595-- --===============9157268393723370791== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tClBMVUct ZGlzY3VzcyBtYWlsaW5nIGxpc3QgLSBQTFVHLWRpc2N1c3NAbGlzdHMucGh4bGludXgub3JnClRv IHN1YnNjcmliZSwgdW5zdWJzY3JpYmUsIG9yIHRvIGNoYW5nZSB5b3VyIG1haWwgc2V0dGluZ3M6 Cmh0dHA6Ly9saXN0cy5waHhsaW51eC5vcmcvbWFpbG1hbi9saXN0aW5mby9wbHVnLWRpc2N1c3M= --===============9157268393723370791==--