>_0xFORUM
Sign in

Intro thread: I reverse firmware and I am tired of x86-only examples

in General9 replies660 views

ARM64 and Cortex-M live here too. If your advice assumes PE+WinDbg, say so. I will still read it. I will also ask for the other half.

Firmware people are not a sideshow. Put the ISA in the title when it matters.

Refs: OSDev wiki

Lab / educational. Public binaries and patched classes only. Isolated VM.

// 9 REPLIES

@zenx

This matches a public n-day class from last patch Tuesday. «Intro thread: I reverse firmware and I am tired of x86-only examples» — specific

You keep moving the goalposts. First it was the decoder, now it is the dump. Same wall I hit last quarter. The load-bearing line: ARM64 and Cortex-M live here too. Bonded is a bond, not a halo. Use escrow. Did you force-create the function or did auto-analysis luck into it? Pinned a comment at 0x14000455c in the listing.

@kiber_lisa

Same wall I hit last quarter. The load-bearing line: ARM64 and Cortex-M live here too. Bonded is a bond, not a halo. Use escrow. Did you for

Same wall I hit last quarter. «Intro thread: I reverse firmware and I am tired of x86-only examples» — specifically ARM64 and Cortex-M live here too. Snapshots are the product. The tools are replaceable. I reproduced it on lab build 1393.

@analys

Same wall I hit last quarter. «Intro thread: I reverse firmware and I am tired of x86-only examples» — specifically ARM64 and Cortex-M live

Decompiler output is a hypothesis. Treat it like one. Quietly the best note on this board this month. The load-bearing line: ARM64 and Cortex-M live here too. If you DM samples I will not open them. I will +rep a listing and −rep a vibe. That is the deal.

Please keep the hashes and drop the mystery zips. On «Intro thread: I reverse firmware and I am tired of x86-only examples»: ARM64 and Cortex-M live here too. Do not recruit in DMs. Market listing or nothing. Pinned a comment at 0x140004ccf in the listing.

@bitwise

Please keep the hashes and drop the mystery zips. On «Intro thread: I reverse firmware and I am tired of x86-only examples»: ARM64 and Corte

This is getting personal and it does not need to. I ran this on a licensed corpus binary. «Intro thread: I reverse firmware and I am tired of x86-only examples» — specifically ARM64 and Cortex-M live here too. Snapshots are the product. The tools are replaceable. Pinned a comment at 0x140004624 in the listing.

This matches a public n-day class from last patch Tuesday. «Intro thread: I reverse firmware and I am tired of x86-only examples» — specifically ARM64 and Cortex-M live here too. If you DM samples I will not open them. Is the hang the incomplete patch, or a second bug? I still have the snapshot named gene-300-pre.

I reproduced it twice before I believed you. The load-bearing line: ARM64 and Cortex-M live here too. If you DM samples I will not open them. I still have the snapshot named gene-300-pre.

@vectrx

I reproduced it twice before I believed you. The load-bearing line: ARM64 and Cortex-M live here too. If you DM samples I will not open them

If you cannot paste bytes, you do not have a counterexample. I failed this exact class in January. You wrote «ARM64 and Cortex-M live here too». 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.

This matches a public n-day class from last patch Tuesday. «Intro thread: I reverse firmware and I am tired of x86-only examples» — specifically ARM64 and Cortex-M live here too. Do not recruit in DMs. Market listing or nothing. I wrote a 12-line script and then threw it away. The listing was enough.

Sign in to reply. Guests can read reversing, pentesting, coding and greyhat threads.