||3 months ago|
|ctf-challenge-src||3 months ago|
|doc||5 months ago|
|src||3 months ago|
|.gitignore||5 months ago|
|Makefile||4 months ago|
|Makefile.new||3 months ago|
|README.md||3 months ago|
|ass.sh||5 months ago|
|flag.txt||5 months ago|
This project is a custom emulator/VM, along with tooling such as an assembler, disassembler, and integrated debugger. It was originally written as a challenge for a CTF run by my school's computer security club. It has been refactored and reorganized. In the future, I may reuse this challenge and modify it, mainly so that it cannot be unintentionally autosolved by the angr framework (as it was in its original form).
For documentation on the assembly language and architecture, consult the relevant file(s) in
- TODO: document assembly language
See files in
/doc for my design process, VM specs, lessons learned, and other stuff.
Build "normal" competition/prod image (default):
Build trace image (integrates debugger into the build):
$ make trace
- Note: in-between making the normal and trace images, one should run
make cleanoto remove previous object files since they'll differ between normal and trace builds
$ make disass
Build VM ROM:
$ make rom
- Note: if one updates the ROM assembly in rom.asm, they'll need to manually rebuild the ROM.
ass.sh, is already good to go (as good as a bad shell-scripted assembler can be at least).
depending on which version you wish to run.
To use the debugger, simply build and run the trace image, as the binary will automatically place you in the debugger to start.
ass.sh, can be used to create a binary ROM image given an assembly language file (file extension
.asm) and an optional zero page initialization file (
zeropage.incbin in the challenge's case). The latter if present, is used to initialize the first 256 bytes of ROM to some hardcoded state.
disass, is located in the
bin/ directory upon being made.
For usage information for both tools, run them with no arguments.