[tomku]

...and if the article's claims aren't true, there wouldn't be any sources to confirm the claims at all. The evidence we've been presented with so far (no sources) is consistent with both possibilities. When you make a claim as big as SemiAccurate did, it's on you to provide sources to back it up. If you can't present any kind of proof, you don't have a story, you have a rumor.

[walterbell]

The article claimed:

> That is the end of June for non-Intelspeak people, they will officially issue this guidance then along with OEM disclosures.

We'll know in two months whether the above claim is true or false.

[tomku]

My prediction: At the end of June, Intel announces a fix for a minor non-RCE bug in the LAN code of Intel ME. SemiAccurate proudly and inaccurately announces that it confirms their previous reporting and adds it to the list of things to mention every time they write an article about Intel. There is no follow-up Hacker News thread with 100+ comments, so most of the people who posted here continue thinking that there was a major RCE in Intel ME that we just haven't heard about because it was covered up.

Edit: Already proven wrong! We're headed for interesting times.

[Natanael_L]

https://security-center.intel.com/advisory.aspx?intelid=INTE...

Looks like an almost full confirmation. They're saying consumer hardware is unaffected, but everything else matches.

[tomku]

Yeah, I blew that prediction pretty badly. Congrats to SemiAccurate on the huge scoop!

[tchaffee]

Then it's a rumor. One you probably want to keep your eye on. Which was the whole point of the article anyway.