• ColeSloth@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    42
    arrow-down
    1
    ·
    1 month ago

    If it’s deliberate and not put back, there’s also the possibility the government made them remove it and not disclose why. So they can continue to access certain info and back doors and this security was giving them issues.

    The government forced email providers to have a backdoor for them. It’s the NSA’s PRISM program. Been around since at least 2008.

  • NarrativeBear@lemmy.world
    link
    fedilink
    English
    arrow-up
    29
    ·
    1 month ago

    YSK: This feature was disabled with a pushed firmware update.

    Its true it was “not supported”, but the CPU was/is capable of it.

    The big issue here is did AMD disable it accidentally, or did they do it intentionally. If it was intentional why did they not announce it anywhere in the update notes, or anywhere else?

  • M0oP0o@mander.xyz
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    1 month ago

    Create the problem, sell the solution situation?

    Or just enshitifcation?

  • unexposedhazard@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    16
    ·
    edit-2
    1 month 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?

    • MalReynolds@slrpnk.net
      link
      fedilink
      English
      arrow-up
      16
      ·
      1 month ago

      Eh, it protects against a certain class of attack when the attacker has physical access e.g. reading memory with memory probes while the computer is (still) on to get passwords etc., i.e. sophisticated attackers like customs, FBI. If they have physical access you’re probably hosed anyway, but if you have the presence of mind to shut the machine off (not sleep, hard off if needed) memory encryption becomes irrelevant.

  • Barbecue Cowboy@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    7
    ·
    1 month 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.

    • raldone01@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      1 month ago

      It seems like it is not a lot of overhead if any at all. Also the hardware design easily accommodates it. So why not if the work is already done?

      • tempest@lemmy.ca
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 month ago

        There is still some overhead. Enough that if you are doing HPC and running on your own hardware you might want want to disable it.

        I’ve disabled it on epycs for this reason but never touched it on ryzens.

      • Barbecue Cowboy@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        1 month ago

        I mean yeah maybe, this one is focused on protecting from threat actors with physical access which is kind of another level.