Home » Developing U++ » U++ Developers corner » Considering different approach to Win32 release
|
Re: Considering different approach to Win32 release [message #45386 is a reply to message #45384] |
Tue, 03 November 2015 11:33 |
Tom1
Messages: 1216 Registered: March 2007
|
Senior Contributor |
|
|
mirek wrote on Tue, 03 November 2015 10:48Tom1 wrote on Tue, 03 November 2015 09:27Hi,
Thanks for your effort on Protect. I can confirm that the last working MS compiler environment is MSC9 32 bit.
Mirek: I just tested 9142 with MSC15 and the updated ProtectTest still crashes on CryptedTest() function. Commenting out the call to CryptedTest() enables the rest of the demo to run correctly. So obfuscation actually works properly even with MSC15 while keyed protection crashes. My wild guess is that obtaining the key is the unwanted static/global reference.
Well, that '2' constant actually seems to be a problem... It gets stored in memory and is loaded.
Quote:
Is it possible to make a decision to keep U++ source code compatible with MSC9 until there is a working replacement for the current Protect package?
I have not changed anything in Protect package(s). Just added a bit to docs.
Mirek
I mean, I wish the entire U++ to be kept MSC9 compatible until Protect can be made to work with current compiler(s) e.g. MSC15. I just want to point out this need for backward compatibility when we are simultaneously talking about eventual switch to C++11, and therefore, MSC15.
Best regards,
Tom
|
|
|
|
|
Goto Forum:
Current Time: Wed May 15 04:59:08 CEST 2024
Total time taken to generate the page: 0.02191 seconds
|