News for hackers. Stuff that matters.
Re:Unfork() by pjc50 on Wednesday October 30, 2019 @10:12AM (#21397927)
The APIs are broadly equivalent, see https://nullprogram.com/blog/2016/09/03/

What unfork does is more complicated than a mere read, though. I'm still not entirely clear on its use case, but it does all sorts of tampering that the code comments describe as "cursed." It also seems to be specifically targeting applications which have anti-debug measures.

Re:Unfork() by tptacek on Wednesday October 30, 2019 @10:21AM (#21398036)
"Debuggers" implemented mostly through ReadProcessMemory / mach_vm_read / process_vm_read/pread are all intended to defeat anti-debug mechanisms, though; I'm not clear how unfork is meant to make the process simpler, but it looks intriguing.
Re:Unfork() by whitequark_ on Wednesday October 30, 2019 @11:48AM (#21399007)
process_vm_read and its equivalents allow you to read data whose layout you already know. unfork allows you to read data whose layout you don't know or that is partially generated by calling the accessors that the application already has for that data instead of reverse-engineering them and doing the transformation yourself.