Hi everybody,

I'm working in a project for my graduation in the university, and I'm not so confidente about it.

Currently, the project is of the following form:

Title: The importance of Reverse Engineering by means of study of cases

Case 1 - Ressurrecting a dead component
By means of an old DOS game, I try to recreate the original screen editor through reverse engineering in the executable, in search of the format of the screens archive.

Case 2 - Fighting malwares, trojans and virus
Using a Trojan that infect me while I used Internet Explorer, I use reverse engineering to detect the alterations that it makes in my computer, and to create corrections for the same ones.

Case 3 - Adding functionalities
I modify the writing routine of a freeware keylogger so that the recorded keyboard keys in the archive of log are cryptographad before they are saved.

It would like suggestions. Do I have to include more cases? Which? The depth is reasonable? The cases are relevants? Any suggestion would be appreciated.

PS: Excuse the bad Altavista translation

About the depth and relevance of the cases, you'd better ask your university about that instead.

As for the cases themselves, I think it completely depends on what you make of it, but I would guess that you need to be much more specific in the definition, right now it is very unclear what you are going to do with each case, and what the results are supposed to be in the report.

interoperability: for example, reverse-engineering protocols, APIs when you do not have their specification. Making your system compatible with another. Trillian, WINE, ...

for fun: learning how things work.

Reverse-engineering is not just about computers. Car makers check their competitors' vehicles too.

Hi,very interesting work indeed..working in an accademic environment too I'm also interested in this project, it could be the base for other works too..would you share it as soon as it will be ready (if it's in english of course) ??