<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 2018-01-04 13:27, Patrick Lufundisu
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADb3FWfNDBdRUwpOhv9ZMfrvtE8BJg=Z4pBJRFj9Jhr1QOuJVQ@mail.gmail.com">
<div dir="ltr">
<div>Hi All,<br>
<br>
<a
href="https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/"
moz-do-not-send="true">https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/</a><br>
<a href="https://security.googleblog.com/"
moz-do-not-send="true">https://security.googleblog.com/</a><br>
<a href="https://meltdownattack.com/" moz-do-not-send="true">https://meltdownattack.com/</a><br>
<br>
</div>
Happy new year 2018 <br clear="all">
<div>
<div><br>
</div>
</div>
</div>
</blockquote>
<br>
CERT recommends replacing the CPU to fix these issues. Is everyone
frantically ripping CPUs out of servers/routers right now?<br>
<br>
<a class="moz-txt-link-freetext" href="https://www.kb.cert.org/vuls/id/584653">https://www.kb.cert.org/vuls/id/584653</a><br>
<br>
Solution<br>
Replace CPU hardware<br>
The underlying vulnerability is primarily caused by CPU
implementation optimization choices. Fully removing the
vulnerability requires replacing vulnerable CPU hardware.<br>
<br>
-Laszlo<br>
<br>
<blockquote type="cite"
cite="mid:CADb3FWfNDBdRUwpOhv9ZMfrvtE8BJg=Z4pBJRFj9Jhr1QOuJVQ@mail.gmail.com">
<div dir="ltr">
<div>
<div>-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Pat<br>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
afnog mailing list
<a class="moz-txt-link-freetext" href="https://www.afnog.org/mailman/listinfo/afnog">https://www.afnog.org/mailman/listinfo/afnog</a></pre>
</blockquote>
<br>
</body>
</html>