- Coverage improvements
- Valgrind added
- Added ELF scanner for modules in memory and for files on disk
- Improved PE scanner, in module scan you can specify section for scan by name.
https://github.com/orange-cpp/omath/releases/tag/v4.6.1
Please open Telegram to view this post
VIEW IN TELEGRAM
GitHub
Release v4.6.1 · orange-cpp/omath
What's Changed
Use clang-cl.exe to generate LCOV coverage report by @luadebug in #129
Valgrind by @luadebug in #131
Feature/elf pattern scan by @orange-cpp in #133
Full Changelog: v4.6.0...v4...
Use clang-cl.exe to generate LCOV coverage report by @luadebug in #129
Valgrind by @luadebug in #131
Feature/elf pattern scan by @orange-cpp in #133
Full Changelog: v4.6.0...v4...
In the next update omath will get new features — crypto containers. I was wondering about not only xor strings in compile time but also other objects that can be sensitive for application integrity. Now you can. Even this simple version looks very horrific in the disassembled version. Its also support RAII scematic like std::mutex with their std::scoped_lock. Even more each encryption key is generated in compile time you also can specify its length and each key for each variable is unique!
https://github.com/orange-cpp/omath/pull/135
https://github.com/orange-cpp/omath/pull/135
Microsoft trying not to put bloat ware in C++ compiler: "Level impossible". Why i need to fuck with x64 native tools for windows? why you cant just put x64 env path by default, why i must do it manually?