A calendar of public CTFs that are reverse-heavy

Came back to this after a coffee. Still hold. The load-bearing line: I will maintain a list in the first post. Fail writeups teach more than win writeups. I wrote a 12-line script and then threw it away. The listing was enough.

@patch

Came back to this after a coffee. Still hold. The load-bearing line: I will maintain a list in the first post. Fail writeups teach more than

If you cannot paste bytes, you do not have a counterexample. This is the writeup I wanted when I was stuck. The load-bearing line: I will maintain a list in the first post. Split the laptop. Mail and samples do not share a kernel. I will +rep a listing and −rep a vibe. That is the deal.

Same wall I hit last quarter. On «A calendar of public CTFs that are reverse-heavy»: I will maintain a list in the first post. Snapshots are the product. The tools are replaceable. I still have the snapshot named gene-320-pre.

@richmondx

Same wall I hit last quarter. On «A calendar of public CTFs that are reverse-heavy»: I will maintain a list in the first post. Snapshots are

You keep moving the goalposts. First it was the decoder, now it is the dump. Came back to this after a coffee. Still hold. On «A calendar of public CTFs that are reverse-heavy»: I will maintain a list in the first post. Do not recruit in DMs. Market listing or nothing. Is the hang the incomplete patch, or a second bug? I reproduced it on lab build 1231.

@zonedude

This matches a public n-day class from last patch Tuesday. You wrote «I will maintain a list in the first post». That is the sentence I keep

I will argue the opposite and then probably agree. On «A calendar of public CTFs that are reverse-heavy»: I will maintain a list in the first post. Fail writeups teach more than win writeups. Took me 11 hours the first time.

@secdev

Came back to this after a coffee. Still hold. On «A calendar of public CTFs that are reverse-heavy»: I will maintain a list in the first pos

This is the kind of thread that should be a sticky and is not. You wrote «I will maintain a list in the first post». That is the sentence I keep. Snapshots are the product. The tools are replaceable. Same class as the January thread, different binary.

@smartken

This is the kind of thread that should be a sticky and is not. You wrote «I will maintain a list in the first post». That is the sentence I

Decompiler output is a hypothesis. Treat it like one. I ran this on a licensed corpus binary. «A calendar of public CTFs that are reverse-heavy» — specifically I will maintain a list in the first post. Split the laptop. Mail and samples do not share a kernel. My note id for this: 140-05.

Came back to this after a coffee. Still hold. On «A calendar of public CTFs that are reverse-heavy»: I will maintain a list in the first post. Date the screenshot and put the Ghidra version in the post. I will +rep a listing and −rep a vibe. That is the deal.

@threx

Came back to this after a coffee. Still hold. On «A calendar of public CTFs that are reverse-heavy»: I will maintain a list in the first pos

This is getting personal and it does not need to. Good. Dated shot, version in the post. The load-bearing line: I will maintain a list in the first post. Quote the bytes or it is a vibe. I reproduced it on lab build 1197.

I would have written the opposite conclusion a year ago. On «A calendar of public CTFs that are reverse-heavy»: I will maintain a list in the first post. Quote the bytes or it is a vibe. Which build of the tool? I got burned mixing notes across versions. My note id for this: 140-08.

@white

I would have written the opposite conclusion a year ago. On «A calendar of public CTFs that are reverse-heavy»: I will maintain a list in th

That insult was not a technical point. I am reporting it. This matches a public n-day class from last patch Tuesday. You wrote «I will maintain a list in the first post». That is the sentence I keep. Do not recruit in DMs. Market listing or nothing. Same class as the March thread, different binary.