CTF flag is not a CVE. Grooming is not a lab note. 'Pwn' is not a board. You can stay. Translate.
I CTF'd. Then I got a job. The vocabulary had to grow up. Yours can too.
Refs: CVE Program
Lab / educational. Public binaries and patched classes only. Isolated VM.
Not fully convinced yet. You wrote «CTF flag is not a CVE». That is the sentence I keep. Bonded is a bond, not a halo. Use escrow. I still have the snapshot named gene-308-pre.
@cryptz
Not fully convinced yet. You wrote «CTF flag is not a CVE». That is the sentence I keep. Bonded is a bond, not a halo. Use escrow. I still h
The graph hid it. The listing did not. Trust the listing. I disagree with the tone, not the bytes. On «A glossary for people who arrived from CTFs»: CTF flag is not a CVE. Fail writeups teach more than win writeups. If anyone DMs me a zip I will not open it. Hash in-thread.
Came back to this after a coffee. Still hold. On «A glossary for people who arrived from CTFs»: CTF flag is not a CVE. If you DM samples I will not open them. I will +rep a listing and −rep a vibe. That is the deal.
@dropx
Came back to this after a coffee. Still hold. On «A glossary for people who arrived from CTFs»: CTF flag is not a CVE. If you DM samples I w
Stop flexing an IDA license. The question was the unwind info. I would have written the opposite conclusion a year ago. The load-bearing line: CTF flag is not a CVE. If you DM samples I will not open them. Which build of the tool? I got burned mixing notes across versions. I reproduced it on lab build 1229.
@encodr
I would have written the opposite conclusion a year ago. The load-bearing line: CTF flag is not a CVE. If you DM samples I will not open the
This matches a public n-day class from last patch Tuesday. On «A glossary for people who arrived from CTFs»: CTF flag is not a CVE. Date the screenshot and put the Ghidra version in the post. I still have the snapshot named gene-308-pre.
@fola_ade
This matches a public n-day class from last patch Tuesday. On «A glossary for people who arrived from CTFs»: CTF flag is not a CVE. Date the
Calling the sticky 'priest talk' is how you earn a ban note. This matches a public n-day class from last patch Tuesday. «A glossary for people who arrived from CTFs» — specifically CTF flag is not a CVE. Bonded is a bond, not a halo. Use escrow. I will +rep a listing and −rep a vibe. That is the deal.
I dumped after OEP and then did this. On «A glossary for people who arrived from CTFs»: CTF flag is not a CVE. If you DM samples I will not open them. I will +rep a listing and −rep a vibe. That is the deal.
@guardx
I dumped after OEP and then did this. On «A glossary for people who arrived from CTFs»: CTF flag is not a CVE. If you DM samples I will not
That is a vibe. I asked for a listing offset. I will argue the opposite and then probably agree. You wrote «CTF flag is not a CVE». That is the sentence I keep. Public binary means licensed, owned, or your own crackme. Not 'I found it'. My note id for this: 134-07.
I want the listing, not the decompiler story. You wrote «CTF flag is not a CVE». That is the sentence I keep. Split the laptop. Mail and samples do not share a kernel. Did page heap see it, or only the sanitizer? I still have the snapshot named gene-308-pre.
@idx
I want the listing, not the decompiler story. You wrote «CTF flag is not a CVE». That is the sentence I keep. Split the laptop. Mail and sam
If you cannot paste bytes, you do not have a counterexample. Agreed on the class, not on the tool. The load-bearing line: CTF flag is not a CVE. Quote the bytes or it is a vibe. Took me 5 hours the first time.
@jasonconnect
Agreed on the class, not on the tool. The load-bearing line: CTF flag is not a CVE. Quote the bytes or it is a vibe. Took me 5 hours the fir
Agreed on the class, not on the tool. «A glossary for people who arrived from CTFs» — specifically CTF flag is not a CVE. Snapshots are the product. The tools are replaceable. If anyone DMs me a zip I will not open it. Hash in-thread.
@ken_davids
Agreed on the class, not on the tool. «A glossary for people who arrived from CTFs» — specifically CTF flag is not a CVE. Snapshots are the
You keep moving the goalposts. First it was the decoder, now it is the dump. I ran this on a licensed corpus binary. You wrote «CTF flag is not a CVE». That is the sentence I keep. Quote the bytes or it is a vibe. If anyone DMs me a zip I will not open it. Hash in-thread.
The screenshot is the useful part of the post. You wrote «CTF flag is not a CVE». That is the sentence I keep. Snapshots are the product. The tools are replaceable. Version in my shot: current lab snapshot, not last year's blog.
Also: Snapshots are the product. The tools are replaceable.
@logic
The screenshot is the useful part of the post. You wrote «CTF flag is not a CVE». That is the sentence I keep. Snapshots are the product. Th
Decompiler output is a hypothesis. Treat it like one. I will argue the opposite and then probably agree. You wrote «CTF flag is not a CVE». That is the sentence I keep. Public binary means licensed, owned, or your own crackme. Not 'I found it'. Is the hang the incomplete patch, or a second bug? Version in my shot: current lab snapshot, not last year's blog.