AMD will reinstate memory encryption on Ryzen 9000 CPUs through a BIOS update in July — TSME is coming back after 'valuable community feedback'

3 days ago by sanitation to c/privacy

The feature was quietly removed through a firmware update on some non-PRO Ryzen CPUs.
load all comments
tiramichu 41 points 3 days ago

It really should be illegal to remove via updates any feature of a product which was present at the time of purchase.

path: 0 24345164, hotness: undefined, score: 41, children: 5
AwesomeLowlander 14 points 3 days ago

Usually yeah, but to my understanding this feature was only advertised in their Pro version of the chip. I suspect it got enabled by mistake in the consumer version and nobody really noticed until now.

path: 0 24345164 24345457, hotness: undefined, score: 14, children: 4
Redjard 7 points 3 days ago

Earlier article mentioned it was acknowledged by high ranking amd officials multiple times over the years.
So they definitely knew.

It might have been that it wasn't documented internally and someone else removed it not knowing it was in use.
But at the latest with the initial bug report this was clear, at that point it did reach people who knew. So not undoing it, especially given the severity of the impact of silently disabling a security feature, is absolutely on amd with no excuse.

path: 0 24345164 24345457 24347679, hotness: undefined, score: 7, children: 2
AwesomeLowlander 3 points 3 days ago

Could you link the article? The one I've seen is the Ars Technica one, which mentions an engineer. That doesn't mean he knows which features are supposed to not supposed to be commercially available, just what they actually do ship with. Left hand not knowing what the right is doing, basically.

Edit: I assume you're referring to this paragraph -

Kilpatrick went on in the thread to remind Lendacky that in 2020, the engineer had confirmed TSME was supported on a Ryzen 3700X (a consumer CPU).

Nothing there makes me think differently. Engineer says that yes, the hardware supports it (because it does). Only later does somebody realise that no, the hardware actually isn't supposed to be supporting it, they forgot to turn it off. Technical vs business.

It's even suggested at the end of the Ars Technica article as one of the most likely reasons for the issue.

path: 0 24345164 24345457 24347679 24347855, hotness: undefined, score: 3, children: 1
veniasilente 1 point 3 days ago

At least here in my country we have a sort of "third time's the charm" law. If something is allowed or let go despite being notified or complained about a third time, it's understood that this allowance is (and, more importantly, was) intended de facto. AMD got more than enough notifications and time to deal with what was going on. Even more before the release of the products.

path: 0 24345164 24345457 24351565, hotness: undefined, score: 1, children: 0
privacy
privacy

@lemmy.dbzer0.com

login for more options
5806
1095
2486

Welcome! This is a community for all those who are interested in protecting their privacy.

Rules

PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!

  1. Be civil and no prejudice
  2. Don't promote big-tech software
  3. No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
  4. No reposting of news that was already posted
  5. No crypto, blockchain, NFTs
  6. No Xitter links (if absolutely necessary, use xcancel)

Related communities:

Some of these are only vaguely related, but great communities.

go to feed...