Hacker News Reader

Comment by dboreham | Hacker News Reader

> And it all got caught because of a fairly obvious perf regression

Always possible that was "parallel construction" evidence.

Someone at a TLA discovered the attack by some other means, had a quiet Signal chat with a former colleague who works at MS...

View on HN

It seems like a much more suitable parallel construction story to invent in this instance would be something like "there were valgrind issues reported, but I couldn't reproduce them, so I sanity checked the tarball was the same as the git source. It wasn't."

Wouldn't it have been easier to just have someone drive-by comment on the changes in the source tree in the comment? Like "what's up with this?"

Though I guess you end up with some other questions if it's totally anonymous. But I often will do a quick look over commits of things that I upgrade (more for backwards compat questions than anything but)

Interesting possibilty but it seems like the "discovery" story is too complex and unbelievable.

There doesn’t seem to be any evidence to support this whatsoever yet it’s nearly impossible to disprove. Classic conspiracy theory.

There also isn't really a reason for some contrived parallel construction here - whoever found the issue could just point to it without explaining how it was detected. They could even do that anonymously.

> Classic conspiracy theory.

I would not be too quick to shit on "conspiracy theories" however as there are plenty of proven cases of people conspiring against the interests of the public.

Reply on news.ycombinator.com