Reverse Engineering Snapchat (Part II): Debofuscating the Undeobfuscatable • Hacker News Board

Re: Reverse Engineering Snapchat (Part II): Debofuscating the Undeobfuscatable

#61

Post by pc86 » Mon, Jun 22, 2020, 8:43 PM UTC

stjohnswarts wrote: post #26

djhaskin987 wrote: post #23

Earlier quoted context omitted.

That's actually the central issue behind the Supreme Court case battle between Oracle and Google right now: whether or not you can copyright apis

That's going to be a really big decision in our world of software. I hope that SCOTUS doesn't side with the devil.

Referring to the other side in a debate as "the devil," aside from being hyperbolic to the point of inducing an eye roll in every reasonable person within earshot, is exactly how the US ended up with a reality TV show host in the White House.

Re: Reverse Engineering Snapchat (Part II): Debofuscating the Undeobfuscatable

#62

Post by posedge » Fri, Jun 26, 2020, 9:06 PM UTC

bluesign wrote: post #30

coolspot wrote: post #25

Shouldn’t you be able to find any code that scans for breakpoints easily and patch it to be blind?

Normally it is more like calculating hash from code piece, then xor result with constant and jump. (In general cases, never reversed snap) So usually there is nothing to patch.

Can you calculate that hash (of the original binary) yourself and patch THAT in the function?

Re: Reverse Engineering Snapchat (Part II): Debofuscating the Undeobfuscatable

#63

Post by moscovium » Mon, Jun 29, 2020, 11:41 PM UTC

mmm_grayons wrote: post #6

moscovium wrote: post #4

Earlier quoted context omitted.

'Debo' or 'Deob'?

It's just a typo, and we're all human. Maybe focus on the really interesting research instead?

i was just clarifying the poster above lol