A chrome book in fancy clothes?
Very true and not always a lot lower, depending on who has it but that’s the security world. It is an arms race and espionage.
1 Like
Like the $1,000 Chromebook Pixel (which has only 32GB of storage)? Kind of… but the Pixel has two USB-C connectors.
“Galileo” and “Figaro” are still available, I believe.
1 Like
(At least in the post-Snowden world I am not looked at as paranoid anymore…)
The targeting differs, though. Luckily no one (almost) will waste a good zeroday on a blanket attack. These things are typically aimed at specific targets. Which makes them better (for the rest) and worse (for the target)…
A way could be strict compartmentalization of processes on the machines, strict separation between data and executable code, defensive coding practices. Ideally, formal verification of the code.
And even then the hardware peculiarities may allow breaking out from the sandboxes. (Rowhammer, I am looking at YOU.)
A supportive way is architecture facilitating easy auditing. The owner/possessor of the machine should be able to inspect the processes and files and to check their integrity and behavior.
But I don’t see any of that getting wider deployment in any near future, albeit sandboxing for apps and extensions and javascript code is fairly common now… Maybe in special applications…
This topic was automatically closed after 5 days. New replies are no longer allowed.
