1. 1

  2. 3

    Stop running XP.

    1. 1

      Sadly, one can assume they’d be sued if they remotely disabled XP systems’ internet connectivity.

      1. [Comment removed by author]

        1. 1

          Does not appear to have worked for the last three years :(

      2. 1

        Tell that to the poor bastards with XP systems running large and un-upgradeable pieces of medical equipment.

        1. 3

          And/or stop exposing your life supporting medical equipment’s SMB shares to the internet.

          I can understand the embedded argument. But such systems should remain embedded. I’m like 99% certain it would be very bad for my printer to be connected to the internet, and so, surprise twist, it’s not connected to the internet.

          Dribbling out these patches, post EOL, just reinforces the notion that if you sit on your ass long enough, someone else will come along and solve your problems for you.

          1. 1

            Well, yes. But this is on the vendors, not necessarily on Microsoft, still less on the overworked IT staff at Mount Sinai Hospital or wherever.

            1. 1

              Yeah, i’d like to see more attention to that. MS was pretty upfront about XP. In ten years this is dead. So did the company making the MRI machine ignore that? Or did the hospital buying the MRI machine ignore the notice from the vendor? Or is this more of some IBM SAP consulting project?

              I get that the hospital didn’t sign up for a giant ongoing IT burden, but the same applies to buying a cesium breeder reactor or whatever they use in radiology. Those things have significant maintenance requirements and fixed lifetimes, etc. Seems like software slipped through the hazardous waste regulations.

              1. 2

                This is sort of a white whale for me, but I wonder if a change to the liability regime around software could get some attention paid to these sorts of potential disasters before the North Koreans pull the trigger again.