Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think you are confusing security and safety. Security is about dealing with malicious attackers, while safety is about making sure random events and mistakes won't kill you.

Your example with the brakes is about safety, i.e. making sure the car won't kill you during normal operation. Normally, unless their CPUs start bursting into flames, this is not a problem for Intel.

The problem here is about security. A car analogy would be that to start your car, you need a code and that code can be found by measuring how long it takes to process the input, making life easier for thieves.

As for liability, I don't think you can be liable in court if you didn't plan for something that wasn't known at the time and isn't trivial.



Ironically, isn't your analogy a literal thing?

http://www.bbc.co.uk/news/business-41367214


As for liability, I don't think you can be liable in court if you didn't plan for something that wasn't known at the time and isn't trivial.

Engineering brakes that work reliably over months and years of use isn't trivial.

Process isolation and kernel security issues have been known for decades and have been fundamental design requirements for decades.




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

Search: