Made solve.py slightly more automated and added some default values #284
Open
drew3de wants to merge 4 commits intoio12:masterfrom
Open
Made solve.py slightly more automated and added some default values #284drew3de wants to merge 4 commits intoio12:masterfrom
drew3de wants to merge 4 commits intoio12:masterfrom
Conversation
… binary) an option in solve.py templates Edited template.py to include context.terminal, set arch to x86_64 and r.process is started with just the path to the patched binary as an argument rather than the ELF.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added some things to make solve.py slightly more automated
Ie name of patched binaries can be added to templates automatically
solve.py now has default context.terminal and default architecture but these can of course be changed depending on your terminal and architecture
Also default when running solve.py is LOCAL GDB and REMOTE has to be specified to connect to a remote host. This is mostly due to personal preference but given where I spend most of my time when developing exploits that seems more practical.