![]() ![]() ![]() They are file container like ISO and ZIP. Understand Nebula Image There are N2S, N2P, N2V files in Acustica Audio products. TECHNiCAL NOTE FOR MANiACS Apart from the main license file scheme (contains key to decrypt library), we will write about their unique bad protection. Don't let your customer selling your products and going to be R2Red. We - R2R, customer, potential customer are watching you. Make a statement that you will remove the shit and focus on the performance and quality. Instead of threatening your customer, do the right thing. We saw you are saying that "legit version is better because you can get updates!" but these updates perform much worse than R2R release unless you change your mind. Please think about how they feel, once after we proved these protections are making your products really fat and decreasing the performance - and R2R ones are far better. As we stated in the previous section, it didn't even take 1 day for us. With the 2 facts above, there are no doubt that we can easily (at least should be much easier than paid protections) remove yours. We can't understand why you can believe in your super bloated multilayered protection. * We have shown that we can decrypt / unpack and emulate expensive commercial protections, which should be obviously more advanced than your homemade one. * We showed we can reverse Virtual DLL trick and make valid keygen for RC4 Crypt for your products in 2014. You have serious misunderstanding about it. Hi developer! Finally you need to change the mind, after you found that current protection scheme does not work for R2R. We also think this release may change developer's mind and avoid "protect more!" action from them :) Mac!!!!! Our decrypted library is macOS compatible if you know how to! We are lazy witches and we don't release 100+ products for macOS. Today, we finally decided to release them. That's why we have kept it internal for long time, and never released 1 or 2 products since 2014. We were sure that they will change the protection again if we release another "art". We know Acustica Audio is freaky worrying about being cracked. If we remember correctly, we already made 1st working crack in 2015 (it was supplied with legit license). The amount of Acustica Audio products had been increasing. Why did it take so long? * We didn't want to expose our crack to public until we can do them (almost) * We were lazy to do all products. It took long time to do them all, but that's a fun part for witches :) Last R2R release (keygen) was in 2014. It took 1 week to realize the library rebuilding like these releases! Anyway, there are many small differences in the protection between product A and B. How long did it take to crack? It just took few hours from one witch to make one product working. ![]() Minimum required skill set: * Know about DLL (if you can manually unpack DLL from UPX, that's enough) * Crypto RC4/RSA * Coding experience with Win32API Legit license is required to make keygen (or perform decryption like R2R). These are completely removed in our rebuild library, because you don't need it anymore :) Simple and good enough! Does Acustica Audio plugins have strong protection? Yes, for beginner crackers. Even small 10KB file have about 3MB of decryption code inside. In some products with many files, our release is 90% smaller than legit version This happens because every single library files have DLL file to decrypt themselves. * Library loading time is faster than legit version because of the reasons above. * Library is not compressed, but it's still smaller than legit one. * Library is not encrypted (RC4/Scorpion) at all. We've rebuilt the whole library which works without any protection. ![]() This time, R2R didn't crack the software. Before we start long technical notes, we should write about more generic things about what people should have more interests. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |