11–15 of 15 posts
https://microcorruption.com/
"We write code that is handed to a compiler, and the compiler takes that code and generates assembly code that will accomplish whatever the C code tells it to." Uhhhh....
It sounds like you have a much clearer way of summarizing the compilation and linking process. As the book is the product of a college student who wanted to start a community around learning these skills it doesn’t promise perfection, and I’m sure we’d benefit from your expertise.
Thanks for the links you've been posting, @throwaway_7718! All great material that will be tried in due time :)
https://microcorruption.com/
Can't recommend this enough. It's an exponential increase in difficulty/time spent on the exercises, but it's really worth it, you end up learning both how to read assembly and different low-level security issues, countermeasures (NX, ASLR, stack canaries, safer programming paradigms) and bypasses to said countermeasures.