• BananaTrifleViolin@piefed.world
    cake
    link
    fedilink
    English
    arrow-up
    57
    ·
    26 days ago

    The headline is a little misleading: the feature has disappeared from consumer chips but AMD is not responding when asked why. As the article itself says: it’s not clear if this is a deliberate decision, or a bug that has caused this issue.

    The headline implies it was a deliberate action. Maybe it was, but at the moment we don’t really know. But it is good that Toms Hardware is writing about this and drawing attention to this issue. It’s concerning regardless of the reason, and it’s also concerning how cagey AMD is being about addressing this issue.

  • unexposedhazard@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    26 days ago

    The article isnt very clear on this, but did they actually remove a critical feature from already sold products? Surely they can be sued for that?

  • BaraCoded@literature.cafe
    link
    fedilink
    English
    arrow-up
    9
    ·
    26 days ago

    It’s funny how every big tech decision these last few years all sound like a shitty James Bond villain step in a shitty world domination plan, with shitty corpo writing.

  • Sir. Haxalot@nord.pub
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    26 days ago

    Hold up, since when did consumer Ryzen CPUs have memory encryption support? I was sure that was always a EPYC exclusive feature.

  • Barbecue Cowboy@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    3
    ·
    26 days ago

    It feels weird this was even ever a standard consumer feature. I wouldn’t even really expect it on enterprise hardware outside of servers. This feels like stuff you only really need to think about if you’re being directly targeted by a group with resources.