By whoever authored this write-up
Paste a screenshot of or copy and paste the challenge text. This introduces the reader to the challenge of getting them in the same mindset as you while solving.
Keeping all your images and other assets in their own folders is much cleaner.
- Example Write Up
- Table of Contents - Optional, but MDAIO can help with this.
- Describe Your Thought Processes
- Move on to your main exploit or solutions here.
- Getting the Flag
Give a quick primer on what started your path to success; you can include what did and didn't work. Any grand ideas or existing knowledge that lead you to the eventual solution.
- You can include your goals.
- What worked.
- Where your knowledge gaps were.
- What you learned.
Keep it organized by putting the various phases of your solution under headings and sub-headings.
Mind your Markdown It dramatically improves the professionalism of your write-up.
VSCode extensions like Markdown All in One (MDAIO) can help write a markdown document.
An example could be Researching the encryption or algorithms the challenge used here.
Include images, links, and references. The right-angle bracket is how you "quote" something.
If you used any tools, put them here as well.
Then, include how YOU used that research.
Try to include any scripts or commands you used as well. This doc is intended to teach you, teach the reader, and improve your technical writing skills.
$ The triple backticks allow you to "fence" code blocks.
$ As well as tell MD what language it should highlight as.
$ Remember, images, scripts, and commands!1. If it makes sense, bring the "final attack" down to the bottom to emphasize that this was the solution.
Try to post the flag using backticks.