For all Olly and coding GUru's

[Crudd[RET]]

This is a quote from one of the mods. He wouldve responded himself, but hes not registered here.

What this contest is supposed to be:

There exists alota anti sice tricks out there. But OllyDbg is used more and more. And there arent so many protections against it. Mostly they are just general anti debugger techniques.

We want to see the best anti olly tricks. And this means, really anti olly tricks, no generell protections.

Quote:
- commented sources (for whom?),


For me to understand what you do. I dont have the time to trace every single entry, especially its getting hard if you combine it with basic asm.
The other thing is that users want to see what you do and learn from it.

Quote:
- must work on Windows 9x,ME,NT,2K,XP (why NT,2K,XP isn't enough?),


Cause there are alota guys out there, who still use 9x. And personally I dont like system specific things. What is the sense of a protection technique if you can switch the OS and ignore all those protections.

Quote:
- accepted languages are: asm, C/C++ (why not Delphi?),


Cause those languages are the most common. Thats nothing against Delphi or whatever, but its easier for everyone to have those common languages (except for the author maybe), and we used to keep it that way.

Quote:
a text file with description of your ideas, explanation of more complicated pieces of code (for whom?).


It's nice to see a single file, where the basic ideas are descripted to get an overview. No big textes needed, just a few notes about what your intention was to write this entry!
Next thing are the more complicated pieces of code: Just imagine I have manually encrypted one part of code a few times with several techniques. How do you know what happened there? Again: I dont have the time, and honestly I dont want to trace all this stuff. What for?


Generally:

I dont wanna do a commercial protector out of it. What I am planning is, if those entrys are good, I am thinking about putting all ideas together, and write a paper about it. Sure, just if you want to. This could be published at codebreakers journal, or maybe some higher instance.
I am sure, we get alot of very interesting protections and techniques together, which are really interesting for most people. Thats our imagination of spreading knowledge. We are here to learn and to spread our knowledge.

For me, it would be great to see some entrys from you guys.


DKT