Skip to content

radiantBear's Write-ups

Welcome! Thanks for checking out my writeups. I hope you find them interesting & helpful! If you have suggestions for improving any writeup, I would love to hear your thoughts. Feel free to create an Issue in the GitHub repo where the docs are stored.

Write-up Conventions

When creating these write-ups, I try to follow a few conventions to express ideas more clearly. These are documented here as much for my own memory as anything else.

  • Code blocks should use line numbers that match the source code file to minimize the amount of context needed in the code block
  • Code blocks should always include a couple highlighted lines calling attention to the crucial points that inform the current conclusion
  • Each step of the investigation stage of solving the puzzle should receive a full section to explain it
  • Admonition blocks should be used to call attention to critical points that may otherwise be lost in a long section
  • Details blocks should be used to provide extra details that aren't crucial to solving the challenge but are interesting or aid a deeper understanding of quirks that may reappear in other challenges

Notes provide details about the challenge

Abstracts hold the challenge's description

Tips provide guidance about tools and techniques

Info provides additional, optional, insights into the vulnerable program

Warnings call attention to details that may cause an attack to fail

Danger calls attention to steps that may be risky to perform on the reader's machine