[CRTech] Christian Radio Tech [MSG 81646]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
Re: CPU security vulnerability
To: CRTech <crtech@crtech.org>
Subject: Re: CPU security vulnerability
From: Willie Barnett <wbradiolists@gmail.com>
Date: Mon, 8 Jan 2018 12:52:03 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=gcdzC9b7KcbbvHT4DXjRX2pnNOuHt6tXAn4bXi3xUNk=; b=pF5wDonviYvH2RqnP5icYoqpbgQmDq7RS/PjlURK5+SyzEffgqGMxIuCmbZNqMoO9i +v9RXU0GFZaFhBtQYxfVnAN8S/iL1qrHA2AiXJoo9NFuhKD13xMAo+FFfTbiyQdS2bsD 5YdPZqRGZdYaZedhUGYZH6Aq7tzHSkEgLsu6ThgusaD7AMdqIbn+ia5Da2qbISeweKAK GRuSSgyAIX+wrDGWKWNs668zZMWZHTvRYBr9NwX1N/p+efT6X2XCSIdtA8zABvep9dZO jCkTwhoIH7AbwEXqC1pNPiSfUj9qgIiAKxVyoiAIX/gWOsPbAEGFvrkX1jLIVfzfSPc/ ZczA==
In-reply-to: <2B4D9BC7-CD59-4B3B-8B7E-AEF3ADA2FB41@paravelsystems.com>
References: <CAOkhgWoMjjwszWXySMMGr=B=tDwe7xi2JHMBw0LsArEhLawk+A@mail.gmail.com> <CAOkhgWqy2to-JUQuJg=a0b5Djyg2YXBBJxKiCCzk1MD1RoEThg@mail.gmail.com> <2B4D9BC7-CD59-4B3B-8B7E-AEF3ADA2FB41@paravelsystems.com>
Although XP was "EOLed" some time ago, MS DID release a version of the WannaCry protection update for it. (I installed it into all of our machines ASAP with no issues.) I suspect that, due to the huge scope of THIS vulnerability, they just might do that again... seeing as they still have some limited security update support for XP that is used in Point of Sale systems, etc, by the millions.

If the performance "hit" is 5% or less, then that's fine, and probably not even noticeable. 30% would be VERY noticeable.

Eyes open and fingers crossed, as they say. ;)


On Mon, Jan 8, 2018 at 12:40 PM, Fred Gleason <fredg@paravelsystems.com> wrote:
On Jan 8, 2018, at 12:17, Willie Barnett <wbradiolists@gmail.com> wrote:
So now we can "look forward" to reducing the performance of our 3Ghz CPU's to about 2Ghz, to implement the current fixes... 
I think those are extreme “worst case” numbers. Based on my own testing plus the experience of others, it looks like a 0% - 5% degradation is a more realistic “real world” estimate. Not great obviously, but the world is by no means ending.
if they are even available for these machines or for WIN XP. :(
Presumably not, as the vendor end-of-lifed XP some time ago.  Code rot is a terrible thing...

References: CPU security vulnerability
(Willie Barnett <wbradiolists@gmail.com>, 8 Jan 2018 15:33:48 -0000)
Re: CPU security vulnerability
(Willie Barnett <wbradiolists@gmail.com>, 8 Jan 2018 17:18:04 -0000)
Re: CPU security vulnerability
(Fred Gleason <fredg@paravelsystems.com>, 8 Jan 2018 17:40:10 -0000)
Prev by date: RE: Re: CPU security vulnerability
(Gullikson, Brian F, 8 Jan 2018 17:50:54 -0000)
Next by date: Re: Re: CPU security vulnerability
(Willie Barnett, 8 Jan 2018 18:03:40 -0000)
Prev by thread: Re: CPU security vulnerability
(Fred Gleason, 8 Jan 2018 17:40:10 -0000)
Next by thread: RE: CPU security vulnerability
(Jon Foreman, 8 Jan 2018 18:20:57 -0000)