Gallopsled / Gallopsled/pwntools
Usage: commandline chroot in pwntools
- Dominant language
- Python
- Stars
- 13.7k
- Forks
- 1.9k
- Avg merge
- 6d 23h
- Merged PRs (30d)
- 3
Description
Hi. I can properly run the commandline
`chroot FIRMWARE_PATH ./qemu-mipsel-static ./FIRMWARE` when I try to execute the dynamically linked router firmware.The reason why using chroot is that the relevant shared libraries is in the path "FIRMWARE_PATH/lib" .
Can I achieve this using pwntools? What is the relevant parameters? And how should I pass them to pwntools?
Contributor guide
Research direction
Start by examining how the command-line chroot invocation is represented in pwntools and how its process-launching entry points accept parameters. Determine whether pwntools should support this workflow or document an existing approach; done means the requested firmware execution path is supported or the usage is clearly explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100