Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

Hi Felix Ok, I now understand your points. You have right, with the Firefox case; and this is GOOD NEWS for the SECURITY. AND if you argue with the one direction of microcode updates YOU have also right. ;) But who (which tech.) can/will stop a clever hacker doing forward updates on the

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

> I’m very very sorry, that you think I’m NOT understanding „Specter" and > what this shows. - I understand this very well! ;) > > *FOR YOU:* > *== > * > PLEASE look at the possibilities of the new *version 57.0.4 of Firefox*. > *With this special created release (of this browser) you can

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

I’m very very sorry, that you think I’m NOT understanding „Specter" and what this shows. - I understand this very well! ;) FOR YOU: == PLEASE look at the possibilities of the new version 57.0.4 of Firefox. With this special created release (of this browser) you can PATCH the Microcode

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

Sorry it’s NOT enough. Don’t worry I trust Intel for changing Intel CPUs; I trust AMD for changing AMD CPUs, etc. NO problem with that! - But SIMPLYFYED: How can Firefox 57.0.4 change the Intel CPU/MMU - Microcode if such change need a secret code signature and don’t know anything secured from

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

*Sorry it’s NOT enough.* Don’t worry I trust Intel for changing Intel CPUs; I trust AMD for changing AMD CPUs, etc. NO problem with that! - But SIMPLYFYED: How can Firefox 57.0.4 change the Intel CPU/MMU - Microcode if such change need a secret code signature and don’t know anything secured

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

*Second:* I’m not willing to accept, that CPU/MMU - Microcode can be changed just by some OS/SW-Updates *without* any physical and local interventions or with *a secret „ONE WAY“* passwords/ticket *directly coming from the manufacture company*. Otherwise "very bad hackers" are able to change

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

On Sat, 6 Jan 2018 13:32:30 +0100 Patrik Lori wrote: > > If Intel, AMD, ARM, .. now communicating, that they can change the CPU/MMU-Microcode outside there secured factories; they send (with this) very dangerous messages to all hackers. > > Hackers can use "the same

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

STOP, STOP, STOP -> ALL THIS "Microcode-Patch" Infos! = If Intel, AMD, ARM, .. now communicating, that they can change the CPU/MMU-Microcode outside there secured factories; they send (with this) very dangerous messages to all hackers. Hackers can use "the