What I meant was exactly that, which you corroborated as correct. You’d first have to already compromise these systems, as well as exploit this vulnerability.
Gosh, it’s not easy getting my point across here today, I’m sorry.
All I’m saying is that I don’t think AMD is doing this to us, on purpose. I think it’s just happened, and they’re not handling it very well, even though it’s somewhat understandable. At least to me. 🤷♂️
But then again, I have no reason to be attacked or have my system compromised, so my situation is better than others’, perhaps.
Grippler@feddit.dk 5 weeks ago
I think what most people disagree with, is that the active choice from AMD to not fix a very fixable issue, is a choice they know leaves customers is a seriously bad position. This is something they choose to do to their customers, because they could just as well choose to help them.
victorz@lemmy.world 5 weeks ago
I think that’s what I have a hard time believing. If they could “just as well” help, it is my belief that they also would. Because I don’t think they’re morons. I think they know this hurts their reputation. There has to be some obstacle, be it financial or lack of man power or… something. That is my belief.
Don’t you (all) think that sounds more likely than them just leaving their customers in the dark for no other reason than not having to do work?
Grippler@feddit.dk 5 weeks ago
Of course there’s a financial reason, they’ve done a cost}benefit analysis and decided that it’s financially better to screw over those customers than to spend money fixing it. But that’s exactly the issue!
victorz@lemmy.world 5 weeks ago
I mean… 🤷♂️ The analysis is made, decision made. I probably have an affected system but… What’s the real risk for private end users? Should I really be so concerned?