You just contradicted yourself. First you seem to want us all to give Intel a free pass and not blame them nor should they fix their own problems. It should be Apple an others who fix it. Now you are saying oh wait others like Apple should not be held liable.
Which is it?
For your last part, I am not contradicting myself. I was replying to sentiment that an average employee in sales should be knowledgable in the impact of all vulnerabilities and fixes on performance of a product. That is really impractical, because there are so many fixes and vulnerabilities that it is really impossible to gauge, and keep track on a day to day basis. The guys in sales are not technical experts, and likely do not have the background to understand or properly respond to questions in this area. In a perfect world, everyone would be infinitely knowledgable on this subject, and they would be able to respond effectively.
You talk such BS.
The only reason these vulnerabilities slipped through is because Intel and companies like them think they are clever and intelligent and in a actual fact many people working for them are arrogant and dumb! They failed to check at all and security can be baked into hardware if you so see fit to and do so with the right approach.
Just look at the secure element in the iPhone 5s onwards.
You may say oh well how do we know that it is secure? We only have Apple's word for that plus if someone had cracked it they would not tell the world about it? They would exploit it, keep it secret.
So much like the person who discovered Apple's Root password bug in Mac OS? They kept it secret didn't they? oh and all the other bugs found in IOS/Mac Os etc?
[doublepost=1515758568][/doublepost]
It was negligence because Intel failed to check their products properly or at all. When I use to design and build PCs I did not just put the dam things together and hope for the bets, oh and then swan around telling everyone how my PC is the best around. How it is awesome and use many many but words and phrases.
I checked it, I did something called quality control.
At every step of the design and build process I would check, check and recheck. These vulnerabilities are not just some minor issue like you seem to suggest. They are major as they allow hackers the ability to basically gather a load of data that would be useful for further exploits.
I am tired of people like you making excuses for when firms as big as intel screw up and we are all expected to get on our knees and suck their ****s just to make you happy!
I say intel can not just shrug it's dam shoulders and say oh well and hey pretend it never happened.
Also not talking BS here. The fact that vulnerabilities can be continually mined out of software and hardware is a source of revenue for security research companies. This isn't exclusive to Intel, products from Apple, Microsoft, Google, and pretty much every tech firm under the sun have vulnerabilities in them to this day. The ongoing process of discovering those vulnerabilities is a job unto itself.
What makes it seem like I'm talking out of my ass is that you don't understand how these vulnerabilities are discovered. There's often a lot of time and effort during production time put into unit testing each aspect of code or a subcomponent of a processor. Often the firm doesn't have time to test every single possible case between the extreme edge cases, and the in-between cases can lead to unexpected output, that may or may not lead to a vulnerable state. If it leads to a vulnerable state, the firm is notified by the researcher / research firm and a patch is developed and then released to the public.
Want an example of a research firm? Zero Day Initiative. They are badass, and I have worked with them in the past.
Want to see examples of how many vulnerabilities are in the pipeline from just this firm alone?
http://www.zerodayinitiative.com/advisories/upcoming/ - here there are 10 vulnerabilities for Apple products in the pipeline already.
You obviously had no understanding of the research community. I hope this enlightened you.