<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p><br /></p>
<p>I think they have a moral obligation to destroy all effected chips that are in the pipeline. Dell and others need to stop sales and not continue selling until the CPU is fixed.</p>
<p>This is much bigger than we know. Almost every computer is effected. The intermittent fix is software. What keeps some smart and devious person from creating an app that replaced the patch with their own and then they can drain your bank account... crash your automated or self driving car.... Yikes.</p>
<p>The real solution is a new generation of chips that are not exploitable. That means replacing every computer and device that is effected. </p>
<p>This should be a wake up call to all of us. We are way too dependent on computers.</p>
<p>There will be major fireworks over this. I can see a lot of companies getting sued. And the only ones that win are the lawyers. </p>
<p>This is going to be with us for years.</p>
<p>I have 7 computers that can be or already are connected to the internet. A lot of it is old technology, however it's value is in testing. I am a software developer. As long as I keep them on a private net I am ok.... Otherwise I will need to replace at least 2. </p>
<p>This is a potential nightmare.... Patching hardware with software is a weak plan. All that need to happen is some wise person to figure out how to replace the patch with their own. Say good by to our economy if that happens.</p>
<p>What a mess!!</p>
<p><br /></p>
<p><br /></p>
<div> </div>
<p><br /></p>
<p>On 2018-01-03 18:12, Matthew Crews wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored -->
<p>I would be more concerned IF the next gen CPU has this fixed. All's I know is that if Intel wants to fix the very next gen, they will need to scrap a lot of silicon that has already been finished.<br /><br /><br />Sent from <a href="https://protonmail.com" target="_blank" rel="noreferrer">ProtonMail</a>, Swiss-based encrypted email.<br /><br /><br /><br /><br /><br />-------- Original Message --------<br />On Jan 3, 2018, 15:35, Nathan O'Brennan wrote:</p>
<blockquote class="protonmail_quote"><br /><!-- meta ignored -->
<p>I'm more curious to know which versions of Intel's upcoming chips have been fixed already. I would like to upgrade my current workstation in the next year and will stick with Intel despite any performance impact over AMD.</p>
<p><br /></p>
<p><br /></p>
<p>On 2018-01-03 00:43, Aaron Jones wrote:</p>
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0;">
<div> </div>
<div>I read the performance hit for Intel chips will be %35 or so after the fix. </div>
<div><br />On Jan 2, 2018, at 7:49 PM, Eric Oyen <<a href="mailto:eric.oyen@icloud.com" rel="noreferrer">eric.oyen@icloud.com</a>> wrote:<br /><br /></div>
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0;">
<div>so, does this mean that the UEFI might get patched first? OR, does the OS ecology have to do so first? Lastly, how much of a performance hit will this represent?
<div> </div>
<div>-eric</div>
<div>from the central offices of the Technomage Guild, the "oh look! yet another bug!" Dept.</div>
<div><br />
<div>
<div>On Jan 2, 2018, at 3:39 PM, Matthew Crews wrote:</div>
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0;"><br /><a href="https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/" target="_blank" rel="noreferrer">https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/</a><br /><br />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 (Linux, 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 patches until an embargo period is expired. Also the reported fix will have a huge performance impact.<br /><br />Also crucial to note is that AMD chips are not affected by this.<br /><br />How the heck does something like this go unnoticed for so long?<br /><br /><br /><br /><br />Sent from <a href="https://protonmail.com/" target="_blank" rel="noreferrer">ProtonMail</a>, Swiss-based encrypted email.<br /><br /></blockquote>
</div>
</div>
</div>
</blockquote>
<br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace;">---------------------------------------------------<br /> PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" rel="noreferrer">PLUG-discuss@lists.phxlinux.org</a><br /> To subscribe, unsubscribe, or to change your mail settings:<br /> <a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank" rel="noreferrer">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a></div>
</blockquote>
<p><br /></p>
<br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">---------------------------------------------------<br /> PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" rel="noreferrer">PLUG-discuss@lists.phxlinux.org</a><br /> To subscribe, unsubscribe, or to change your mail settings:<br /> <a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank" rel="noreferrer">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a></div>
</blockquote>
</blockquote>
</body></html>