Virtualization

Architecture All Access: Live at Lunar Lake ITT: Architecting Next Gen Security



Architecture All Access is a master class technology series, featuring Senior Intel Technical Leaders taking an educational …

[ad_2]

source

Related Articles

7 Comments

  1. If you cared about security, you would not allow branch prediction, and you would not allow ANY updates to firmware, it would be purely hardware. Stop using Field Programmable Gate Arrays. Encryption and virtualization are just bad for performance and recovery of data, they don't actually help, and are not required at all. Virtualization just makes everything slow. USERS should have full control over their machines, but instead you only allow Linux and Microsoft to control encryption signing what the processor does at a deep level, and this results in spyware backdoors built by governments. I don't trust your PARTNERS to control my machine. I will never buy another Intel Chip.

    JUST HARD WIRE THE FIRMWARE INTO THE CHIP. AND STOP TRYING TO CHANGE IT AFTER YOU SHIP. That would make every one of these "features" irrelevant. I don't want ANY encryption. It does more harm than good, and you are creating monopolies of Operating System manufacturers. If I want to write my own operating system, You, INTEL are stopping me with these "features." This should be considered illegal Monopolistic cartel collusion. Intel should face an Antitrust Lawsuit, because Intel is locking down everyone's machines and only allowing access to their Partners, which could be Russia and China for all we know, Whoever pays them for access will probably get it.

  2. If you cared about security, you would not allow branch prediction, and you would not allow ANY updates to firmware, it would be purely hardware. Stop using Field Programmable Gate Arrays. Encryption and virtualization are just bad for performance and recovery of data, they don't actually help, and are not required at all. Virtualization just makes everything slow. USERS should have full control over their machines, but instead you only allow Linux and Microsoft to control encryption signing what the processor does at a deep level, and this results in spyware backdoors built by governments. I don't trust your PARTNERS to control my machine. I will never buy another Intel Chip.

    JUST HARD WIRE THE FIRMWARE INTO THE CHIP. AND STOP TRYING TO CHANGE IT AFTER YOU SHIP. That would make every one of these "features" irrelevant. I don't want ANY encryption. It does more harm than good, and you are creating monopolies of Operating System manufacturers. If I want to write my own operating system, You, INTEL are stopping me with these "features." This should be considered illegal Monopolistic cartel collusion.

  3. If you cared about security, you would not allow branch prediction, and you would not allow ANY updates to firmware, it would be purely hardware. Stop using Field Programmable Gate Arrays. Encryption and virtualization are just bad for performance and recovery of data, they don't actually help, and are not required at all. Virtualization just makes everything slow. USERS should have full control over their machines, but instead you only allow Linux and Microsoft to control encryption signing what the processor does at a deep level, and this results in spyware backdoors built by governments. I don't trust your PARTNERS to control my machine. I will never buy another Intel Chip.

    JUST HARD WIRE THE FIRMWARE INTO THE CHIP. AND STOP TRYING TO CHANGE IT AFTER YOU SHIP. That would make every one of these "features" irrelevant. I don't want ANY encryption. It does more harm than good, and you are creating monopolies of Operating System manufacturers. If I want to write my own operating system, You, INTEL are stopping me with these "features." This should be considered illegal Monopolistic cartel collusion. Intel should face an Antitrust Lawsuit, because Intel is locking down everyone's machines and only allowing access to their Partners, which could be Russia and China for all we know, Whoever pays them for access will probably get it. If you wanted to actually protect firmware, IT WOULD NOT BE FPGA, IT WOULD BE HARD CODED IN CIRCUITS.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button