Have you ever encountered an obfuscated JavaScript page that left you frustrated? I've been there too. Spending anywhere from 20 minutes to an hour(or more) trying to reverse-engineer it. Even after using tools like deobfuscate.io, it can be a challenge to make the primary component that I want, functional.
However, I've chosen to embrace a challenge, thinking that I could add a touch of complexity beyond what many publicly available obfuscator's offer, and what I've seen from "real world" examples
With that out of the way, I'm seeking a small group of people willing to test my obfuscator tool, offer feedback, and assist in uncovering any potential bugs. I also need the external motivation to keep pushing its development forward.
As a tester, you could participate as an idea generator, a critic, a regular user offering perspective, a reverse engineer, or even as a code contributor.
I'm getting a bit bored testing it on my own; it would be great to introduce some diversity into the testing process, especially since it's not even finished yet.
It would be pretty healthy to connect with like-minded individuals for coding discussions as well.
It's worth noting that I initially drew inspiration from obfuscator.io, implementing a lot of their idea's. Some features are basic in comparison, while others are more advanced. There are also aspects I haven't replicated at all, and some that only exist in my obfuscator.
One of the more complex features I'm eager to develop is 'control flow flattening,' a technique used by well-known obfuscation tools.
I won't delve into further exhaustive technical details about the tool's functions or challenges, given its ever-changing nature and to maintain an element of pleasant surprise.
However, I've chosen to embrace a challenge, thinking that I could add a touch of complexity beyond what many publicly available obfuscator's offer, and what I've seen from "real world" examples
With that out of the way, I'm seeking a small group of people willing to test my obfuscator tool, offer feedback, and assist in uncovering any potential bugs. I also need the external motivation to keep pushing its development forward.
As a tester, you could participate as an idea generator, a critic, a regular user offering perspective, a reverse engineer, or even as a code contributor.
I'm getting a bit bored testing it on my own; it would be great to introduce some diversity into the testing process, especially since it's not even finished yet.
It would be pretty healthy to connect with like-minded individuals for coding discussions as well.
It's worth noting that I initially drew inspiration from obfuscator.io, implementing a lot of their idea's. Some features are basic in comparison, while others are more advanced. There are also aspects I haven't replicated at all, and some that only exist in my obfuscator.
One of the more complex features I'm eager to develop is 'control flow flattening,' a technique used by well-known obfuscation tools.
I won't delve into further exhaustive technical details about the tool's functions or challenges, given its ever-changing nature and to maintain an element of pleasant surprise.
