You can use Frida.
For your purpose, you need to hook the MD5_Update function using the Interceptor API.
// Use the mangled form ...
When I had the same problem (I was working on ELF binaries from Linux and QNX systems) I had to do the following:
run ldd on the executable to get the list of loaded libraries
obtain a list of exports of each mentioned library (by running nm -CD full_library_name | grep " T " on the system)
If your function is there - it is there
If you are working with C++,...
Answer to your first question
Googling for gdb step yields https://sourceware.org/gdb/onlinedocs/gdb/Continuing-and-Stepping.html as the first result. From that page:
Warning: If you use the step command while control is within a
function that was compiled without debugging information, execution
proceeds until control reaches a function that does ...
You can use GameGuardian for dump memory. Need root.
Memory editor tab - menu - memory dump - select range and folder - press ok - wait for toast "Dump end".
Here some video examples how to do this:
How to dump memory of any running processes in Android -
How to dump odex file from memory on Android -
How to dump deleted file ...
I was misinterpreting the context of the comment in the original link, it seems. I was under the impression that Module.load was a v8-ism, while it in fact appears to be a Frida-API.
There are several ways to show the different functions of a binary file in radare2.
Start by opening the binary file and analyze it.
$ r2 -A libdbm64.so
The simplest way to list the functions, is the afl command which stands for analysis function list. The command will list all the functions in the binary and print it with four columns: ...
I don't know whether the advice I'll give you is the "leading edge way", but I will describe some steps that you can perform in order to protect your software.
Is it possible to protect it such that no one will be able to crack it?
No, and it's important to know that and keep in mind that what you really want to do is to keep it as hard to crack as ...
Found somewhat of a solution.
After a lot googling I came to a conclusion that the ELF file was corrupted on purpose. I've found that only 3 fields can be manipulated in order to make an ELF break a debugger and still be able to run -> (e_shoff, e_shnum, e_shstrndx).
I downloaded ELF ...
an so file is self contained, to use it, you simply need to load it and use functions it implements. However, in order to use those functions a header file describing the functions and their input parameters is required.
Getting the available functions from within an so file is easy, you just need to parse the GOT. Understanding the input (and output) ...