**Moritz Heiber** @moritzheiber · 2018-05-10T12:58:50Z

Moritz Heiber @moritzheiber

Moritz Heiber @moritzheiber

intel security heisenbug Show more

May 10, 2018, 12:58 · Amaroq · 0 · 1

**Moritz Heiber** @moritzheiber · May 10, 2018, 12:59

**Moritz Heiber** @moritzheiber · May 10, 2018, 12:59

intel security heisenbug Show more

**swiley** @swiley@octodon.social · May 10, 2018, 14:52

**swiley** @swiley@octodon.social · May 10, 2018, 14:52

@moritzheiber It looks to me like many people correctly interpreted it. I think modern computers are just very complex and it’s very easy to miss tiny things like that with almost no noticeable bugs.

**Moritz Heiber** @moritzheiber · May 10, 2018, 14:54

**Moritz Heiber** @moritzheiber · May 10, 2018, 14:54

@swiley do you have a reference?

Also, Intel is known for its shoddy documentation, and I was also mainly playing on the corporate double speak of the press release echoed verbatim in the article ☺️

(It also doesn’t help that this has been as is since roughly the late 80s, without any engineer at Intel (or the respective vendors) ever catching on)

**swiley** @swiley@octodon.social · May 10, 2018, 14:57

**swiley** @swiley@octodon.social · May 10, 2018, 14:57

@moritzheiber yes, openbsd wasn’t affected (probably because they tend to pay closer attention to detail) someone from hacker news (apparently the author of “JPC” a Java x86 emulator) thought it was clear and implemented it correctly himself.

**Moritz Heiber** @moritzheiber · May 10, 2018, 14:59

**Moritz Heiber** @moritzheiber · May 10, 2018, 14:59

@swiley thanks! I commend both for their diligence 👍