Add "pwn template" command for generating templates #909
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Super useful for quickly stubbing stuff out, and for introducing people to
pwntools
for the first time.Any File
This only happens if we get something not-an-ELF, e.g. perhaps the target is a shell-script wrapper around something else. Note we set context explicitly here.
ELF File
If a valid ELF file is specified, we set the context, and add a breakpoint on either the entry or
main
.Additionally, we use
gdb.debug()
instead ofgdb.attach()
in case there is a foreign-architecture binary (can't attach to a QEMU-emulated process), and we avoid the question of "How do I debug from the start?".Remote TCP exploit
Note that we use
args
and inform the user about their options.Additionally, note that we use
gdb.attach()
for the remote process.Finally, we use
connect
instead ofremote
. This makes it so I don't need a better name forremote
.Secure Shell
Again, we use
gdb.debug()
in favor ofgdb.attach()
.Closes #680
Closes #830