11–20 of 37 posts
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.
If you are an experienced C/C++ hacker, this article will hurt your brain.
Well we already know that crowdsourcing works for funding---that it works for coding is no surprise. The folks over in Bio have learned that lesson. All of which makes me wonder about a future (at least to me) formal mechanism to allow projects to adopt crowds as part of their overall coding methods. Parsing the useful from the cruft might be a pain, but it seems like it might well be worth it depending on the need a…
that it deceived kaspersky this long is frankly disturbing.
Utter rubbish. One wonders how he got to be "director of Kaspersky’s Global Research and Analysis Team" if his knowledge is so limited
this was blindingly obvious to anyone that does anything with compilers and reverse engineering. there are some really big clues: the access to C functions from win32 is direct, with no visible FFI. the generated code has a lot of qualities shared with C code, in terms of control flow and stack usage, and it had a lot in common with the MS C compiler based on how it uses the stack. that it deceived kaspersky this lon…
It may have seemed obvious in hindsight, but some pretty bright people were looking at it, including compiler people at MS.
If it were truly so obvious, it's a shame you didn't end everyone's troubles when the mystery was originally posted here.
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.
this was blindingly obvious to anyone that does anything with compilers and reverse engineering. there are some really big clues: the access to C functions from win32 is direct, with no visible FFI. the generated code has a lot of qualities shared with C code, in terms of control flow and stack usage, and it had a lot in common with the MS C compiler based on how it uses the stack. that it deceived kaspersky this lon…
Hindsight is 20/20. It may have seemed obvious in hindsight, but some pretty bright people were looking at it, including compiler people at MS. If it were truly so obvious, it's a shame you didn't end everyone's troubles when the mystery was originally posted here.
it was posted to some (private) mailing lists I'm on, and I posted exactly the same thing there.
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.
We do now know however that one compiler flag is all it takes to throw off professional, full-time reverse-engineers. That's got to be valuable to someone.