71–80 of 127 posts
According to the README, this is not the Stuxnet source code. Rather it's authored by people mentioned in the license by reverse engineers from the binaries. The real source code would probably have lots of juicy interesting things revealing how it was developed.
// TODO: תקן את זה
Earlier quoted context omitted.
Imagine if the same strategy were applied to biological warfare. Novel viruses tailored to be symptomatic and cause harm to just one specific world leader. If the technology exists, it could be the most formidable assassination tool available; a self-delivering, non-nuclear ace-in-the-hole for winning a war.
It's probably not that imaginary. There was much hand ringing during COVID that Russia's testing protocol for meeting Putin would allow them to collect DNA from world leaders. https://www.reuters.com/world/europe/putin-kept-macron-dista...
>This repository contains RCEd code extracted from Stuxnet binaries via disassembler and decompilers. Is there a way to write code (make binaries) such that it would be extremely difficult to recover the source code via decompilers or a disassembler?
Can anyone explain why Stuxnet was admitted to and publicised so much. Aren’t secret operations usually kept… secret? What was the motivation for the PR drive?
It was never admitted to though; https://en.wikipedia.org/wiki/Stuxnet It was publicised so much because it was the most advanced cyber weapon of its kind to ever been released.
Correction:
... it was the most advanced cyber weapon of its kind to ever been discovered
Earlier quoted context omitted.
Is the law clear in this? They created something different from the source material binary program.
This. They don't give you the same as the original virus code, they give you different code (namely readable one), than apparently compiles to the virus assembly. It's plausible this took effort, so I think it's only fair if they license it - it seems also ethically fair, since their licence is permissive.
>but both of us spent hundreds, if not thousands, of hours between ASM code trying to figure out what was behind those binaries and we are providing the product of our hard work (i.e. readable C code) to you for free
also
> It is not a simple job and it is not a short job, both our licenses are extremely permissive
>I'd like to ask you is that our job get recognized...show us your support by giving us credit for what we did
>This repository contains RCEd code extracted from Stuxnet binaries via disassembler and decompilers. Is there a way to write code (make binaries) such that it would be extremely difficult to recover the source code via decompilers or a disassembler?
When writing in a higher language such as e.g. C, you can use code obfuscators to make your C code extremely hard to read.
If you want to make decompiling even impossible, you could modify the machine code generated by the C compiler. Even slight moderations are already enough.
If you want to make it (virtually) impossible to even disassemble the machine code, you could encrypt your binary itself except for a small bootstrap that will unencrypt the remainder of the binary when it runs.
I remember reading a very well written article on stuxnet, detailing the entire way it worked. It was written in a very story-like way that built slowly until it revealed what the actual payload and impact was. Does anyone have a link to this article?
[1]: https://docs.broadcom.com/doc/security-response-w32-stuxnet-...
In Iran the copyrights of foreign works are not well protected. This lead to a lot of copying: western software and books are/were available for little more than the price of the writable CD-ROM or paper+ink you got it on. Translations of works were slightly more expensive, that the translator did have to get paid. Since Windows (etc.) was free, and the university thought curriculum based largely on US uni-books, Win…
>This repository contains RCEd code extracted from Stuxnet binaries via disassembler and decompilers. Is there a way to write code (make binaries) such that it would be extremely difficult to recover the source code via decompilers or a disassembler?
Yes, there are many ways to do that. When writing in a higher language such as e.g. C, you can use code obfuscators to make your C code extremely hard to read. If you want to make decompiling even impossible, you could modify the machine code generated by the C compiler. Even slight moderations are already enough. If you want to make it (virtually) impossible to even disassemble the machine code, you could encrypt yo…
I remember having to write a presentation about Stuxnet while at Uni, it was insane. At the time they reckoned the authors had a functioning QA environment to ensure it actually worked (broke) the Siemens PLCs they were targeting.
Stuxnet didn't break anything. It was used to override the working regime of centrifuges and conceal this fact from being discovered.