Page 1 of 1

Critical Import Protection Bug

Posted: Sat Jun 13, 2015 6:51 pm
by lody
Hi there guys,

im a long time enigma customer and im very statisfied so var, but now i ran into a bug that caused me big problems. Enigma normally should obfuscate the whole import table, but theres a problem. The first entry of every imported module doesnt get obfuscated. Take a look at the screens. I tried different settings in my project but nothing fixed the leaking imports. It would be great if you can provide me a solution or a bugfix in the upcoming update.

file imports without protection:
http://i.imgur.com/fXZ5hlh.png

import table after enigma protection:
http://i.imgur.com/qMRMfQk.png

enigma project settings:
http://i.imgur.com/3fMfILs.png

Im looking forward to an awnser from you.

Thank you very much,
lody

Re: Critical Import Protection Bug

Posted: Tue Jun 16, 2015 6:53 am
by Alec
Hi, this it not the bug. This is done in order to ensure that every imported module gets loaded in a right time.

Re: Critical Import Protection Bug

Posted: Wed Jun 17, 2015 12:39 am
by lody
:?

im gonna load my imports dynamically at runtime then but whats the case in hiding them in the first place if some infos leak through. Would be nice to have a setting for that.

best regards

Re: Critical Import Protection Bug

Posted: Thu Jun 18, 2015 2:17 pm
by Enigma
The reason of that is that when you have at least one function entry for a library then the system will load this library itself (you do not have to load this library yourself, dynamically).

Some libraries, like VC runtime libraries, do not allow dynamic loading (it will fail if you try to load such lib using LoadLibrary). The workaround we use in protection allows to load the library anyway.