Hacker News new | past | comments | ask | show | jobs | submit login

This sure smells like misdirection!

I've no pity for devs that end up getting ruined because they didn't know what to do. It's like going too fast on a freeway you don't normally take, getting pulled over and trying to explain that you didn't know. You knew better. Ignorance is no excuse.

Ridicule is absolutely an effective response to companies who have put MILLIONS, literally MILLIONS of people in fiscal and possibly even physical danger. There's absolutely no room for error when it comes to safety for the users, and a tweet saying "Oh yeah, well uh we take opsec real real serious" doesn't cut it.

Of course they take security seriously, I mean obviously. But the point of the article that this article is responding too is that it doesn't matter if apologize after something that could've been prevented, it's too late.




You're assuming that all security issues are obvious known ahead of time, and that's clearly not true. You can't compare your average remote code execution vulnerability with a speed limit. Speed limits are posted; RCEs typically aren't as clearly documented ;)


I'm assuming that a hundred million users aren't made vulnerable by sheer wizardry. In all of the cases that the original article listed, I'd bet my salary that there was oversight in terms of the critical components or the architecture. RCE should not be enough to make that kind of dent, there should be more security there.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: