This project is currently on-going. The purpose of this is to reconstruct the full source code of the original windows xp Minesweeper. (sha256: bcff89311d792f6428468e813ac6929a346a979f907071c302f418d128eaaf41)
I finished reconstructing the full minesweeper source:) The only thing that I don't have time to do is to order variables in one module.. Looking in the assembly code and variable layout it looks like most of the variables were global variables declared in one source file.
The artifacts of the reverse engineering process:
- Design document explaining the full design and implementation of MineSweeper
- Full compilable source code of MineSweeper
- Finding bugs
Most of the process is done using static analysis without using a decompiler. I wanted to read lots of assembly code.
- Create documentation
- Test code
- Create remote hacking tool
As stated here, The source code of Minesweeper has already been leaked - So we have a peek at the original source back then.
- I did not know it was leaked when I started this
- I was doing this just for fun and learning so probably I would have done it anyway
- This is not the exact version I wanted to reverse engineer
After I finished the project, I compared the source code from my reversing to the leaked source, you can see it's almost identical, so yay.
The purpose of this tool is to allow full control over a remote minesweeper process. Some ideas I had:
- Create a remote Minesweeper Hacking Tool (in Rust)
- Configure bombs
- Configure timer
- Configure board size beyond the usual limits
- Configure game state - end game, win game, lose game
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent