Thanks. Just tried it out. It's working good now.
I also noticed the 5-second demo splash screen is gone. Was that interfering with the checkup?

Thanks for the reply. Is this fix available as a demo? So I can test it again?
Nope, I didn't get any results.

Hi, if you still have this problem, can you please contact us at support@enigmaprotector.com?

Would be good if we find ways to touch to solve this problem.

Hello,

I sent files to support about 2 weeks ago, but haven't received a reply.

Basically, if this integrity check doesn't work here ...

I tested both 32-bit and 64-bit keygens with new changes.
Everything seems to be working now.
Thanks for the help!

You guys should think about making your keygen DLL open-source.

If it's based on RSA, then there's nothing to hide, and nothing that an adversary can use to exploit or weaken the security.
There is nothing there that they already know.

And if you let your users re-compile the source, it can help ...

Well, I hope someone can fix this, because this is what I call a show stopper.
If the C# Keygen crashes on my computer, then it will crash on my webserver.
And if it crashes on my webserver, then I cannot use your product.
My webserver specifically uses compiled C# assembly DLLs.

Hi. If you are using The Enigma Protector x64 then platform must be set to x64 as well in your Visual Studio project settings.

I understand, but I don't think that's my problem. The SDK provides two keygen dlls, one 32-bit, the other 64-bit.
I have tried to compile both 32-bit and 64-bit projects ...

I have compiled C# Keygen for all given NET frameworks. They all crash or give invalid results:

NET Framework 2.0 -> crash
NET Framework 3.0 -> crash
NET Framework 3.5 -> crash
NET Framework 3.5 Client Profile -> crash
NET Framework 4.0 -> EP_ERROR_PRIVATEKEYISNOTSET
NET Framework 4.0 Client ...

Oops, sorry, that was for NET Framework 4.0.


I must use C# keygen for NET Framework 3.5. This is the important one for me. (although, it would be nice to see both working for future webserver upgrades)

Now, when I re-compile and call GenerateRegistrationKey, I get a new exception error:


System ...

Hi, just set the CPU type to x86 when you compile the keygen.exe in Visual Studio.

Thanks, that worked. But, now, I get a new error message after clicking on Generate button:

EP_ERROR_PRIVATEKEYISNOTSET

But, this can't be true. I can print out the private key, and it's not empty.


// debug ...