well, that was a known factor well ahead of time. This situation is different. Intel KNEW there might be a problem with this method of memory processing. They just didn't know how big a problem it could turn out to be. And all of these chips are in everything from routers, to servers to switches and even devices used in the smart home. That is slightly more than $3 trillion worth of infrastructure and commodity equippment that many consumers have bought since then. This includes smart phones (which can be as expensive as $1,000 a throw). That's a hell of a lot of exposure that Intel will have to deal with and they don't have nearly enough capital to even touch a small part of this mess.
from the central offices of the Technomage Guild, "The world does not die with a bang, but a whimper" dept.
On Jan 5, 2018, at 12:06 PM, Victor Odhner wrote:
> So, Eric — You don’t think Y2K had consequences?
> It just happened to be a raft of stupid bugs that the industry dealt with in time.
> I was coding around Y2K bugs as early as 1979, as were lots of other people, just matter of factly planning on Y2K, but some of the older and more primitive stuff wasn’t being looked at until the late 1990s, and lots of production lines would have gone nuts.
> As for how much damage this year's vulnerability will do, yeah, strap in for the ride. Hopefully it will help people think about Internet of Things. (Banned from my house, as much as possible, but I can’t control my Vizio TV.)
> And self-driving cars are going to be scarey, but I’ll need a driver in another 10 years if I’m still around. I might already be more dangerous behind the wheel than a compromised automatic driver . . . . But I agree with Stephen, at least they need an air gap between the Internet and the robotic driver.
> Even then, some rich kids *will* get kidnapped on the way to school by their hacked chauffeur-bots, it’s bound to happen, too obvious. And remember the TV series “Extant,” where the top robotics guy was assassinated by the central computer which locked him in his car on the railroad track. (I’m sorry, Dave….)
> On 20180105, at 11:27, Eric Oyen <firstname.lastname@example.org> wrote:
> oh boy. This sounds like another Y2K problem, only this one has some reality about it and real consequences.
> from the central offices of the Technomage Guild, Truth or Consequences Dept.
> PLUG-discuss mailing list - PLUGemail@example.com > To subscribe, unsubscribe, or to change your mail settings: