On 04/01/2018 05:06, Ronald F. Guilmette wrote:
In message <2347560.AJVtGcUuTT@elisha.atlnet>,
Joey Kelly <j...@joeykelly.net> wrote:
...
No, I mean their lame excuses, dances around the truth, claiming many other
platforms AND OPERATING SYSTEMS do it too. 'Tain't so. This is hardware, INTEL
hardware, and not an OS problem...
While it is clearly true, even from the current very preliminary reports, that
this is indeed a hardware issue, rather than an OS issue, you may want to
reserve
judgement about the possibility that this thing is confined only to Intel
hardware.
Intel, of course, has said that they believe that this bug may also affect
AMD and also ARM CPUs. (But then they would say that, wouldn't they?) But
AMD, for its part, has already put out a public statement saying that their
CPUs are not affected.
So now, the other shoe that we should all be expecting to drop, any time now,
is some public statement from ARM Holdings, PLC. If one has already been issued
by that company, then Google News doesn't seem to be giving me any easy way to
find it, and there is nothing of relevance on the ARM corporate web site
(www.arm.com). So I suspect that they haven't said anything yet, which is
itself a rather ominous data point.
They already have:
https://googleprojectzero.blogspot.co.uk/2018/01/reading-privileged-memory-with-side.html
If it turns out that this same bug, or same sort of bug, also affects ARM-based
chips, then that is quite possibly an even bigger deal than the already obvious
Intel cataclysm.
Regards,
rfg
_______________________________________________
freebsd-security@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org"
