On Wed, Jan 20, 2016 at 12:55 AM, Alberto Salvia Novella <es204904...@gmail.com> wrote: > Joel Rees: >> >> Just for the record, if microcode can play with the CPU internal >> system state, say, the bits that specify whether the CPU is in >> supervisor or user state, there's not much to stop, for instance, a >> microcode update from providing an undocumented trap to a hidden >> routine in the BIOS that does deep packet inspection and arbitrary >> forwarding. > > > http://security.stackexchange.com/questions/29730/processor-microcode-manipulation-to-change-opcodes >
Other than some significant errors in that, how do you interpret it? It supports neither your peculiar assertion that microcode is not executable nor your equally peculiar assertion that microcode is not and has not been a cause for concern. -- Joel Rees Be careful when you look at conspiracy. Arm yourself with knowledge of yourself, as well: http://reiisi.blogspot.jp/2011/10/conspiracy-theories.html
