pwnrunner ./challenge-binary will run the challenge binary in the correct environment (libc/ld/cwd)
Should also have a variant to run w/ GDB, like pwnrunner --debug ./challenge-binary? Maybe one variant will run under GDB, and another variant will run a gdbserver with the provided port? How about pwntools integration?
Should some minimal info be embedded in challenge binaries? Like Ubuntu version and PwnableHarness version? Then the pwnrunner script could extract these from the binary to always load the correct environment.
What about challenges with custom Dockerfiles? #14 is related. Perhaps should just use published Docker images instead? Maybe with #24 to support debugging?
Useful by players during a ctf.
Usage:
pwnrunner ./challenge-binarywill run the challenge binary in the correct environment (libc/ld/cwd)Should also have a variant to run w/ GDB, like
pwnrunner --debug ./challenge-binary? Maybe one variant will run under GDB, and another variant will run a gdbserver with the provided port? How about pwntools integration?Should some minimal info be embedded in challenge binaries? Like Ubuntu version and PwnableHarness version? Then the
pwnrunnerscript could extract these from the binary to always load the correct environment.What about challenges with custom Dockerfiles? #14 is related. Perhaps should just use published Docker images instead? Maybe with #24 to support debugging?