On 04/01/18 23:48, Carlos E. R. wrote:
On Wednesday, 2018-01-03 at 23:48 +0100, Yamaban wrote:
On Wed, 3 Jan 2018 19:45, Carlos E. R. <robin.listas@...> wrote:
Any method to know if /my/ processor is affected? It was bought several years ago. A list of exact processor models for looking in /proc/cpuinfo, perhaps.
AFAICT, if is has 'Core' in its name, its affected, as well as all other Processor models of the last 6 years at least, talk is going on on the older models, up to 10 years back is hit in certain models.
Core 2 Duo, so yes, I'm hit.
Check the better sources, e.g. the more serious computer publications or proven to be better informed sources on the internet on details.
Links will pop up in time :-)
Root cause is a 'accelerated' branch pre-execution, in other words, they dropped the security checks to gain speed.
Yes, that part I found out.
Intentionally? They forgot? Ineptitude? Did they really think they would not be found out? Sigh :-(
But..but...it's taken some 20-odd years to be "found out"! :-) BC -- Always be nice to people on your way up -- you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org