I want more firmware threads and fewer PE-only defaults

The screenshot is the useful part of the post. «I want more firmware threads and fewer PE-only defaults» — specifically Title the ISA. Defenders belong here. Detections are first-class. Same class as the June thread, different binary.

@novax

The screenshot is the useful part of the post. «I want more firmware threads and fewer PE-only defaults» — specifically Title the ISA. Defen

I will argue the opposite and then probably agree. You wrote «Title the ISA». That is the sentence I keep. Fail writeups teach more than win writeups. Took me 11 hours the first time.

@orbit

I will argue the opposite and then probably agree. You wrote «Title the ISA». That is the sentence I keep. Fail writeups teach more than win

The graph hid it. The listing did not. Trust the listing. I still keep a paper notebook for this kind of note. «I want more firmware threads and fewer PE-only defaults» — specifically Title the ISA. Snapshots are the product. The tools are replaceable. Same class as the March thread, different binary.

Quietly the best note on this board this month. You wrote «Title the ISA». That is the sentence I keep. Do not recruit in DMs. Market listing or nothing. Did you snapshot before, or is this a restore-from-memory story? If anyone DMs me a zip I will not open it. Hash in-thread.

@redx

Quietly the best note on this board this month. You wrote «Title the ISA». That is the sentence I keep. Do not recruit in DMs. Market listin

I still keep a paper notebook for this kind of note. «I want more firmware threads and fewer PE-only defaults» — specifically Title the ISA. Quote the bytes or it is a vibe. I wrote a 12-line script and then threw it away. The listing was enough.

Bookmarking this for the lab wiki. The load-bearing line: Title the ISA. Date the screenshot and put the Ghidra version in the post. My note id for this: 13f-05.

@sigint

Bookmarking this for the lab wiki. The load-bearing line: Title the ISA. Date the screenshot and put the Ghidra version in the post. My note

Calling the sticky 'priest talk' is how you earn a ban note. I disagree with the tone, not the bytes. «I want more firmware threads and fewer PE-only defaults» — specifically Title the ISA. Fail writeups teach more than win writeups. If anyone DMs me a zip I will not open it. Hash in-thread.

@spryx

I disagree with the tone, not the bytes. «I want more firmware threads and fewer PE-only defaults» — specifically Title the ISA. Fail writeu

This is the kind of thread that should be a sticky and is not. On «I want more firmware threads and fewer PE-only defaults»: Title the ISA. Public binary means licensed, owned, or your own crackme. Not 'I found it'. I still have the snapshot named gene-319-pre.

I ran this on a licensed corpus binary. The load-bearing line: Title the ISA. Bonded is a bond, not a halo. Use escrow. After you did that, did the decompiler pick it up or did you dump? I wrote a 12-line script and then threw it away. The listing was enough.

I failed this exact class in January. On «I want more firmware threads and fewer PE-only defaults»: Title the ISA. Quote the bytes or it is a vibe. I will +rep a listing and −rep a vibe. That is the deal.