Built/ordered my first PCB! Make a little base health counter for Star Wars Unlimited.

If you ever wanted to make a video ctf writeup, here's a little brain dump on how to get started: If you do record one, please send it to me! I'd love to check it out.

Oh wow, unexpected, thank you @snyksec/@_JohnHammond for hosting the CTF and for the VR set!

(Part 2), went back and did the heap sprays:

I'm addicted to ~200 no BS challenges with writeups. I have done nothing but alpacahack challenges for the past week. I'll probs do some writeups on my favorite challenges in the future, but all of them are amazing.

New video on exploiting a vulnerable kernel driver /w oob read/write to modprobe from checksumz/irisCTF:

Do people have an intuitive sense of how algorithms such as pollard's p-1 works? Or is it more "ah, p-1 is smooth, time for pollard's p-1, hope it works".

(I discuss the above in writeup video: ).

Could someone build a search engine for CTF writeups?.

Started uploading videos again: (first one on DNS rebinding from iris/web/webhook). Content should be roughly the same, but I'll probably only chat about chals I thought were neat instead of trying to do them all.

So yeah, the STACK_TOP is randomized, and then the stack pointer (first frame) is randomized within the stack. Crazy stuff!. (Thanks to corg0 from buckeye for also investigating!).

If the stack is already randomized, does additionally randomizing the starting Stack Pointer also help? I feel like I'm missing something, but going to stop there for now.

There's a comment that mention "Hyper-Threading L1 cache evictions[1]. but I don't think that is the reason. It looks like it was reused as part of some ASLR upgrades[2][3]. [1] [2] [3]

I *think* it is this. Now to find out why:.

For zseries elf, but I think it still applies, "The system may also leave an unspecified amount of memory between the null auxiliary vector entry and the beginning of the information block.", tracking that down.

To clarify further, not a variable in a stack frame. Something like *__libc_argv.

Oh to clarify, this is not from an active CTF. Doing some research from a past challenge (sailing_the_c, buckeye2024).

Vague question, but I'm having trouble finding an answer on google. Why is calculating the top of the stack from a stack leak unreliable? If you have a leak in libc and you know what the symbol is, you can calculate the base of libc. But with a stack, it's off by 0x1000 or so.

Just a friendly reminder that MIT Battlecode starts tonight! It's not a security CTF, but it's super fun! Programming little autonomous agents, hacking java byte code, getting dunked on by college/high schools kids. All the fun things!.

Some quick thoughts on why people shouldn't be too hard on themselves when it comes to CTFs.