News for hackers. Stuff that matters.

A comment on Reverse Engineering Snapchat (Part II): Debofuscating the Undeobfuscatable.

Re:Reverse Engineering Snapchat (Part II): Debofuscating the... by underdeserver on Monday June 22, 2020 @02:30AM (#23597767)
For fuckup_debugging, can't you use hardware breakpoints instead?

Also, why not patch the binary? I think iteratively patching out protections (in a repeatable, versioned way) would be my approach. It is then applicable to other binaries as well.

[ Parent | on HN ]
Re:Reverse Engineering Snapchat (Part II): Debofuscating the... by saagarjha on Monday June 22, 2020 @03:35AM (#23598022)
Hardware breakpoints are a little complicated on iOS. And patching the binary would of course only work if no other code verified the validity of the page you touched.
[ Parent | on HN ]
Re:Reverse Engineering Snapchat (Part II): Debofuscating the... by 3eed on Monday June 22, 2020 @07:08AM (#23598982)
Are hardware breakpoints even possible on iOS? And correct, you can't patch the binary because there many anti-tampering measures, you could probably bypass those, but that's going a different route.
[ Parent | on HN ]
Re:Reverse Engineering Snapchat (Part II): Debofuscating the... by bluesign on Monday June 22, 2020 @02:48AM (#23597848)
Not the OP, but I can answer I guess. Hardware breakpoints are very limited (number of breakpoints you can put). Usually when you are debugging a decent target, number of breakpoints you use easily reach 50-60.
[ Parent | on HN ]
Re:Reverse Engineering Snapchat (Part II): Debofuscating the... by underdeserver on Monday June 22, 2020 @03:09AM (#23597929)
No doubt, but it's better than pausing every time. I guess with scripting it isn't really different.
[ Parent | on HN ]