chapters/exploitation-techniques: Handle 07-challenge-shellcode-on-st…#56
Conversation
…ack Docker setup and automation Added the following files to help with automation: 1. A Dockerfile containing two stages: build and runtime 2. A run.sh script which the student can run to handle the docker process 3. A README.md file which depicts the usage of the previous components. Signed-off-by: catalinamanolache <mmariacatalina@yahoo.com>
razvand
left a comment
There was a problem hiding this comment.
Simplify your commit prefix. Use only exploit-techniques: ....
Add ending newline.
Use present tense in commit description.
Use two commits. One for the solution and one for the Dockerfile in src/.
Use your proper name in the commit authorship and signature, i.e. use Cătălina Manolache <mmariacatalina@yahoo.com>, instead of catalinamanolache <mmariacatalina@yahoo.com>
...ters/exploitation-techniques/shellcodes/drills/07-challenge-shellcode-on-stack/sol/README.md
Outdated
Show resolved
Hide resolved
Updated the Dockerfile for the shellcode-on-stack challenge to properly build and run the vulnerable binary, ensuring it works correctly in the Docker environment and listens on port 31345. Signed-off-by: Cătălina Manolache <mmariacatalina@yahoo.com>
Added the following files: 1. A Makefile which the student can use to handle the docker process. 2. A README.md file which depicts the usage of the previous component. Signed-off-by: Cătălina Manolache <mmariacatalina@yahoo.com>
razvand
left a comment
There was a problem hiding this comment.
One of your commits doesn't have the proper name. Use Cătălina Manolache <mmariacatalina@yahoo.com> instead of catalinamanolache <mmariacatalina@yahoo.com>.
| The Makefile automates the process of building the Docker image, running the | ||
| container, copying the binary and executing the exploit script. |
There was a problem hiding this comment.
| The Makefile automates the process of building the Docker image, running the | |
| container, copying the binary and executing the exploit script. | |
| The Makefile automates the process of building the Docker image, running the container, copying the binary and executing the exploit script. |
One sentence per line.
| # Cleanup: Remove the local copy of the binary and stop the container | ||
| rm -f vuln | ||
| docker stop challenge07 | ||
| docker rm -f challenge07 No newline at end of file |
| ENV TERM=xterm | ||
|
|
||
| COPY --from=builder /build/vuln /app/vuln | ||
| COPY sol/exploit.py /app/exploit.py |
There was a problem hiding this comment.
Why do you copy the exploit?
| stop: | ||
| -docker stop $(CONT_NAME) 2>/dev/null || true | ||
| -docker rm -f $(CONT_NAME) 2>/dev/null || true | ||
| -rm -f ./vuln 2>/dev/null || true |
There was a problem hiding this comment.
This line isn't required, is it?
…ack Docker setup and automation
Added the following files to help with automation:
Prerequisite Checklist
Description of changes