Skip to the content ForoHackers
Log inJoin

n0p_sl3d

Joined 17 July 2024

Posts in the forum

  1. Replied in CTF warm-up: read a stack frame and the vulnerability stops being magic

    If you are new: draw the frame on paper for *every* function you read in the first ten challenges. Sizes, offsets, arrows. You will hate it for a week and then you will read any disassembly twice as …

  2. Replied in Hi, I teach assembly through CTF puzzles

    Count me in for puzzle number one. For people who like to check their work: after you decode by hand, assemble and run your guess in a throwaway program of your own and compare. Pencil first, machine…

  3. Replied in Constant-time comparison: why memcmp is the wrong tool for secrets

    Perfect companion to the CTF-style "guess the flag byte by byte" exercises: on your own local challenge, the lesson is that the fix is not "add a random delay" (statistics beat that) but "do the same…

  4. Replied in CTF writeup: the download endpoint that trusted the filename (and the fix)

    Great writeup. For practice challenges I would add the variant where the app decodes the parameter twice (once in the proxy, once in the app). The fix is the same, resolve at the point of use, but th…

  5. Replied in What I do: how computers leak through time and power

    The early-exit compare is a great first example. In CTF terms it shows up as "check the flag one byte at a time and watch the response time". Practice it on your own local challenge binary and you wi…

  6. Replied in Finding the load address of a raw Cortex-M firmware dump

    Great for CTF firmware tasks too. If a challenge gives you a raw blob, the first thing I check is whether word 0 and word 1 look like a stack pointer and an odd code address. Takes ten seconds and sa…

  7. Replied in Spotting djb2 inside a practice crackme (my cat helped)

    The "constants as fingerprints" trick is the one I teach first in CTF write-ups. People expect magic, and it is a lookup table in your head. Add the AES S-box start `63 7c 77 7b` to the list.

  8. Replied in Order of volatility: what to capture first and why

    Good list. For CTF forensics challenges the same order shows up in miniature: if you are given a memory image, strings and process listing first, then network artefacts, then the disk image. Cheap ch…