Strip second executable section about obfuscator

[es3n1n]

Hello,
Implementing such a feature requires a little bit more time than I have these days. And while theoretically implementing this is possible and at first glance doesn't require a lot of work, I am not sure if I would get to it anytime soon.
PR welcome though.

[ZehMatt]

Is there even a reliable way to extend the existing .x section without having to fix RVA's for x64 builds? This will likely shift the address of sections that follow invalidating all RVA's. With relocation items its probably possible but there is still a chance that some code uses imagebase relative addressing.

[es3n1n]

Is there even a reliable way to extend the existing .x section without having to fix RVA's for x64 builds? This will likely shift the address of sections that follow invalidating all RVA's. With relocation items its probably possible but there is still a chance that some code uses imagebase relative addressing.

Ah yes, I completely forgot about x64 rva addressing, if we want to process those as well, we would need to analyze all of the functions within the binary and recompile every single one of them. This indeed requires a lot of work and at the current state I'm not 100% sure in reliableness of my code analysis thingy 😄, however, I fixed some bugs in the dev branch, but there are still a lot more.

However, there is another (a bit more dirty, but still) approach for this, with the custom SDK we can allocate a bunch of memory in the .text section and overwrite it with our stubs. But yeah, I'm not really a fan of such implementation 🤷‍♂️ .