3 ms·
>So Intel failed to mitigate the vulnerability when it was first reported. Then they extended the embargo from May until November. And they still didn't fix it.
by coldtea 7y ago
>So Intel failed to mitigate the vulnerability when it was first reported. Then they extended the embargo from May until November. And they still didn't fix it.
The assumption being that they could in the time given, but are sitting on their hands?
- wolf550e 7y agoNo. This timeline shows incompetence, not sitting on their hands: https://mdsattacks.com/#ng-full-story https://mdsattacks.com/#ng-full-story
- coldtea 7y agoIncompetence as in "they're incompetent engineers", and if so, compared to what baseline? Or incompetence in as "they weren't capable of doing it"? The latter is very probable. The former could underestimate the difficulty of such fixes...
- yifanl 7y agoThe two statements are identical, competence is always within a given context.
- diffeomorphism 7y agoNo, the second is "incapable" and suggests that even a "great" engineer could not have done it. The first one says that a "competent" engineer could have. Big difference.
- yifanl 7y agoA great engineer can still be incompetent in the face of a difficult (or poorly specced) task.
- deleted 7y ago[deleted]
- coldtea 7y agoIt's precisely because "competence is always within a given context" that the two statements are not identical. Incompetent can mean "as to the particular project context" (i.e. they could be great engineers that din't manage to deliver the fixes for this issue), or "as to their general professional capacity" (i.e. they are lesser engineers).
- yifanl 7y agoFair point. I read both statements in the context of the particular hardware bugs Intel's trying to fix, but I can see how my comment is quite vague.