4 ms·
Intel tried to do the right thing three times: https://en.wikipedia.org/wiki/Intel_iAPX_432 https://en.wikipedia.org/wiki/Intel_iAPX_432 https://en.wikipedia.
by nickpsecurity 10y ago
Intel tried to do the right thing three times:
https://en.wikipedia.org/wiki/Intel_iAPX_432 https://en.wikipedia.org/wiki/Intel_iAPX_432
https://en.wikipedia.org/wiki/Intel_i960 https://en.wikipedia.org/wiki/Intel_i960
https://www-ssl.intel.com/content/dam/www/public/us/en/documents/white-papers/intel-itanium-secure-white-paper.pdf https://www-ssl.intel.com/content/dam/www/public/us/en/docum...
Backward compatibility with insecure apps, language, and OS features above all else is what market said. That plus raw speed. The above projects collectively cost Intel over a billion dollars that they didn't make back. i432 died for sure. i960 is in legacy mode with security features turned off or removed. Itanium is in downward spiral. Realistically, they should just modify x86 to support C safety like Cambridge's CHERI or other group's Hardbound are doing. Then, they get compatibility + safety.
They're probably just too afraid to make another attempt after loosing a billion to a market that said "F* security or software maintenance." Giving them the insecure crap they demand is actually the ethical choice in capitalism given they'll put you out of business otherwise. Only two that ever made it with a Right Thing approach were Burroughs B5000 and System/38 (aka AS/400). Both turned off hardware security due to user demand (performance over security) but kept OS architecture. Both still sell.
- slededit 10y agoThey are making some more attempts with MPX. https://en.wikipedia.org/wiki/Intel_MPX https://en.wikipedia.org/wiki/Intel_MPX
- nickpsecurity 10y agoIt's just an extension for one problem. A good thing that's happening. It's not a solution to a bunch at once. They're not risking it. Maybe they'll do it incrementally over time.