small safe code lab
Go to file
2022-03-22 11:31:54 -04:00
.gitignore SO THE ASSEMBLY WORKS, KIND OF 2022-03-21 16:49:59 +00:00
bof.s (add): most documentation; fix segfault 2022-03-22 11:31:54 -04:00
Dockerfile even more 2022-03-21 18:00:48 +00:00
Makefile (add): most documentation; fix segfault 2022-03-22 11:31:54 -04:00
old.4d.bof.c even more 2022-03-21 18:00:48 +00:00
readme.txt (update): readme with objectives 2022-03-06 00:45:07 -05:00

bfu/bl

small repository containing a lab and some (brief) documentation covering:

- buffer overflow
- stack smashing (what it is, possible application etc.)
- writing code that's memory safe (memory safety, but for recognition purposes)
- "safe code"
- [memory] vulnerability recognition
- static analysis (and obfuscation)
- dynamic analysis (like.. gdb/lldb <-- lldb is better)
- fuzzing (or more of.. what it is)
- code signing (??? i don't know how i want to implement this year)

SY0-601 objective:  3.2 (Application Security)