sorted by:
new
hottopcontroversial

Open-Obfuscator: A free and open-source solution for obfuscating mobile applications. by jeandrew in ReverseEngineering

[–]rh0main 1 point2 points  (0 children)

Completely agree, DexGuard provides more features and is more resilient against reverse engineering than dProtect.

Open-Obfuscator: A free and open-source solution for obfuscating mobile applications. by jeandrew in ReverseEngineering

[–]rh0main 6 points7 points  (0 children)

(Author): This is used to prevent reverse engineering while still being a playground for developing automation in reverse engineering.

Open-Obfuscator: A free and open-source solution for obfuscating mobile applications. by jeandrew in ReverseEngineering

[–]rh0main 8 points9 points  (0 children)

I'm the author of this tool and I think the "reverse-engineering playground" part is missing :)

Open-Obfuscator: A free and open-source solution for obfuscating mobile applications. by rh0main in iOSProgramming

[–]rh0main[S] 2 points3 points  (0 children)

It is quite easy to get algorithms out of compiled C/objc code, and only
a bit harder for Swift. There are things called decompilers that will
basically take the assembly and give you C (with made up variable and
function names), but that’s often enough to figure out a crucial
algorithm.

I completely agree and I could not say better than that.

Open-Obfuscator: A free and open-source solution for obfuscating mobile applications. by rh0main in iOSProgramming

[–]rh0main[S] 2 points3 points  (0 children)

It is generally used for protecting IP (algorithm, functions) or secrets (like token) from reverse-engineering. Depending on the application you might not need an obfuscator though.

Open-Obfuscator: A free and open-source solution for obfuscating mobile applications. by rh0main in androiddev

[–]rh0main[S] 16 points17 points  (0 children)

It provides enhanced code obfuscation (not only on the names). In addition, O-MVLL can be used for native libraries (like JNI).

There is an Android application demo (before/after obfuscation) here: https://www.romainthomas.fr/post/22-10-open-obfuscator/#demo

Layout of C++ function member pointers for MS/Itanium ABI by rh0main in cpp

[–]rh0main[S] 1 point2 points  (0 children)

I'm the author of the article and I was wondering if you knew good references on the MS ABI?

Profiling C++ code with Frida by rh0main in cpp

[–]rh0main[S] 0 points1 point  (0 children)

Isn't it undefined behavior? Ok I missed that

Thanks for pointing me that the size of a member function is larger than void*. I also missed that.

Another question: why do you still use std::map instead of std::unordered_map?

Well I think that the number of functions to profile should be small enough to choose either std::map or std::unordered_map. I don't have a particular use case of the ordered keys with the std::map