|
|
Paging SteveH.
|
"So there."
|
Caused by Intel hardware.
|
And?
|
I thought, for a moment, you were having a dig at Macs in general.
|
|
There's no evidence of what actually happens to an OSX system if it is
hacked, though.
|
It runs on my Windows XP machine using VMWare quite happily. Oh hang
on, perhaps you didn't mean that kind of hacking.
|
|
That wasn't why I posted it... it was more a folow on from your
"wireless is secure" post.
|
Oh, right.
I didn't actually say that wifi is secure, just that I couldn't really
see the issue if you were operating on a VPN over wifi.
I mean, wifi can be turned on on our machines, it's just that we can't
tweak the network settings, meaning it's useless. But it means the
machines could still be open to hackers. IYSWIM.
|
|
|
Nope - caused by an apple mac (and windows) device driver, i.e. a bit of
software that almost certainly sits inside ring zero, which means the
ability to run arbitary code with kernel privilages.
Device drivers for the same peripheral chip but different OSes /
processors are often very similar, as they're based on standard
frameworks. You write the core of the driver, and then just plug it in
to the correct interface layer for the OS, and compile it for the
correct processor.
Often, these stages are done by completely different companies - the
chip manufacturer provides binary lumps that the OS writer or final
product manufacturer then links to the interface layer, using an API
document that was 'finished' six months before the final design of the
hardware was, which itself was produced before the industry standard was
finalized: "but that's OK, we'll be able to correct any probelms with a
firmware update that the user can download".
|
I'd also note that the demo wasn't given 'live' - it was a video
recording, so we don't actually know if it exists or not.
|
|
|