251–260 of 265 posts
Earlier quoted context omitted.
> Essentially you pick what fields in complex (maybe even nested) data structures to sort by, in what order, and the system makes a sort. Wait, is that it? What makes this novel?
What's novel is projecting that operation efficiently into a field where radix sort can operate on all the discrimination at once.
Weirdly, the paper isn't much discussed alongside the usual contenders. (WOOT, Logoot, RGA, LSEQ, etc.)
[1]: https://ai2-s2-pdfs.s3.amazonaws.com/6534/c371ef78979d7ed84b...
Earlier quoted context omitted.
You can not. The point is you cannot run the code of a compiler, you have to run the compiled binary. And there's no way to verify if the binary does the same thing as the code when the Ken Thompson Hack is implemented.
Aren't there C interpreters still around?
Earlier quoted context omitted.
> they installed themselves in the hard drive firmware, then hid the sectors where the exploit code was stored even from the BIOS. Where can I read more technical details (such as code analysis) about this? I've never heard of anything like this hiding for 10 years before.
https://www.symantec.com/content/en/us/enterprise/media/secu...
The un-named nls_933w.dll responsible for modifying firmware on "over a dozen" HDDs is only termed as Stuxnet-like however: https://securelist.com/equation-the-death-star-of-malware-ga...
That's remarkably impressive though.
HDDs aren't impenetrable walls - http://spritesmods.com/?art=hddhack - but reflashing firmware on over a dozen disks, presumably from Windows... nice.
Earlier quoted context omitted.
https://www.symantec.com/content/en/us/enterprise/media/secu...
Okay, that was interesting reading. Now I actually know what Stuxnet did and how it worked. The un-named nls_933w.dll responsible for modifying firmware on "over a dozen" HDDs is only termed as Stuxnet- like however: https://securelist.com/equation-the-death-star-of-malware-ga... That's remarkably impressive though. HDDs aren't impenetrable walls - http://spritesmods.com/?art=hddhack - but reflashing firmware on over…
Sure, it costs billions. But to a nation-state, billions are easy to find.
This is why modern security tools and practices are really only going to be capable of keeping out criminal organizations and mass-hacks. If a nation-state decides to target you, there is really no way you can defend against it. Often they are able to undermine the trust mechanisms in place through sheer resource asymmetry (they have the compute resources to brute-force SSL key collisions -- they did this with Stuxnet to fake a Microsoft signing cert to push the payload via a MITMed Windows Update).
There are even reports of three-letter-agencies intercepting routers during shipment, desolderig chips from the board, and replacing them with "bugged" chips containing back doors in hardware; then packaging it all up and getting it delivered on-time.
You just can't fight that kind of power; even as a company as large as Google or Apple. Nation states will always be able to probe and exploit the edge cases in your security model. In general, you can't make anything totally secure, but you can try to make it cost enough to break into that it will deter anyone who can't justify the cost.
Earlier quoted context omitted.
https://www.symantec.com/content/en/us/enterprise/media/secu...
Okay, that was interesting reading. Now I actually know what Stuxnet did and how it worked. The un-named nls_933w.dll responsible for modifying firmware on "over a dozen" HDDs is only termed as Stuxnet- like however: https://securelist.com/equation-the-death-star-of-malware-ga... That's remarkably impressive though. HDDs aren't impenetrable walls - http://spritesmods.com/?art=hddhack - but reflashing firmware on over…
It was really ingenious in a lot of ways: it targeted a specific industrial controller card. Even then, all it did was use the controller card to introduce a subtle voltage fluctuation in the power supply in 1/10 of the centrifuges that rapidly burned out the motors.
Basically, it introduced subtle errors into the system that the Iranians spent about a year trying to resolve. It also spread itself through some ingenious mechanisms to avoid air gaps -- in this case it is suspected they infiltrated a supplier for the centrifuges in China via spear phishing and got it on a USB drive from the supplier to cross the air gap (the way it embeds and hides itself in USB microcode is pretty cool).
The whole story reads like a spy novel; except it actually happened. It's one of my favorite examples of how a nation-state can use cyberterrorism to sabotage an enemy from the shadows -- and this action saved lives, because the alternative was an Israeli air strike on the compound. IMO this is a great example of ethical super-spy hacking.
The most simple and most effective hash table scheme, and nobody is using it, or even knows about it. Fastest and least memory, but not thread-safe. After 12 years there's still nothing better on the horizon.
Though the CheneyMTA paper is also brilliant, a typical Baker paper.
Earlier quoted context omitted.
Aren't there C interpreters still around?
How can you be sure there's no Ken Thompson Hack in the interpretor?
Without a doubt. Time, Clocks, and the Ordering of Events in a Distributed System. Leslie Lamport. http://amturing.acm.org/p558-lamport.pdf My first introduction to time scales as a partial ordering. Very mind opening.
I once spoke to Henri Gouraud after he gave a talk. He was very self-deprecating and acutely embarrassed that his name was attached to a blindingly obvious first-thing-that-comes-into-your-head shading expression-that-barely-deserves-the-name-algorithm. Sometimes that low hanging stuff gives you stomach ache.