[CRTech] Christian Radio Tech [MSG 81647]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
Re: Re: CPU security vulnerability
To: CRTech <crtech@crtech.org>
Subject: Re: Re: CPU security vulnerability
From: Willie Barnett <wbradiolists@gmail.com>
Date: Mon, 8 Jan 2018 13:03:27 -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=pgPtlhg1LqTqPSQXMRKVQ47AbZR1LFZgPoyeiMwTajo=; b=sgh5IG9nS8rGKIqQAISTnXFsZtTZmXlqpMWBCFJ4HID8aQz4uPnl3JT2pT6ooqjPW+ 6UwvU5QmKzXIePcZtKy95DDycgjgFfU0qy1qkyuggsyfzwsXoHkM965WVool7yL99afd qBQw15zCu7ivbk4cvOD0QFtQO3RnvPU58EVvMRdvOAj1UT4ZhGj5oJNr+fE8XQU5UlOf xBPFdbUqXwMEyeDOoJj/vyx2HdDeJjlKRSF2PRffb4SSLhMro/pmvntlg1+E95K3nnY5 E3QMLy34vsGUELsKAZmE+EOFqjG66dBb2Cn70512XCE3LCcZaclFGLEAatosKNIZtdsi NyqA==
In-reply-to: <MWHPR07MB31173C559461BDB4BC845F95A9130@MWHPR07MB3117.namprd07.prod.outlook.com>
References: <CAOkhgWoMjjwszWXySMMGr=B=tDwe7xi2JHMBw0LsArEhLawk+A@mail.gmail.com> <CAOkhgWqy2to-JUQuJg=a0b5Djyg2YXBBJxKiCCzk1MD1RoEThg@mail.gmail.com> <MWHPR07MB31173C559461BDB4BC845F95A9130@MWHPR07MB3117.namprd07.prod.outlook.com>
Of course the sky isn't falling... note my closing sentence of my original post, below. ;)

Point 1 - We will be doing likewise, because, yeah... no choice. ;)

Point 2 - Hopefully, MS will make a patch for this, as they did for "WannaCry", due to its vast scope.

Point 3 - 30% would mean audio edit/conversion processes take that much longer to complete.

Point 4 - I believe most of these are Prescott core chips. ;)

As for "moving on"... $$$$!!?


On Mon, Jan 8, 2018 at 12:50 PM, Gullikson, Brian F <bfgullikson@unwsp.edu> wrote:

Personal opinion here:


·         I'm going to keep using my CPUs


·         I'm going to apply all security patches


·         I'm not going to fret about a 30% performance hit,


·         Willie, I can, however, understand how this performance hit could certainly be a bigger deal if you're trying to squeeze the last bit of juice out of that "perfectly adequate" P4…  Assuming it's a Northwood core, that's a chip whose architecture was first released to the retail market in January, 2002…  16 years ago…  Perhaps this performance-decreasing patch is simply the tipping point that makes your P4's no longer "perfectly adequate", and It might just be time to move on… 


In the end… God is on his throne, and the sky is not falling…




From: Willie Barnett [mailto:wbradiolists@gmail.com]
Sent: Monday, January 08, 2018 11:18 AM
To: CRTech <crtech@crtech.org>
Subject: [CRTech] Re: CPU security vulnerability


As we all know, we wrestle not against flesh and blood... Keep the prayer warriors armed and praying!



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: Re: CPU security vulnerability
("Gullikson, Brian F" <bfgullikson@unwsp.edu>, 8 Jan 2018 17:50:54 -0000)
Prev by date: Re: CPU security vulnerability
(Willie Barnett, 8 Jan 2018 17:52:14 -0000)
Next by date: Translator IDs
(Ben Barber, 8 Jan 2018 18:06:39 -0000)
Prev by thread: RE: Re: CPU security vulnerability
(Gullikson, Brian F, 8 Jan 2018 17:50:54 -0000)
Next by thread: RE: Re: CPU security vulnerability
(Mike Shane, 8 Jan 2018 21:41:14 -0000)