21–30 of 37 posts
* "So you will never code a constructor directly [in C++]. Instead, the compiler codes the constructor for you [and] basically you lose control of the whole thing"* Utter rubbish. One wonders how he got to be "director of Kaspersky’s Global Research and Analysis Team" if his knowledge is so limited
I actually found myself disappointed that it turned out to be something as pedestrian as C on Visual Studio - I thought (hoped?) it would be something really obscure and exotic. I confess that I'm tickled silly by the whole mystery of Stuxnet. It must have been a fascinating project to work on.
Wouldn't you expect an exploit to be written in a low level/system level language on the very platform(and associated tool-chain) it is targeting?
That limits possible authors to all programmers in the world.
I actually found myself disappointed that it turned out to be something as pedestrian as C on Visual Studio - I thought (hoped?) it would be something really obscure and exotic. I confess that I'm tickled silly by the whole mystery of Stuxnet. It must have been a fascinating project to work on.
I wonder why this "research" hasn't been shut down by various governments. Yet. Unless it leads to a red herring.
Earlier quoted context omitted.
Eugene Kaspersky's twitter comment seemed a lot more speculative than anything I heard Costin Raiu say. Exact quote: "The mystery of #Duqu framework http://bit.ly/w5BrzP I don't even do much programming and I was immediately wondering "wtf?" at that statement. The idea of developing a new programming language just to create a worm seemed far fetched, to say the least. He also mentions, as if it were fact despite that…
While I agree that it is reasonable to expect trending towards an alarmist reaction, there are significant enough similarities between DuQu and Stuxnet to suggest that the authors of the former had access to the source code of the latter. If you read the W32.Stuxnet Dossier ( http://www.symantec.com/content/en/us/enterprise/media/secur... ) from Symantec it pretty objectively articulates the complexity and sophistica…
Earlier quoted context omitted.
While I agree that it is reasonable to expect trending towards an alarmist reaction, there are significant enough similarities between DuQu and Stuxnet to suggest that the authors of the former had access to the source code of the latter. If you read the W32.Stuxnet Dossier ( http://www.symantec.com/content/en/us/enterprise/media/secur... ) from Symantec it pretty objectively articulates the complexity and sophistica…
There are significant similarities between DuQu and Stuxnet, agreed. However, I don't think that necessarily means they share the same author. Stuxnet has been widely distributed and analysed. There are a lot of smart people/groups in this world and one of them could have decided to use it as a starting point for other purposes. I also agree that it isn't alarmist to believe Stuxnet had a national interest behind it,…
HN's previous speculation: http://news.ycombinator.com/item?id=3682280 As for this Wired article, feel free to stop reading after: > A custom framework allowed DuQu’s authors to meld C code with object-oriented programming. The rest is just Costin Raiu spewing bullshit.
All of the posts on Duku are pretty interesting. If you have a few minutes you should check them out.
I actually found myself disappointed that it turned out to be something as pedestrian as C on Visual Studio - I thought (hoped?) it would be something really obscure and exotic. I confess that I'm tickled silly by the whole mystery of Stuxnet. It must have been a fascinating project to work on.
C is perfect. It's low level and compiles on every platform in the world. I wonder why this "research" hasn't been shut down by various governments. Yet. Unless it leads to a red herring.
Because anyone who stepped in to stop it would be basically admitting involvement. Right now the perpetrators are likely exactly where they want to be. Speculated on as a possibility, but unconfirmed.
And unconfirmed they will likely remain.
If you are an experienced C/C++ hacker, this article will hurt your brain.