rub-syssec / marx Goto Github PK

In your paper, you mentioned the implementation of an analysis framework called Marx in C++ for Linux x86-64 binaries. However, it would have been helpful if you explicitly stated that only x86-64 binaries are supported, saving readers the time of going through the entire paper to discover this detail. It is unfortunate that you relied on Python scripts that did not work, despite the effort you put into developing the C/C++ code. Additionally, it is not realistic to expect that code written on static data and modified accordingly will work seamlessly on other data. It is also not practical for users to download a 3 GB data set just to obtain an example of the configuration file. It would have been beneficial to reorganize the README.md file, placing the information related to VEX at the forefront before the instructions for building the tool.

Hello,

I built marx and also ran idapython script to excavate necessary data. But, I noticed that in the config file you used a variable called NEWOPERATORS. I couldn't find more information about this in the description (nor in the paper). Could you kindly explain what is it and what parameters to set?

The link behind MARX: Uncovering Class Hierarchies in C++ Programs is dead. Do you maybe mean one of these:

• https://download.vusec.net/papers/marx_ndss17.pdf
• https://www.ndss-symposium.org/ndss2017/ndss-2017-programme/marx-uncovering-class-hierarchies-c-programs/