Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Friday January 19 2018, @01:39PM   Printer-friendly
from the tell-us-how-you-REALLY-think dept.

SoylentNews first reported the vulnerabilities on January 3. Since then, we have had a few stories addressing different reports about these vulnerabilities. Now that it is over two weeks later and we are *still* dealing with reboots, I am curious as to what our community's experience has been.

What steps have you taken, if any, to deal with these reports? Be utterly proactive and install every next thing that comes along? Do a constrained roll out to test a system or two before pushing out to other systems? Wait for the dust to settle before taking any steps?

What providers (system/os/motherboard/chip) have been especially helpful... or non-helpful? How has their response affected your view of that company?

What resources have you been using to check on the status of fixes for your systems? Have you found a site that stands above the others in timeliness and accuracy?

How has this affected your purchasing plans... and your expectations on what you could get for selling your old system? Are you now holding off on purchasing something new?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by ElizabethGreene on Friday January 19 2018, @02:46PM (2 children)

    by ElizabethGreene (6748) Subscriber Badge on Friday January 19 2018, @02:46PM (#624690) Journal

    This is a 2-day old press release from Intel.
    https://newsroom.intel.com/news/firmware-updates-and-initial-performance-data-for-data-center-systems/ [intel.com]

    “[…]As I noted in my blog post last week, while the firmware updates are effective at mitigating exposure to the security issues, customers have reported more frequent reboots on firmware updated systems.

    As part of this, we have determined that similar behavior occurs on other products in some configurations, including Ivy Bridge-, Sandy Bridge-, Skylake-, and Kaby Lake-based platforms. We have reproduced these issues internally and are making progress toward identifying the root cause. In parallel, we will be providing beta microcode to vendors for validation by next week.”

    I'm waiting to apply the Intel/Hp microcode updates to my PC until they get it sorted. The windows patches cover two of the three attacks. That has to be good enough for now.

  • (Score: 5, Insightful) by bradley13 on Friday January 19 2018, @03:04PM (1 child)

    by bradley13 (3053) on Friday January 19 2018, @03:04PM (#624699) Homepage Journal

    You have to love the "more frequent reboots". Their PR folks are being weasels. Say it together now: "system crashes".

    A rushed microcode update that causes the O/S to crash. That's going to be just buckets of fun to debug.

    --
    Everyone is somebody else's weirdo.