Texas A&M Student writeups for CTFs
- It helps solidify the knowledge and skills that you used to solve the challenge.
- It helps other people who were not able to solve the problem learn new knowledge and skills.
- It will show other people different approaches and thought processes used while solving challenges.
- Recruiters like to see proof that you are actually able to solve these types of challenges and on top of that can explain how you did it.
- Fork this repo (https://help.github.com/articles/fork-a-repo/)
- Add your writeups to your repo
- Writeup folder name should be
challengename-user/screenname
. Ex)pwn1-messy
- Writeup folder name should be
- Create a pull request against this repo with your new writeup (https://help.github.com/articles/about-pull-requests/)
When creating a writeup for a challenge please consider the following things:
- Be as detailed as possible. Explain the theory behind what you did to solve the challenge instead of simple one line answers like "execute
python script.py
" and you will get the answer. This is because other students will be reading these writeups as a learning tool so the more theory and thought process you explain the better. - When possible and appropriate add screenshots.
- When appropriate provide any scripts that you wrote and used for that challenge.
- When possible provide the challenge files that you recieved. Most CTFs are only up for a weekend so the files will not be accessible afterwards.
- The suggested file format to do the writeups in is markdown or
.md
Example writeups can be found here: https://ctftime.org/writeups
Markdown Cheatsheet: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet